
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
- Images not showing up --
so i made this movie app - i hosted it successfully using appwrite but the images arent showing up --- https://movie-app-jsm.appwrite.network/ this is the movie...
- What’s the current approach for always o...
Read that it’s not a thing out of the box, but what’s the possible setup here?
- Error 431 header fields too large
Some times to times when i load or switch the page, it shows an error 431. And on what i saw it'w because of the cookies, when i remove the legacy tokens it wo...
