search

docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
233 stars 48 forks source link

Public static IP blocked #2370

Closed pears0 closed 3 months ago

pears0 commented 4 months ago

My static Public IP address appears to be blocked / rate limited on auth.docker.io. This means I am unable to register my docker instances for work so as to avoid any issues with download limits from the docker hub.

Public IP: 45.13.7.122

Could it be unblocked so I can at least log into docker desktop etc please?

ingshtrom commented 4 months ago

Thank you for reaching out. I would like to get more detail from you so I can better help you.

Can you be specific with what command you are running or how you are trying to log in?

Can you please provide the error message you are receiving or the difference between your expected and actual behavior?

Thank you!

pears0 commented 4 months ago

I'm attempting to login to docker hub from my docker deamon: root@nas:~# cat dock_pass.txt | docker login --username gonzohome --password-stdin Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 10.42.2.200:50034->54.198.86.24:443: read: connection reset by peer

I'd expect to be able to login or get an authentication failed error message. I also attempted to login on docker desktop on a different machine behind the same public IP. The web login works, but the desktop app instantly logs back out and asks for me to login. It appears that I'm unable to access the api / api auth from behind my public IP address

pears0 commented 4 months ago

I've also just tested on a 3rd machine on my home network that's connected via a dial-in VPN, so appears from a seperate static public IP address, and that's connected successfully without issue on the same account details.

pears0 commented 3 months ago

Any updates? @ingshtrom

ingshtrom commented 3 months ago

Thank you for the info!

That is strange, but I've heard of it happening from time to time. I cannot reproduce this. In addition, all of our rate limits, anti-abuse limits, and legal geo-restrictions are done at layer 7 of the OSI model (HTTP). If you were being limited or blocked by us, you would receive a HTTP response code from our server saying such.

I am curious, in #2271 they had a similar issue and a VPN worked. Requesting a new IP from their ISP seemed to fix the problem. I wonder if your IP rotated from your ISP recently 🤔

Do you see these same problems when attempting to reach hub.docker.com from your browser?

pears0 commented 3 months ago

I do see the issue on hub.docker.com and as mentioned, behind a VPN from the same network I connect fine. I see the issue on hub.docker.com, I have a right game logging in via a browser, and as such, the login from docker desktop appears to initally connect then signs out again immediatly.

My IP from my ISP is static and hasn't been rotated in at least 18 month, possibly the last 2 years, wondering if the whole block (it's assigned from a /24 block) has been blacklisted somewhere? Are you using Amazon for your hosting, wonder if Amazon is doing something funky, as I see a lot of packet fragmentation issues from Amazon IPs on my firewall.

ingshtrom commented 3 months ago

Yes, we use Amazon for this endpoint.

pears0 commented 3 months ago

This is what I see on my network tab when I attempt to log in to docker-desktop via the web page: image

It seems really odd that it's taking so long. This is in firefox, but I don't see this issue as much when on the VPN but still on firefox.

pears0 commented 3 months ago

Ok, I'm pleased to report I have finally identified the issue and resolved it.

For future refrence, the issue was being caused by packet duplication by one of my switches erronously mirrior packets across VLAN's!!!!