-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: SSL bug, 0.11 #2669
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I've been having similar issues:
|
@lost-RD the |
@reyesmfabian it seems like your certificates worker has problems connecting to Redis. Try to restart it and check your Redis instance status. You can also use the Appwrite Doctor to check for any potential issues. |
Hi @eldadfux I did everything but nothing seems to work, I restarted the service, restarted the containers, restarted the server, everything, and it never fixed. The only thing that worked was deleting everything and restoring an old copy of my Appwrite instance. I'm worried that something similar will happen again. The other thing, I don't know where all those domains are coming from in my instance, I never added them. |
SSL has been completely refactored lately, if new issues arise please open a new issue. |
Uh oh!
There was an error while loading. Please reload this page.
👟 Reproduction steps
One of the certificates on one of my servers expired and it did not renew automatically. Try running
docker-compose exec appwrite ssl
But the certificate still shows the same error.
👍 Expected behavior
The certificate should renew automatically without any problems.
👎 Actual Behavior
The certificate shows the error NET::ERR_CERT_DATE_INVALID, this is the
log docker-compose logs appwrite-worker-certificates
. I changed my real domain for MYDOMAIN string.In the logs, I see many domains that I don't know where they come from, domains like "happyfox.com" or "2tech.net". Nowhere in my configuration are these domains found, I did not add them at any time.
🎲 Appwrite version
Version 0.11.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: