Go app deploys, but HTTPS uses a self-signed certificate
Warning recorded 2 times in PanelAlpha Engine deploys on Go. 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.
Seen2 times
WhereGo
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The application started and passed the container health check, but PanelAlpha Online could not create the site because the service has reached its site limit. The domain therefore used PanelAlpha's fallback certificate, which browsers reject as self-signed. The app also reported port 8443 while the detected port was 8080, so verify the configured listening port and health endpoint.
What the log looks like
Deploy log
Detected project type: GoUsing strategy: goDetected application port: 8080Application compiledStarting application (docker compose up -d)Application is listening on port 8443, not 8080; forwarding there insteadHealth check: http://[ip]:8080/ answered HTTP 400Deploy finished with warnings: https://<account>... is served a certificate browsers will refuse (self_signed, issued by PanelAlpha).PanelAlpha Online create failed: Sites limit reached for this service