[SOLVED] web interface not reachable

lightmeupper

New Member
Dec 16, 2024
3
0
1
After 3 weeks of uptime, I added in extra network ports via web interface to run as slaves (to get more speed). Should have never done that. Now I cannot reach web interface from outside system itself.
How do I go back? I found some backups in /var/log/ifupdown2. They seem valid, and I think I got /etc/network/interface file restored.
# ip -a
shows all interfaces down. Is there other places where network info is stored?
 

Attachments

  • Screenshot from 2024-12-16 01-55-43.png
    Screenshot from 2024-12-16 01-55-43.png
    109.2 KB · Views: 15
Last edited:
Hi,

the the physical interface eno1 shows NO-CARRIER, meaning that no cable is connected, or not properly - thus there can also be no connection.

Have you tried reseating, trying a new cable?
 
Hi thanks for great tips!
I checked cable, looks good....
I did "loose" network right after a misconfiguration from the web panel in networking, so I assume its network config related.

The network setup should be basic. I have a network card with 4 ports. Probably not relevant. Not using port 2-4.

My /etc/network/interface file:

auto lo
iface lo inet loopback

auto eno1

auto vmbr0
iface vmbr inet static
address 172.24.8.33/26
gateway 172.24.8.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet manual

source /etc/network/interfaces.d/*
 
Last edited:
I also found this file: /etc/network/.pve-interfaces.lock (I see in the source code, not sure what it does)
It was created 5 days before my hangup started.

Also in /var/log/ifupdown2/***date***/interfaces.log shows:
main.py:85:main(): error main exception: No main ifaces found matching given allow lists

This is getting stranger by the hour

Resolved dec 17: :
Cisco switch shut down my ports. Was resolved by rectivating them from Cisco interface.
 
Last edited: