Node app deployed, but direct hostname uses a self-signed certificate
Warning recorded 1 times in PanelAlpha Engine deploys on Node.js. 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.
Seen1 times
WhereNode.js
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The application built and started successfully, and the health check reached it. The configured direct hostname could not be provisioned through PanelAlpha Online because the service has reached its site limit. Engine therefore served the hostname with a PanelAlpha self-signed certificate, which browsers will reject. The app also listened on port 8081 instead of the hinted port 3000; Engine forwarded traffic and confirmed a 404 response.
What the log looks like
Deploy log
Application is listening on port 8081, not 3000; forwarding there insteadHealth check: http://[ip]:3000/ answered HTTP 404Reachable: https://<account>.<host>/ answered 404 through the webserverDeploy finished with warnings: certificate browsers will refuse (self_signed, issued by PanelAlpha)PanelAlpha Online create failed: Sites limit reached for this service