Of course, it isn't just game servers - if it involves internet traffic, ports are involved. Your router uses port forwarding rules to sort out which computer should be sent the traffic relating to the Minecraft server. When they try to connect, their traffic has to be sent to the correct computer on your network, and their connection must be permitted by your router. Say you want to host a Minecraft server for your friends on your computer. Port Forwarding (or port mapping) allows external traffic from the internet to connect to a device, like a computer, on a private network. Fortunately, it's very simple to forward ports on a router if you know where to look What Is Port Forwarding? "ResolvConfPath": "/var/lib/docker/containers/e0b1be5c35ff60f337087f58819be190dcf495796114b6a2054dd78cf0e4679c/resolv.Although modern Wi-Fi routers handle most functions automatically, some applications will require you to manually forward a port in your router's settings. "SandboxKey": "/var/run/docker/netns/cb385fa1d3da", "": "Automated nginx proxy for Docker containers using docker-gen", "maintainer": "NGINX Docker Maintainers ", ".working_dir": "/home/winfield/contain/nginx-proxy", "Image": "nginxproxy/nginx-proxy:alpine", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "Source": "/var/lib/docker/volumes/nginx-proxy_vhost/_data", "Source": "/var/lib/docker/volumes/nginx-proxy_conf/_data", "Source": "/var/lib/docker/volumes/nginx-proxy_certs/_data", "Source": "/var/lib/docker/volumes/nginx-proxy_html/_data", "/var/run/docker.sock:/tmp/docker.sock:ro" I don’t see why changing the default would matter for packets that were already being routed somewhere. One thing I did recently was change the default policy in the FORWARD chain in iptables. nmap confirms that it’s only port 80 that’s actually open on the container. But then I can’t access anything on that, I can access it on port 80 (even though 80 is also in use by the nginx proxy). And then when I use lsof to show what ports are open on the host, I see 8001 in use. I have told Docker to map port 8001 on the host to 80 in the container. So for example one of my apps is just nginx again serving a website. The host even thinks that the originally specified port is open, but it isn’t. After investigating, I found out that the other containers were just opening up whatever ports they wanted to on the host. It couldn’t reach the containerized apps on the ports I had specified. Then all of a sudden I started getting 502 errors from the nginx proxy.
Setup: Arch Linux with kernel 5.16, Docker 20.10.12, using nginx-proxy with its acme companion to get certs for various apps in other containers. I don’t know if it was something I did or what.
0 kommentar(er)
