Problem accessing Proxmox GUI on remote site connected via Wireguard

sprickw

Member
Nov 1, 2020
24
1
8
Waldems, Germany
www.datagon.de
Yes, I did read the posts regarding Wireguard over here, but nothing seems to fit.

I connected two site with site-to-site wireguard, site A ist server, side B "client". Everything seems fine both directions. ping and ssh work. Even curl to the remote Proxmox GUI works:

curl -v http://192.168.0.201:8006
* Trying 192.168.0.201:8006...
* Connected to 192.168.0.201 (192.168.0.201) port 8006 (#0)
> GET / HTTP/1.1
> Host: 192.168.0.201:8006
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Cache-Control: max-age=0
< Connection: Keep-Alive
< Date: Thu, 15 Feb 2024 20:45:17 GMT
< Pragma: no-cache
< Location: https://192.168.0.201:8006/
< Server: pve-api-daemon/3.0
< Expires: Thu, 15 Feb 2024 20:45:17 GMT
* no chunk, no close, no size. Assume close to signal end
<
* Closing connection 0

But trying to connect to Proxmox GUI at site B with different browsers (Firefox, Chromium, Brave, Edge, Opera) get timeouts with http/https.

All firewalls at remote datacenter/Proxmox server are off.

Accessing the Proxmox server from local LAN works as expected. Even more weird: Access from site B to Proxmox GUI at site A works.

After spending a few hours on this I still have no idea.

Any hints?

Regards Wolfgang
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!