Self Hosted

Certificate expired error (custom domain)

Dec 27, 2023, 18:56

View on Discord

Votes

Replies

Participants

Unknown

Messages

AlOriginal post

@everyone

Sep 21, 2023, 21:05

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.

Summary

There is an error with the certificate for a custom domain. The error may be caused by the domain not being publicly accessible. The user manually refreshed the certificate, but wonders if there should be an automatic job for this. Upgrading to a newer version did not fix the issue. The user resolved the issue by running the command "docker exec appwrite ssl".

@everyone

Sep 21, 2023, 21:09

One more thing - certificate was expired for around 2 weeks until I ran manual refresh today.

Drake

Sep 21, 2023, 21:32

Anything in the docker logs for the certificates worker?

@everyone

Sep 22, 2023, 06:12

Thanks, Steven. After checking, there is this line in the log indeed:
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.

@everyone

Sep 22, 2023, 06:28

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.

Drake

Sep 22, 2023, 17:59

how about the maintenance worker?

Join the discussion

Reply to this thread by joining our Discord.

Reply on Discord

Need support?_

Join Discord Get premium support