Public hostname setup fails with TLS packet length too long when origin protocol is HTTPS on port 80

Location: ServerCompass > Finish public hostname setup > Cloudflare tunnel public hostname

Environment / setup from screenshot:
- Product: ServerCompass
- Flow: Finish public hostname setup
- Subdomain / hostname: 1dev.wpcteam.homes
- Cloudflare zone: wpcteam.homes
- Tunnel: servercompass-f0ad0794e09f
- App: interactive-comparison
- Service: interactive-comparison
- Container port: 80 (detected from Compose)
- Origin protocol selected: HTTPS
- Option enabled: Close direct server access after the tunnel works

Actual result:
ServerCompass cannot finish hostname setup and shows this error:

Could not finish hostname setup
Your app is not answering at sc-origin-852f6792:80: curl: (35) TLS connect error: error:0A0000C6:SSL routines::packet length too long

The tunnel itself appears healthy as an outbound connector, but validation fails at the origin health check.

Expected result:
ServerCompass should either:
1. detect that container port 80 is likely plain HTTP and default/suggest HTTP instead of HTTPS, or
2. show a clearer actionable message explaining that HTTPS + port 80 likely causes the TLS packet length error and the user should switch origin protocol to HTTP, or
3. validate the selected origin protocol against the detected Compose port before running the tunnel setup.

Steps to reproduce:
1. Open ServerCompass public hostname setup for an app detected from Compose.
2. Use container port 80.
3. Select origin protocol HTTPS.
4. Use a healthy Cloudflare tunnel and click setup/retry.
5. Observe the TLS error above.

Impact:
Hostname setup is blocked, even though the tunnel is healthy. The UI makes it look like the app is not answering, but the deeper cause appears to be protocol/port mismatch.