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
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- No Document ID?
Hi I have a self hosted appwrite. My documents get a document ID but are not visible in the console. I don't know why this happens and how to fix this
- How to determine if a user is anonymous?
This is probably a silly question, but I have not yet found a good answer. Is there a method to determine if the current session is anonymous aside from seein...