Error message "Bind for 0.0.0.0:443 failed: port is already allocated"

Admin Talk Installation
1

Your Setup:

  • Hardware or environment you use: UGreen NASync DXP2800
  • SeaTable Edition (Developer or Enterprise) Enterprise
  • SeaTable Version (only necessary for self-hosted): 5.2.7
    You can find your SeaTable Server version at https://your-server-url/server-info

Describe the Problem/Error/Question:

Please describe your issue as precise as possible. If helpful, you can also provide:

  • Commands you executed: All in the manual at SeaTable Server - SeaTable Admin Manual up to docker compose up -d
  • At that point the error message comes up.
  • I am quite sure this comes from Nextcloud being installed on the NAS as well using the same ports. How can I work around this?

Error Messages:

If there are any error messages shown in the console, please include them for better readability by wrapping them in a code block.

[+] Running 3/4
 ✔ Container mariadb          Healthy                                                                              0.0s
 ✔ Container redis            Healthy                                                                              0.0s
 ✔ Container seatable-server  Started                                                                              1.6s
 ⠧ Container caddy            Starting                                                                             4.7s
Error response from daemon: driver failed programming external connectivity on endpoint caddy (cd8dd31211e85f469643d06a15b2936397324fd3047f58915d114878fc4f9138): Bind for 0.0.0.0:443 failed: port is already allocated
2

Caddy tries to bind to port 443. The port, however, is already in use. I guess you are running another web server/proxy on your machine.

Ok, are reviewing your post again, I see that you are also running Nextcloud on the same machine. Then your assumption is spot on.

You’d have to run SeaTable on non-standard ports. I advise against it. It is possible, but inconvenient and will cause all kinds of problems down the road.

I suggest you create a new VM.

3

Thanks for your reply.
Any suggestions how to achieve this easily? Any special settings needed for that VM?

4

I am not familiar with UGreen NASync DXP2800. Generally also, we do recommend against the installation of SeaTable on NAS.

I suggest you get a plain vanilla Linux VM at Hetzner, OVH, ionos, … with >= 4 cores, 8GB RAM and sufficient storage for your use cases and follow the instructions for the basic single node deployment.

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.