this post was submitted on 28 Oct 2023
5 points (100.0% liked)

Self-Hosted Main

521 readers
6 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 2 years ago
MODERATORS
[email protected]
5
Can somebody help me understand the 0.0.0.0 address in docker? (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
5 comments fedilink hide all child comments
 

Basically, I have this doubt, I have some self hosted services in docker where I add the ports like this:
host_port:container_port, so I don't specify the interface, so by default, it is 0.0.0.0.

Somebody recently told me that this is dangerous and that I expose my services to the public internet by doing this. I don't want to do that since I am the only one accessing them so I just use a vpn to access them. So, to try this out, I typed in my browser my public ip alongside the host port I used for one of my services but I cannot access it. This has me puzzled. How's the deal? Am I exposing it? Should I change it?

What are your thoughts? Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

0.0.0.0 means it binds to every available address on your docker host. If your host has a directly available public IP, then i can understand the concern.

if your box is behind your network firewall, then you would have to port forward to have the service reachable from the internet.

You’re welcome to bind to a specific IP on your host, I do this over plain 0.0.0.0. Looks cleaner that way IMO.

i use static IPs and it’s been fine for me for months-years now.

But why do you have UPnP enabled?