How to deal with bind issues with default/standard ports - New Ports?

[nodecentral]

Is your feature request related to a problem? Please describe.

With so many ports and different set ups in use out there - and by looking at the number of related support issues raised - people are often faced with bind issues whenever I’m setting up containers that n want to use more of the default network setting.

Is there a way for NPM to better handle that..

If I simply try the quick start guide on my QNAP NAS, it instantly has an issue with port 443 (see below). - For a quick start guide if would be great if there was a very low likelihood of an error being encountered..

Failed to create application "npm". Error message: operateApp action …. Error response from daemon: driver failed programming external connectivity on endpoint npm-app-1 (18dae2dcc7eee4f9348dcc89824df962d8d62d60f1148ec79795521854a587fc): listen tcp4 0.0.0.0:443: bind: address already in use

Describe the solution you'd like

In situation where someone is only trying to access other docker containers, can NPM make use of its own ports and remove their emphasis on the defaults ? I appreciate it might require a new port exposed but it would be one dedicated and monitored by NPM?

[cjboyle]

Maybe I'm misreading your issue, but normally nginx/NPM should bind to the standard ports (80:80, 443:443), and your apps should be bound to non-standard ports (e.g. 10080:80, 10443:443, or as required by each app).

Do you know what is currently using :443, e.g. is it a QNAP web UI, or another container?

[nodecentral]

Running a quick check, the QNAP UI / control panel seems to suggest my TLS https web port is 8081, yet going into the command line and doing a look up, I can see there is something associated with 443, but I have no idea what it is - although the other apache_proxys entries are for the non TLS http web port of 8080..???

apache_proxys    7555   admin     IPv6  TCP     *:443
apache_proxys    8679   admin     IPv6  TCP     *:443
apache_proxys    28712  admin     IPv6  TCP     *:443

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1:

[falciloid]

I have an another replication of this issue. RouterOS 7.19.2. Container will interfere with service (SSTP server) that use same port (443). It won't interfere right after container start, but it will after container restart.

UPD: It seems I find a root for this issue in my case. I will create a stream to 443 port. Maybe it also make sense in other cases