How to forward ports correctly when they are already busy?

[ivan-pinatti]

How to forward ports correctly when they are already busy?

[ivan-pinatti]

Hello @Magisdn,

You can check the docker-compose official documentation, please find it here.

[Magisdn]

I read the documentation, but after running the containers I can't connect to any of them :(

[ivan-pinatti]

@Magisdn

I hope this article can help you to investigate the open ports you have running on your machine and then you can adjust accordingly. My suggestion would be to stop all services to avoid any port been in use.

[Magisdn]

@ivan-pinatti
Thanks, I know how to look at open ports, but none of them are available.
All of them are forward on the home server via protonvpn, but none are accessible from the local network.

$ sudo netstat -tulpn | grep LISTEN 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      462/sshd: /usr/sbin 
tcp        0      0 0.0.0.0:8087            0.0.0.0:*               LISTEN      9090/docker-proxy   
tcp        0      0 0.0.0.0:8090            0.0.0.0:*               LISTEN      2630172/docker-prox 
tcp        0      0 127.0.0.1:9050          0.0.0.0:*               LISTEN      4925/docker-proxy   
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      999/docker-proxy    
tcp        0      0 0.0.0.0:3005            0.0.0.0:*               LISTEN      2630403/docker-prox 
tcp        0      0 0.0.0.0:8989            0.0.0.0:*               LISTEN      2630068/docker-prox 
tcp        0      0 0.0.0.0:9117            0.0.0.0:*               LISTEN      2630048/docker-prox 
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      478/smbd            
tcp        0      0 0.0.0.0:8191            0.0.0.0:*               LISTEN      2630152/docker-prox 
tcp        0      0 0.0.0.0:8384            0.0.0.0:*               LISTEN      8578/docker-proxy   
tcp        0      0 0.0.0.0:3779            0.0.0.0:*               LISTEN      8741/docker-proxy   
tcp        0      0 0.0.0.0:8324            0.0.0.0:*               LISTEN      2630130/docker-prox 
tcp        0      0 0.0.0.0:6789            0.0.0.0:*               LISTEN      2630337/docker-prox 
tcp        0      0 0.0.0.0:7878            0.0.0.0:*               LISTEN      2630273/docker-prox 
tcp        0      0 0.0.0.0:6791            0.0.0.0:*               LISTEN      2630315/docker-prox 
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      4037077/docker-prox 
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      884/docker-proxy    
tcp        0      0 0.0.0.0:9898            0.0.0.0:*               LISTEN      2630025/docker-prox 
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      478/smbd            
tcp        0      0 0.0.0.0:8686            0.0.0.0:*               LISTEN      2630110/docker-prox 
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2630253/docker-prox 
tcp        0      0 0.0.0.0:32400           0.0.0.0:*               LISTEN      2630003/docker-prox 
tcp        0      0 0.0.0.0:22000           0.0.0.0:*               LISTEN      8445/docker-proxy   
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      5690/docker-proxy   
tcp        0      0 0.0.0.0:2000            0.0.0.0:*               LISTEN      4948/docker-proxy   
tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      2630233/docker-prox 
tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      1048/docker-proxy   
tcp        0      0 0.0.0.0:8082            0.0.0.0:*               LISTEN      2630213/docker-prox 
tcp        0      0 0.0.0.0:5299            0.0.0.0:*               LISTEN      2630359/docker-prox 
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      2630193/docker-prox 
tcp        0      0 0.0.0.0:8787            0.0.0.0:*               LISTEN      2630090/docker-prox 
tcp        0      0 0.0.0.0:5076            0.0.0.0:*               LISTEN      2630382/docker-prox 
tcp        0      0 0.0.0.0:6868            0.0.0.0:*               LISTEN      2630294/docker-prox 
tcp        0      0 0.0.0.0:6420            0.0.0.0:*               LISTEN      9172/docker-proxy   
tcp        0      0 0.0.0.0:32469           0.0.0.0:*               LISTEN      2629896/docker-prox

Maybe the problem is in the protonvpn container?
In his log:

[cont-init.d] 70-vpn-setup: executing... 
2023-01-11 23:51:07+03:00 [INFO    ] OK! Check URL is secure 
2023-01-11 23:51:07+03:00 [INFO    ] Healthcheck endpoint returned 200 
2023-01-11 23:51:07+03:00 [NOTICE  ] Free Plan 
2023-01-11 23:51:07+03:00 [NOTICE  ] Protocol: UDP 
2023-01-11 23:51:07+03:00 [NOTICE  ] Using fastest server from COUNTRY: US 
2023-01-11 23:51:07+03:00 [INFO    ] Validating CIDRs 
2023-01-11 23:51:07+03:00 [INFO    ] CIDR 192.168.1.0/24 is valid 
2023-01-11 23:51:07+03:00 [INFO    ] Enabling DNS leak protection. 
2023-01-11 23:51:07+03:00 [NOTICE  ] Following CIDRs will be excluded from VPN 192.168.1.0/24 
2023-01-11 23:51:07+03:00 [INFO    ] Creating folders 
2023-01-11 23:51:07+03:00 [INFO    ] Set file permissions 
2023-01-11 23:51:07+03:00 [INFO    ] Prefetch server list 
curl: (28) Operation timed out after 20000 milliseconds with 0 out of 0 bytes received
[cont-init.d] 70-vpn-setup: exited 28.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

[ivan-pinatti]

@Magisdn, for testing purposes, you could shutdown all the other services to test the container stack. And then, slowly turning services on, one by one, to make adjustments.

The container stack works well, it looks like there is some conflict on your ports/network configuration that you will have to investigate further. I hope it helps.