-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker login returns 400 Bad Request #7159
Comments
@nicholasamorim please reproduce this issue and attach the package containing all the log files. |
registry.log
adminserver.log
core.log
And this is what the Nginx that is acting like a proxy logs:
If I curl straight to the auth service, it is successfull:
This effectively returns:
|
@nicholasamorim I notice the timestamp in your log messages mismatch. Additionally is the nginx log the one you deployed in front of Harbor? There's another nginx container running when you deploy Harbor OSS, could you provide the logs of that container in the same time frame the error happened? |
Ah, they mismatch because I issued several of the Sorry, forgot to paste the Harbor's nginx logs proxy.log
How can I even find out more about what's causing the 400 Bad Request? The logs (for me) don't seem too helpful. |
Did you reproduce the
Based on these messages Harbor returned Normally by checking the log there should be some clue, but the information you provided has mismatch timestamps so I'm confused... |
Okay, I'll provide logs from the same timestamp. The lines will be the same as the one I've sent already, though. Yeah, that's what bothers me, I can't find the source of the 400. adminserver.log
core.log
proxy.log
registry.log
my nginx access log:
So the only 400 I can see is this last one, but I don't see any errors on registry.log - so I'm at loss on what to do or even investigate. |
I have fixed this. I had applied the recommended settings by the dev-sec project on Nginx. Turns out this was the culprit: Increasing the number made it work. Thank you for your time and sorry I didn't find the issue before. |
Your nginx ssl config helped me to fix mine(!). I had |
For me, this issue came from an invalid |
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
Expected behaviour: for docker login to return sucessfully
Actual behaviour:
However, if I enter a wrong user/password, I get what's expected:
Steps to reproduce the problem:
I've installed Harbor and I'm running it behind a Nginx that terminates the SSL. Due to conflict in ports/names, I have:
redisharbor
/ port 6380.8798
.As per the troubleshooting section I have commented out the line below in Harbor's Nginx:
I can access the UI, I can login, I can use Harbor's API - all containers are healthy.
But I can't use
docker login
Versions:
Please specify the versions of following systems.
Additional context:
My Nginx configuration:
Harbor configuration files attached:
config.zip
The text was updated successfully, but these errors were encountered: