[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"problem-detail-warning-go-app-deploys-but-https-uses-a-self":3},{"stack":4,"error":5,"seoName":6,"seoStack":7,"seo":8,"breadcrumb":10,"titlePrefix":17,"titleAccent":6,"lead":18,"facts":21,"why":36,"log":41,"fix":82,"engine":96,"related":103,"pitch":114},"go","go-app-deploys-but-https-uses-a-self","Go app deploys, but HTTPS uses a self-signed certificate","Go",{"description":9},"Learn what causes Go app deploys, but HTTPS uses a self-signed certificate, how PanelAlpha Engine responds to it during deployment.",[11,14,16],{"label":12,"href":13},"App Installations","\u002Fapps",{"label":7,"href":15},"\u002Fapps\u002Fstacks\u002Fgo",{"label":6},"",[19],{"text":20},"Warning recorded 2 times in PanelAlpha Engine deploys on Go. The deploy log below is the recorded failure output.",[22,27,30,32],{"label":23,"value":24,"tone":25,"tooltip":26},"Type","Warning","warn","An 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.",{"label":28,"value":29},"Seen","2 times",{"label":31,"value":7},"Where",{"label":33,"value":34,"tooltip":35},"Status","Observed","Our team will look into this soon, verify the cause and try to fix it in an upcoming release.",{"heading":37,"body":38},"Why it happens",[39],{"text":40},"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.",{"heading":42,"block":43},"What the log looks like",{"header":44,"lines":45},"Deploy log",[46,50,54,58,62,66,70,74,78],{"segments":47},[48],{"text":49},"Detected project type: Go",{"segments":51},[52],{"text":53},"Using strategy: go",{"segments":55},[56],{"text":57},"Detected application port: 8080",{"segments":59},[60],{"text":61},"Application compiled",{"segments":63},[64],{"text":65},"Starting application (docker compose up -d)",{"segments":67},[68],{"text":69},"Application is listening on port 8443, not 8080; forwarding there instead",{"segments":71},[72],{"text":73},"Health check: http:\u002F\u002F[ip]:8080\u002F answered HTTP 400",{"segments":75},[76],{"text":77},"Deploy finished with warnings: https:\u002F\u002F\u003Caccount>... is served a certificate browsers will refuse (self_signed, issued by PanelAlpha).",{"segments":79},[80],{"text":81},"PanelAlpha Online create failed: Sites limit reached for this service",{"heading":83,"steps":84,"block":93},"How to fix it",[85],[86,88,91],{"text":87},"Free capacity by removing an unused site or increasing the service site limit. Confirm the domain resolves to this host, then request a certificate with ",{"text":89,"code":90},"ssl:project-cert:request",true,{"text":92},". Review the Go app's port configuration and set the deployment port to the port it actually serves, if needed. The HTTP 400 health response should also be checked against the app's expected health route.",{"header":94,"lines":95},"Fix by hand",[],{"heading":97,"body":98,"block":101},"How PanelAlpha Engine solves it",[99],{"text":100},"When site creation fails because the service limit is reached, Engine should clearly mark the deployment as fallback TLS rather than a normal successful domain setup. It should also reconcile the detected port with the runtime port before health checks and surface the port mismatch as a separate warning. The permission-denied log warning should be retained with an actionable explanation.",{"header":17,"lines":102},[],{"heading":104,"items":105},"Apps affected",[106,111],{"title":107,"badge":108,"tone":109,"href":110},"graphql-go","1 occurrence","err","\u002Fapps\u002Fgraph-gophers\u002Fgraphql-go",{"title":112,"badge":108,"tone":109,"href":113},"jaeger","\u002Fapps\u002Fjaegertracing\u002Fjaeger",{"heading":115,"body":116,"footNote":117,"docsLabel":118,"docsHref":119},"Try PanelAlpha Engine yourself.","The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.","Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPU","Read the documentation","https:\u002F\u002Fpanelalpha.com\u002Fdocs"]