I have a brand new install of Debian 12. I am installing Seatable by the new admin guide. The first issue I had was that the Caddy package would not install because it said a port was in use. I have Apache listening on ports 80/443 so that was the conflict. I changed apache to ports 81/444 and then I was able to successfully install Seatable with all Docker installs currently working and healthy.
HOWEVER, my website will not load. When I go to my URL it just spins and then after 20 seconds it says:
Secure Connection Failed
An error occurred during a connection to www.mydomain.com. Peer reports it experienced an internal error.
Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
this seems to be some sort of SSL issue. I went to /opt/seatable-server/ssl and there are no files in there. I’m thinking that Let’s Encrypt did not install for some reason.
Any ideas on how I might troubleshoot this. I am so close to finishing, I just need this last port or SSL issue resolved.
When I installed Debian I installed Gnome as well as “Web Server” and “SSH Server”. I had a feeling the Web Server was interfering with Caddy, so I went back in reinstalled Debian with only Gnome, no other services. I thought I would need a Web Server (I guess Debian uses Apache) to direct incoming traffic to my hostname , but I think that is what Caddy is doing. I’m not familiar with Caddy which is why I was confused; i’m not sure if it is a reverse proxy or a full blown web server.
UPDATE - so after the fresh install and not installing Apache, I am able to reach my SeaTable without any issue.
Related Topic - What happens if I want to host websites on my Debian box in the future? Won’t I need to install Apache and won’t it conflict again with Caddy?
Thank you,
Mark (newbie to Linux but eager to learn)
Open Ports for HTTP and HTTPS access (probably more ports for other components)
The ports should not be already in use by another proxy such as NGINX or Apache
If the requirements are not met, you should not be surprised if it does not work.
Following the instructions pays off
Last comment: setting up a SeaTable Server is not difficult. But we only recommend the operation of a production SeaTable Server to experienced Linux Admins. If you don’t know what you are doing, you risk losing all your data.
