A similar error about expired certificate as few others listed here, but I want to ask if it isn't the bug that there is no automatic 'job' to execute certificate refresh? Is it something which self-hosted appwrite administrator should control or the refresh should be automatic? I was running 1.4.1 when the error first occured and upgrading to 1.4.3 didn't fix it / didn't refresh the certificate. I ran docker exec appwrite ssl and it fixed the issue. _APP_ENV=production Thanks for a possible explanation.
One more thing - certificate was expired for around 2 weeks until I ran manual refresh today.
Anything in the docker logs for the certificates worker?
Thanks, Steven. After checking, there is this line in the log indeed: <SERVER PUBLIC IP> is not a publicly accessible domain. Skipping SSL certificate generation. IP listed is the same as current (and indeed publicly accessible), on which manual update through docker exec appwrite worked. Thanks for any hint, I'll dig into it also.
Hm, this warning only appears since my upgrade to 1.4.3 yesterday, nothing in the logs for the certificate / SSL / TLS / etc earlier that that.
how about the maintenance worker?
Recommended threads
- Impossible to create project via CLI?
Is it possible to create a new project via the appwrite CLI ? I need to create a few projects for something I'm working on and because i don't want to do it man...
- Understanding S3 setup with appwrite
Hey, i'm planning to change the storage from local to S3, tho i have some questions to see before starting the migration. 1. Does all the `/storage/<storage_ty...
- S3 files like health6a079a79afaa25.44072...
I migrated to another external S3 host for my appwrite and in many (but not all) folders a file (something like health6a079a79afaa25.44072323 - file itself is e...