![proxmox web interface port proxmox web interface port](https://hostbillapp.com/appstore/hosting_proxmox2/images/vmdetails.png)
I will however link to the corresponding git commits. Because I’m looking at the source for the modules, I wont quote line numbers as they will likely change over time. At the time of writing, I was using Proxmox 5.2 for my testing.
![proxmox web interface port proxmox web interface port](https://www.linuxbabe.com/wp-content/uploads/2020/08/proxmox-web-interface.png)
In order to figure this one out, I had to dig into the supplied perl modules for Proxmox. Leaving bindv6only disabled (default) is my preferred choice here as this would affect more than just Proxmox for me. If this is enabled then the socket would only work for IPv6 addresses and applications would have to specifically bind to both v4 and v6 address families independently, depending on which they want to support. Specifically, this depends on the value of bindv6only in sysctl. By changing the family to v6, enables it to work for both families, primarily because of how the OS is configured. How pveproxy chooses which family to use…īy default, pveproxy decides to bind to an IPv4 family socket. Viola – The Proxmox Web interface should work on both IPv4 and IPv6. This tells the OS that its an IPv6 address – but its a special IPv4-mapped-IPv6 address. Restart the pveproxy service and you should now see it binds to an IPv6 socket tcp6 0 0 :::8006 :::* LISTEN. We start with (for example) 10.0.0.100 pvehost pvelocalhostĪnd we should change it to ::ffff:10.0.0.100 pvehost pvelocalhostĪll we’ve done here is add ::ffff: before the IP address of our node. In order to change this we need to edit our /etc/hosts file and change the line which identifies our Proxmox host Pveproxy seems to rely on the contents of /etc/hosts in order to figure out what address family to use when binding port 8006 (the default GUI port).
#Proxmox web interface port how to#
If you’re just here to see how to do it, check below. This post is going to spend most of its time explaining why this happens rather than the fix. This stumped me for a little while, but its pretty simple to fix when you know whats going on. As part of my recent (and ongoing) project to implement native IPv6 on my own infrastructure (except at home… I’m looking at you Hyperoptic), I decided to try to dual-stack as much as possible so that when I have IPv6 connectivity, services would prefer that over IPv4, without making things unavailable.Īs it turns out, Proxmox’s Web interface (pveproxy) doesn’t listen on the IPv6 address family by default.