Site works, but its HTTPS certificate is self-signed
Warning recorded 10 times in PanelAlpha Engine deploys on Static site. The deploy log below is the recorded failure output.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen10 times
WhereStatic site
StatusResolve ReadyOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The engine serves a self-signed certificate until a real one is requested for the domain. By default it does not request one from Let's Encrypt automatically, and it never retries on its own, so browsers show a certificate warning.
What the log looks like
Deploy log
Starting application (docker compose up -d)Health check: http://[ip]:8080/ answered HTTP 200Reachable: http://<account>.<ip>.sslip.io/ answered 200 through the webserverDeploy finished with warnings: certificate browsers will refuse (self_signed, issued by PanelAlpha)