-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug Report: Cannot renew domain #8153
Comments
@mauricev, thanks for creating this issue! First, running Secondly, since you have cloudflare in front of Appwrite, there's no need for Appwrite to generate certificates. You can just disable the worker. Is there anything else you need or can this be closed? |
You're saying that the communication between cloudflare and appwrite doesn't require a certificate? How does this communication happen then? |
According to this, https://forumweb.hosting/22401-difference-between-flexible-full-and-full-strict-in-cloudflare.html, this is not correct. I have it Full (strict) which requires appwrite have a valid certificate. |
@mauricev, full should be fine because, by default, traefik serves a self signed certificate. |
This doesn't seem to be happening
|
For whatever strange reason, the traefik container wasn't running. All appears to be well now. Thank you. |
馃憻 Reproduction steps
Run sudo docker compose logs appwrite-worker-certificates
馃憤 Expected behavior
Certificate should renew regardless of its current status. Who is even checking this? Why?
馃憥 Actual Behavior
This server is behind a cloudflare firewall, so the certificate cannot on its own be renewed. I have to manually disable it and then run sudo docker compose logs appwrite-worker-certificates to renew certificate. I want the renewal to take this place on a given day to coincide with another server on this same VM. Instead, I am greeted with this message:
There is also no way to check the certificate's status on appwrite.
馃幉 Appwrite version
Version 1.5.x
馃捇 Operating system
Linux
馃П Your Environment
No response
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: