[SOLVED] Can no more access the Web GUI

[Eversman001]

Hello everyone,

I ran into the problem that I cannot access the web GUI anymore, which is probably linked to one or both below events:
I had to unplug and reconned all my internet ports on the switch and order is probably not the same anymore. But if I remember correctly everything still worked fine after that.
Later I had a general power outage and after the system rebooted I could not connect to the Web GUI anymore.
I usualy do access the Proxmox Web GUI on 192.168.129.40. But I saw that after rebooting the terminal said I could reach the GUI via 192.168.129.20.
Following that I set the etc/hosts from 192.168.129.20 to 192.168.129.40, but no success reaching the Web GUI.
Via SSH I can acces 192.168.129.40.

Below are my settings. I hope that someone can spot something in the configuration that might not be right. I am still quite new to all this...:

--> /etc/network/interfaces

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.129.40/24
        gateway 192.168.128.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

iface wlp0s20f3 inet manual

--> /etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.1.40 proxmox.local proxmox

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

--> ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 88:ae:dd:0f:1c:70 brd ff:ff:ff:ff:ff:ff
    altname enp2s0
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 3c:21:9c:87:cb:61 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 88:ae:dd:0f:1c:70 brd ff:ff:ff:ff:ff:ff
    inet 192.168.129.40/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::8aae:ddff:fe0f:1c70/64 scope link
       valid_lft forever preferred_lft forever

An on my router the device is recognized as follows:
192.168.129.40
88:ae:dd:0f:1c:70

I would appreciate your help a lot.

 

[Moayad]

Hi,

Did you check the syslog?

Can you ping 192.168.129.40?

 

[Eversman001]

Thank you for your reply.

After spending much more time searching the internet I could finally identify the source of the problem.

For those interested, the hint came from the following thread:
Thread_133914

In fact, after the power outage, the raid with the external hard drives didn't boot up. But I had my Proxmox already running again. This caused the backups being written automatically to the Proxmox local drive and not the external drives. It filled up the local drive completely and caused Proxmox to not function properly. I could still communicate with it over SSH but couldn’t access the web interface anymore. Once I freed up the disk and did a reboot everything was working again.
(Still there was probably something messed up with the IP configurations initially as Proxmox wanted me to connect to a different IP for the web interface, but I fixed this already before as described above).

In the end the trick is to activate the "is_mountpoint 1" on the directory storage used for backups as described in the thread. This prevents the backups from being written to the root drive once the external hard drive disconnects.