Access to second hostname in tunnel fails

What is the name of the domain?

svens.space

What is the error number?

Error code 502

What is the error message?

Bad gateway

What is the issue you’re encountering

I have configured a hostname on my Proxmox host that points to Proxmox itself - this works perfectly. (Thanks for that.) If I try to set up another hostname, the connection fails afterwards. No matter which IP or service I try to connect to.

What steps have you taken to resolve the issue?

I tried different IPs and ports.

What are the steps to reproduce the issue?

Setting up a second hostname in the tunnel.

Screenshot of the error

HTTPS seems to be the problem (even with no TLS verify). If I create a second hostname with HTTP, it works as expected. The ports on the hostnames are different.

Make sure to have SSL certificate for your hostname installed on the origin and Cloudflare IPs allowed (just in case if Proxmox doesn’t trust or cannot clearify the correct IP of the visitor, or by default is firewall/blocking mode enabled).

Nevertheless, tiwh TLS verify you could have HTTP on the origin, while HTTPS for the end-user (visitor).

May I ask over which ports you’ve configured Proxmox admin through the tunnel?
Only HTTP(S) traffic, correct?

Hello, thank you for your message. I made several mistakes based on incorrect assumptions. I thought that if I wanted my service to be accessible via HTTPS, I always had to specify this protocol. I didn’t know that Cloudflare does this automatically. In addition, the self-signed certificate was missing in one case. Everything is now working as it should - thank you for your offer of help. I hope you have a nice and relaxing Sunday.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.