Unable to bind ports 443 or 80 to docker container

IPv4/6, Port, VPN, proxy, SSH, remote access and more.
Locked
User avatar
matt_30
Posts: 67
Joined: 02 Jan 2021, 23:22

Unable to bind ports 443 or 80 to docker container

Post by matt_30 »

I appear to be unable to bind ports 443 or 80 to any docker container.

I am unable to see any application using these ports.

Is there any process the TNAS uses which reserves these ports?

I'm planning to use these to point to docker containers.
User avatar
TMS
TerraMaster Team
Posts: 508
Joined: 20 Oct 2020, 17:06

Re: Unable to bind ports 443 or 80 to docker container

Post by TMS »

Hi,
Port 80 is occupied by the web server and port 443 is occupied by the system, none of them can be used elsewhere
To contact our tech team, please email to support(at)terra-master.com, remember to replace (at) with @
User avatar
matt_30
Posts: 67
Joined: 02 Jan 2021, 23:22

Re: Unable to bind ports 443 or 80 to docker container

Post by matt_30 »

Thank you for confriming.

What does the system need 443 for?

Can this be moved? This is impacting the ability to run many containers.
User avatar
TMS
TerraMaster Team
Posts: 508
Joined: 20 Oct 2020, 17:06

Re: Unable to bind ports 443 or 80 to docker container

Post by TMS »

Port 443 is used by TNAS PC to search for TNAS device address and cannot be moved.
To contact our tech team, please email to support(at)terra-master.com, remember to replace (at) with @
User avatar
matt_30
Posts: 67
Joined: 02 Jan 2021, 23:22

Re: Unable to bind ports 443 or 80 to docker container

Post by matt_30 »

Is there any reason why you have selected the most commonly used port for your discovery app?

You have almost 50,000 ports you could have used but blocked the one most commonly needed for many applications.

Applications like SWAG, Nextcloud or anything which requires SSL cert generation requires this port.

Can you please change this port in your next build as you are seriously limiting the capability of your product.
Locked