Back
Function certificates are all self-signed on production. Is this by design?
I'm currently testing out a selfhosted production instance. As I understood / expected, after reading the documentation, the certs should be automatically generated. The interface also displays the status 'verified' and 'generated'. But Appwrite serves me the TRAEFIK DEFAULT CERT. Using a custom domain for the function will generate a valid cert.
- Is it by design that the
[function-hash].[domain]URL's are not supplied with signed certs? - In my setup the APP_DOMAIN is already hosted under a subdomain. Could the format
[function-hash].api.domain.comcause the issue?
TL;DR
- Developers testing self-hosted production instance notice self-signed certificates for function URLs
- Default behavior; valid certificates generated only when using custom domains for functions
- Question about potential issue with using `[function-hash].api.domain.com` format
Solution:
- Custom domains required for valid certificates on function URLs in production instances