WebUI and SSH IPV4 not accesible - but able to connect with IPV6

Devilmac

New Member
Jun 11, 2024
4
0
1
Hello,

After rebooting the Proxmox shuddenly I cannot access through the IPV4 address but I am able to connect by the IPv6 address.

root@lab:~# pveversion
pve-manager/8.2.2/9355359cd7afbae4 (running kernel: 6.8.4-2-pve)

root@lab:~# cat /proc/sys/net/ipv6/bindv6only
0

root@lab:~# ss -tlpn
State Recv-Q Send-Q Local Address:port Peer Address:port Process
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=1321,fd=3))
LISTEN 0 4096 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=1147,fd=4),("systemd",pid=1,fd=36))
LISTEN 0 100 127.0.0.1:25 0.0.0.0:* users:(("master",pid=1464,fd=13))
LISTEN 0 4096 127.0.0.1:85 0.0.0.0:* users:(("pvedaemon worke",pid=1525,fd=6),("pvedaemon worke",pid=1524,fd=6),("pvedaemon worke",pid=1523,fd=6),("pvedaemon",pid=1522,fd=6))
LISTEN 0 4096 *:3128 *:* users:(("spiceproxy work",pid=1539,fd=6),("spiceproxy",pid=1538,fd=6))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=1321,fd=4))
LISTEN 0 4096 [::]:111 [::]:* users:(("rpcbind",pid=1147,fd=6),("systemd",pid=1,fd=38))
LISTEN 0 4096 *:8006 *:* users:(("pveproxy worker",pid=12946,fd=6),("pveproxy worker",pid=1534,fd=6),("pveproxy worker",pid=1533,fd=6),("pveproxy",pid=1531,fd=6))
LISTEN 0 100 [::1]:25 [::]:* users:(("master",pid=1464,fd=14))
 
Does the host IPv4 connection still work? Is there a firewall active?
 
Hello Kevin,
No firewall active. And the host is able to connect to others IPv4 services.
 
Have you tried pinging and a tcpdump to see if there's maybe a different ipv4 problem?

Since everything is working under ipv6 i don't see a reason why ssh/web service should be a problem.
try
Code:
curl https://localhost:8006 -k
to see if the web server is really just not working under ipv4

if not try to restart pveproxz and pvedaemon services and check again

Code:
systemctl restart pveproxy.service pvedaemon.service

Please check
Code:
journalctl -f
for any error messages.
 
Curl to localhost works.

This is my hosts file:

root@lab:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
172.17.30.120 lab.int lab

If I try to ping lab it doesnt work:

root@lab:~# ping 172.17.30.120
PING 172.17.30.120 (172.17.30.120) 56(84) bytes of data.
From 172.17.30.0 icmp_seq=1 Destination Host Unreachable
From 172.17.30.0 icmp_seq=2 Destination Host Unreachable
From 172.17.30.0 icmp_seq=3 Destination Host Unreachable
From 172.17.30.0 icmp_seq=4 Destination Host Unreachable


root@lab:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback
iface enp7s0 inet manual
iface enp4s0 inet manual
iface enp5s0 inet manual
iface enp6s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 172.17.30.0/24
gateway 172.17.30.100
bridge-ports enp7s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

auto vmbr0.80
iface vmbr0.80 inet static
address 192.168.80.0/24

source /etc/network/interfaces.d/*


Thanks for your help
 

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!