
Hi there,
I have self-hosted appwrite on a VM, which had a nginx proxy manager issuing the SSL certificates. NPM was pointing to the appwrite container and had the subdomain baas.example.com
as subdomain. Now I have moved the appwrite endpoint to a DigitalOcean appwrite droplet. The only thing what is missing is the SSL certificate. NPM allows me download the SSL certificate for the subdomain baas.example.com
but I don't know how to import the certificate into the DigitalOcean appwrite droplet. If I didn't misread the docs, I would need to use my TLD (example.com
) to be pointing to the appwrite instance. But the the TLD is used for displaying my website. So what exactly should I do to get my appwrite instance SSL certified?

Don't you have NPM on your new server?

No NPM is not installed on the new server (yet). I would only add it if necessary. Wasn't Traefik also capable to do what nginx (NPM) can, like issuing, renewing certificates etc.?

Generally, isn't appwrite designed to cover the certificate handling etc. by its own? Or is using nginx proxy manager of advantage?

You said you have other apps on that server too. How are you handling that?

In the past I used to have other apps. Now I wanted to have a dedicated appwrite server/droplet. So there is now handling required besides appwrite for this instance anymore.
Recommended threads
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
- Issue - Migration From Cloud > Self Host...
Hi team, I’m trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in “archive mode” due to th...
