Hi,
Quick note on the privacy first: this forum is public — sorry, we don't have a separate ticketing system at the moment. Private posts are reserved for Developer plan and above. For this thread, feel free to omit anything sensitive (server IPs, credentials, etc.) and we'll work around it.
On the ports:
Ports 80 and 443 on your Zeabur dedicated server are bound by the Zeabur ingress-controller — that's the component that routes HTTPS traffic from your *.zeabur.app domains and any custom domains into the right service pods. Releasing those ports would mean all of your other Zeabur services on the same server stop being reachable over HTTP/HTTPS.
To point you in the right direction — could you share what you're trying to do that needs 80/443 directly? Common cases and the usual answers:
- Running a separate web app / blog → expose it as a Zeabur service and bind a custom domain. The ingress-controller will keep handling 80/443 and route to your app — TLS cert handled for you. No need to take the ports back.
- Non-HTTP TCP service that has to be on 80 or 443 specifically → only path is to free up the ports, which means disabling Zeabur's ingress (significant downside; we'd talk you through implications first).
- Let's Encrypt HTTP-01 challenge for an external app → not needed if the cert is for a Zeabur-managed domain (Zeabur does this automatically).
Once we know the use case we can recommend the cleanest path.
