Site works, but its HTTPS certificate is self-signed
Warning recorded 68 times in PanelAlpha Engine deploys on Docker Compose, Dockerfile, Laravel and more. 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.
Seen68 times · 8 variants
WhereDocker Compose, Dockerfile, Laravel +3 moreDocker Compose, Dockerfile, Laravel, Php, Rust, Static 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
Build finished successfully:#23 exporting to image#23 naming to docker.io/library/project-app:latest doneHealth check: HTTP 200 on port 8080PanelAlpha Online create failed: Sites limit reached for this service (HTTP 200)The site is served with a self-signed certificate issued by PanelAlpha.