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
- MCP server not able to do list documents...
I recommend the MCP server be updated. I know there are a lot of changes to the API but SOTA models have hard time doing a simple list documents with a simple q...
- Why TablesDB ListRows function does not ...
When I try to list the rows with queries, there is no column data included in the returned value with forced me to fetch the items one-by-one with ID (which was...
- 404 Error on Self Hosted instance
I have a 404 page not found error when I want to access my console 😢 I am on Ubuntu 24.04.3 LTS and I just do a `apt update` and `apt upgrade` and after a reb...