Can't Connect to GUI

looski

New Member
Feb 15, 2026
2
0
1
Hello!

So I'm a hobbyist, just find it fun to have a home server. I am not versed in networking. I have been working on this for hours now and I feel I have exhausted what google has provided. I have a Ubiquity router in case that matters. It states that the ip range is 192.168.1.6 - 192.168.1.254. I have tried selecting an ip outside the range and inside the range, 192.168.1.5 and 192.168.1.15 respectively. I have the server pc hard-wired into a switch which runs a cord to my router.
 

Attachments

  • signal-2026-02-15-160644.jpeg
    signal-2026-02-15-160644.jpeg
    233.9 KB · Views: 7
  • signal-2026-02-15-160641.jpeg
    signal-2026-02-15-160641.jpeg
    135.2 KB · Views: 7
Hi,

as visible on the pictures, the physical interface nic0 (and thus the connected bridge vmbr0) is marked as NO-CARRIER.
This means that no cable connection was detected. Have you tried another cable/switch port?
You can try checking the system journal and/or kernel log for errors, e.g. the output of journalctl -b | grep nic0 might be helpful as a start.
 
oh goodness... The cat cable wasn't pushed all the way in. I'm sorry. Not your realm of expertise... but does anyone know why a windows 10 pc can't connect to the lan. I can't connect to my server, nas or router. My macbook can connect to everything