Thanks already for your help 🙏🏽
For DynDNS: {"server":"1.3.3","client-web":"11.0.0","client-flutter":"9.0.0","client-apple":"2.0.0","client-android":"2.0.0","client-graphql":"October 2021","client-rest":"","console-web":"0.1.0","console-cli":"2.0.2","server-nodejs":"9.0.0","server-deno":"7.0.0","server-php":"8.0.0","server-python":"2.0.0","server-ruby":"8.0.0","server-dart":"8.0.0","server-kotlin":"2.0.0","server-swift":"2.0.0","server-graphql":"October 2021","server-rest":""}
For the subdomain: {"server":"1.3.3","client-web":"11.0.0","client-flutter":"9.0.0","client-apple":"2.0.0","client-android":"2.0.0","client-graphql":"October 2021","client-rest":"","console-web":"0.1.0","console-cli":"2.0.2","server-nodejs":"9.0.0","server-deno":"7.0.0","server-php":"8.0.0","server-python":"2.0.0","server-ruby":"8.0.0","server-dart":"8.0.0","server-kotlin":"2.0.0","server-swift":"2.0.0","server-graphql":"October 2021","server-rest":""}
What's not working?
I don't get a certificate for my subdomain. Only for the IP, and before the DynDNS domain. My subdomain doesn't have an A record pointing to Appwrite, as it's routed through DynDNS. Can it work this way? Actually, is worked last time, but I don't get a new certificate now.
What do you mean you don't get a certificate? What happens?
IPs can't get a valid certificate
You custom domain does not need an A record
When I say domain, I mean domain or subdomain
The certificate for my subdomain is expired. And there is no new one. There now are new ones for the IP and DynDNS though (not valid, but at least existent).
Is this supposed to be your main hostname or your custom domain hostname?
What do you mean? For Appwrite I use my subdomain, like sub.domain.com.
My response to the message was that I tried and it was not successful. This only helps the UI show 'verified'.
How many hostnames do you need for your Appwrite instance?
Setup is: My domain has a subdomain like sub.domain.com, with a CNAME to sub.dyndns.com, that gets updated to forward to the server's IP. I only access Appwrite via sub.domain.com. This already worked for 8 months, but no new certificate was generated, so now it's not accessible from the app.
It's a very basic setup I believe. Just a DynDNS between my subdomain and the server.
So it sounds like you only need 1 hostname for your Appwrite instance. You don't need to create a custom domain in your project then. You need to add your hostname as the domain and domain target environment variables. Delete the custom domain in your project
So sub.domain.com as app domain target and app domain? I had this for 9 months and it didn't work.
I only added the custom domain since this thread
Yes. If something isn't working, you would need to check the logs for the appwrite-worker-certificates container
Actually it did work in the beginning, but since April the certificate is expired. Is there a way to just use the certificate from my website (from my registrar)?
I already posted logs earlier here: https://discord.com/channels/564160730845151244/1103160463585456249/1103165225504624700
So far I tried all suggestions, turns out they're not necessary and my setup was ok. I can send you the full log via message if that helps.
sure, please DM me the logs from the worker
I solved it after a long day of debugging: The IPv6 suffix of my server changed when I restarted it in January. I changed it back, and now the http challenge works again 😊
Recommended threads
- Issue with downloading large files (40GB...
Hi everyone! I am using the latest Appwrite 1.8.0 version on my self-hosted server. I successfully uploaded a large ZIP archive (~40GB) using the chunked uploa...
- Firebase app import
I'm **very** new to appwrite and I just set up appwrite with docker and I'm trying to import a Firebase app I have set up but it's erroring and I don't really k...
- Console infinite loading behind NginxPro...
Hi All, I am trying to get AppWrite to work behind NPM. I've followed the Medium guide to set proper headers, I've added my proxy configuration to NPM, and I ...