About Custom root certificates

I deployed Seatable on a local area network and encountered a problem with the certificate. According to the instructions on this link Custom Certificates - SeaTable Admin Manual , I created the /opt/caddy/certs/ directory and used the command “openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ./key.pem -out ./cert.pem” to apply for the certificate. In the eatable-server.yml file, I added the following: labels: caddy: ${SEATABLE_SERVER_HOSTNAME} caddy.tls: “/data/caddy/certs/cert.pem /data/caddy/certs/key.pem” However, it still doesn’t work. What could be the problem?

The link you provided seems to have failed to resolve. This issue might be related to the link itself or the network connection. Please check the validity of the link and try again. If you need further assistance with the certificate issue, feel free to ask.

What do you mean with that? I don’t get it.

Please post here the complete label part of your seatable-server.yml. Use backticks to paste it as code.

I installed it according to this tutorial.


docker compose up -d
.env

seatable-server.yml

cd /opt/caddy/certs
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ./key.pem -out ./cert.pem


This is the main error:
/data/caddy/certy/cert.pem is a directory.
image
You have to solve this first.

Is there a tutorial for deploying on an intranet and manually applying for certificates?
Thanks!

Hey apple524,
All necessary information can be found at https://admin.seatable.com/.

My recommendation would be that you book a VPS for around 5 € / $ per month and install SeaTable with caddy and a let’s encrypt certificat. This will save you a lot of time and headace.
Alternatively I offer to support you in a paid support session.

Best regards
Christoph

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