Invalid or non-existent authentication information
See original GitHub issueWhen I run python setup.py sdist upload
I always get:
Submitting dist/xxxxxxx-0.1.4.tar.gz to https://upload.pypi.org/legacy/
Upload failed (403): Invalid or non-existent authentication information.
error: Upload failed (403): Invalid or non-existent authentication information.
It never asks me to enter my username but only password. So I assume the username is the same as when I run “register”.
I am pretty sure that password I entered is correct because I can login https://pypi.python.org/pypi
Could you please help? I am not new to pypi. I published several packages before. But now I am confused. What has changed recently?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:13
- Comments:50 (8 by maintainers)
Top Results From Across the Web
403 Client Error: Invalid or non-existent authentication ...
403 Client Error : Invalid or non-existent authentication information occurs when uploading new module to pypi with Twine.
Read more >PyPI deployments : Invalid or non-existent authentication ...
Hello,. I am trying to setup travis to automatically deploy to PyPI. Nothing I tried seem to work so far. My travis config...
Read more >How to Fix Pypi Upload failed (403): Invalid or non-existent ...
If you run into authentication failure when trying to upload packages ... failed (403): Invalid or non-existent authentication information.
Read more >LO78785: ERROR 'INVALID OR NONEXISTENT DOCUMENT'
Several users receive an error message, when they start their lotus notes client. (after they filled in their password)
Read more >Help - PyPI
How can I use API tokens to authenticate with PyPI? ... Why am I getting a "Invalid or non-existent authentication information." error when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Heres What I Did To Fix:
Created
~/.pypirc
File With The Following Contents:The very existence of this issue, the number of people commenting, etc, shows this stuff is really quite bad 😦
Could someone explain why
https://upload.pypi.org/legacy/
is a URL that we should/can use?