FileBrowser Unreachable After Docker 4.29.0 Update

[sawyerhart]

Hey there! I have a FileBrowser container in Docker that is no longer reachable through the internet after the 4.29.0 update. Previously we were using FileBrowser as an FTP server for our organization, so it was working on a large scale, though now it is completely inaccessible (besides locally accessing it). The server runs off of a Mac Mini on Ventura 13.4. Honestly, I have little to no experience using Docker or any code-centric programs in general (someone else set up the server before me), but I’m willing to dig a little if I have a place to start. If anyone has any pointers or questions, they would be greatly appreciated!

Thanks so much.

[rimelek (Ákos Takács)]

Why it stopped working, I don’t know, but whether it works or not depends on your firewall. I made some screenshots to show you where the settings is to allow incomming connections for Docker Destkop on macOS

Go to System settings » Network

Choose Firewall

Either disable thw firewall (temporarily) or click on “options”

Make sure “block all incomming connections” is not enabled

Scroll down to “Docker.app”

Make sure it is set to “Allow incomming connections”

If it still doesn’t work, also make sure the port mapping definition of the container does not contain an IP address like 127.0.0.1. You can even set it to 0.0.0.0 to forward from all ip addresses if you wan to.

If it still doesn’t work, I have no idea. I use Docker Desktop for Mac v4.29.0 as well. I have macOS 14.4.1, but Docker Desktop supports the latest and two previous macOS versions so v13 is still supported.

[sawyerhart]

Thank you so much for your response! This was helpful.

I checked out the network settings and it appears that Docker connections are indeed allowed.

I am wondering about your second potential solution though, how would I check what IP address the port mapping definition contains?

I will be doing some Googling in the meantime

Thanks again!

[rimelek (Ákos Takács)]

@sawyerhart

I checked out the network settings and it appears that Docker connections are indeed allowed.

That option is inactive. It means you have “Block all incomming connections” turned on. My 3rd screenshot shows when that setting is wrong and the 4th shows when it is right and only then can you scroll down and check if Docker is enabled. It will be, because that can be seen even when the option is inactive. But the text must be white, not grayed out.