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
- Go 1.25 runtime
So I'm trying to use go 1.25 for my functions and I can only find go-1.23 as a function runtime. So I did some searching and found https://github.com/appwrite/a...
- Failed to generate functions SSL
```appwrite-worker-certificates | Cannot renew domain (functions.domain.com) on attempt no. 9 certificate: Failed to verify domain DNS records. appwrite-worker...
- Dart 3.10 runtime on self-host 1.8.1
I added dart-3.10 runtime in .env file, applied the changes, but cannot see such option on console. is dart 3.10 not supported by self hosted 1.8.1? if not, whe...