When running any container, ERR_CONNECTION_RESET on first load in Chrome but works normally in Firefox

Docker Desktop
1

When running containers, accessing a container in the browser leads to ERR_CONNECTION_RESET in Chrome, but loads as expected in Firefox. Sometimes it reloads and loads successfully, sometimes, it reloads but only partly, and sometimes it won’t load at all. This happens both with containers I set up and the welcome-to-docker container you can get directly in the GUI.

OS Version/Build: Windows 11 Home, 22621.1848
App Version: Docker version 24.0.2, build cb74dfc
Chrome Version: Version 114.0.5735.199 (64-bit)

Steps to Reproduce:

Attempt 1: Via the welcome-to-docker container

  1. Go to the Learning Center
  2. Download the welcome-to-docker container (which starts itself)
  3. Go to http://localhost:8088/

This circles for a while and eventually shows ERR_CONNECTION_RESET in Chrome, but loads as expected in Firefox.

Attempt 2: Via my own container

  1. Run the command docker run -d -p 9000:80 nginx in command line to create an NGINX container bound to port 9000.
  2. Go to http://localhost:9000/.

Again, this circles for a while and eventually shows ERR_CONNECTION_RESET IN Chrome, but loads as expected in Firefox.

Attempted fixes:

  1. Checked for Chrome updates
  2. Disabled extensions while attempting to load the page.
  3. Tried loading in Incognito Mode to see if it was a particularly strange caching issue.
  4. Completely cleared all history
  5. Reset Chrome to defaults.
  6. Uninstalled and reinstalled Chrome.
  7. Restarted PC

What’s particularly odd to me is the Docker logs:

This is what seems to be produced when I open the container in Firefox (which works):

2023-07-02 08:25:56 172.17.0.1 - - [02/Jul/2023:13:25:56 +0000] "GET /favicon.ico HTTP/1.1" 200 15086 "http://localhost:8088/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0" "-"

So, that’s a simple 200 response code as you would expect.

I haven’t been able to capture a log for when it doesn’t load at all, but on an instance where it reloaded but only partly (e.g. loaded but looks wrong), I got these when loading in Chrome:

2023-07-02 08:34:11 172.17.0.1 - - [02/Jul/2023:13:34:11 +0000] "GET / HTTP/1.1" 200 659 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36" "-"
2023-07-02 08:34:11 172.17.0.1 - - [02/Jul/2023:13:34:11 +0000] "GET /static/js/main.8b84ea86.js HTTP/1.1" 200 382483 "http://localhost:8088/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36" "-"
2023-07-02 08:34:26 172.17.0.1 - - [02/Jul/2023:13:34:26 +0000] "GET /favicon.ico HTTP/1.1" 200 15086 "http://localhost:8088/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36" "-"

That seems to be sending a 200 response, but also a 659, and I don’ t know what that represents? It doesn’t seem to be a standard response. Another time (but I didn’t copy this log), I got a 200 and 615, which I think is an SSL error.

I did look at the forums and do a fair bit of searching, but I didn’t find anyone with a matching error to this. Does anyone have any ideas for fixes?

2

Hrm…I’m starting to suspect Webroot, my antivirus.

I can’t seem to get consistent results. Sometimes if I disable it and clear my history, I get the container to load in my browser right away. Other times, it still doesn’t load completely the first time and has to be reloaded. Still very peculiar.

3

659 is not status code. It is probably the size of the response.

Again, you got HTTP 200. SSL errors are pretty hard to miss in the log or in the browser and you don’t even use HTTPS.

and another number next to the status code. So as you can see, there is no difference :slight_smile: The size is bigger because it’s a favicon, not a text plain text response.

MY guess is that Firefox waits until it can give you a working site while chrome gives you the error too.

Antivuruses can indeed cause issues if not compatible with Dockr Desktop somehow, so it’s a good guess.