[solved]Are duplicate hostnames an issue? Can't connect to a local address over http

Started by Sunshine, February 21, 2025, 10:42:52 PM

Previous topic - Next topic
I'm having trouble accessing a proxmox interface on a machine that is different what OPNsense is running on. I can however, connect to the VMs that are on this particular machine. Probably best described with the pictures. The clients can connect to the green lines, but not the red.
OPNsense is able to ping proxmox though and appears to be giving it the appropriate reserved address.

The only thing I can think if is that both proxmox instances were set up with the default hostname of "pve", and some searching is implying that changing one is not a trivial task.

It seems like a proxmox issue, but this only occurs when running OPNsense. If I spin up a different firewall, I can access everything without issue. I recall running OPNsense about 5 or 6 years ago on this same hardware config and never had issues, so i'm assuming it's a simple setting I'm overlooking.

-----------------

Changing the hostname did not fix this issue. I discovered that the problematic proxmox node was configured as 192.168.1.10/32. Changing it to /24 subnet (the same as the node OPNsense is on) seems to have solved it, and I can now access the gui. The previous version of OPNsense and a few other firewalls I've used all seem to be fine with /32 though.



Quote from: Sunshine on February 21, 2025, 10:42:52 PMOPNsense is able to ping proxmox though and appears to be giving it the appropriate reserved address.
The Proxmox host in question is getting its IP from the DHCP server on OPNsense?
Otherwise check its network settings.

Quote from: viragomann on February 21, 2025, 11:13:17 PM
Quote from: Sunshine on February 21, 2025, 10:42:52 PMOPNsense is able to ping proxmox though and appears to be giving it the appropriate reserved address.
The Proxmox host in question is getting its IP from the DHCP server on OPNsense?
Otherwise check its network settings.

Yes, I believe it is. It has a reservation outside of the dynamic range. When I plug a monitor into the machine in question, it's prompting to connect and configure at 192.168.1.10 as I would expect.
I am just noticing that status icon is indicating offline, yet the vms on the same bridge are showing online.


I've renamed my Proxmox nodes early. It was not difficult. It appears to be more involved with containers present...

Look at your hosts file (ssh on under System > Hosts). There's typically an entry for the host itself (on top of localhost).
You have to mess with /etc/interfaces to get Proxmox to obtain an IP via DHCP.
But then, if you use a DHCP reservation, I'm not sure why you bother... You might as well stick with the recommendation of using static IPs.
Just adjust your DHCP pool to not include the static IPs.

You don't really specify how you try to access the top host. ssh or GUI? by IP?