Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Upgraded Server - Server Works Fine Locally but Can't See Outside World

Featured Replies

Upgrade to 7.2.1 from 7.0. Everything seemed to go smooth. Server just sat doing it's thing until I wanted to watch a show on my Emby. Normal I access it with a domain with rever proxy and all that. Has worked for over a year no issues. Could not access it. Tried to just run it with the local ip to the docker and worked fine. Jumped on server and noticed that APPS can't access the WWW either. It is looking like Everything works fine locally but the server itself can't access outside.

Fiber Modem/Router (AT&T) - Ethernet to Server. I use Cloudflare/Reverse Proxy to access my services. Again, haven't had any issues until after upgrading. I turned off Docker and VMs to see if it would make a difference; nothing. Attached is Diag.

I am not sure where to go from here on fixing this issue beside maybe downgrading back to 7.0.

cuddles-diagnostics-20251206-0043.zip

Solved by JorgeB

  • Community Expert
  • Solution

There are two gateways configured; only eth0/br0/bond0 should have a gateway. Remove the other one and retest.

  • Author

I am a beginner in a lot of this but after turning off VMs, Docker, and Wireguard I have this and still not working. Is there somewhere else I am supposed to make the change?

Network Settings - Routing Table

Edited by bitphire

  • Community Expert

You only need to remove it from the network settings.

  • Author

I'm in Settings -> Network Settings. for eth0 IPv4 default gateway is set. eth1 has same gateway as etho but is inactive, eth2 and eth3 are inactive with no gateway listed. Interface Extra br0 br1 are Current listening interfaces, include listening interface virbr0. Interface Rules just shows eth0-3 mac addresses. Routing table, see screenshot link in previous post.

I see at the bottom "Interface - Ethernet Port 1 is down. Check cable!" however, I only have 1 ethernet cable going to the server and it's on eth0. I believe wireguard setup the eth1.

I just don't know why my internet settings were changed during the upgrade. It's been working for a couple of years now with no issues.

ifconfig: 192.168.1.8 is the static ip of the server. 192.168.1.254 is the router/gateway.

bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        ether 24:6e:96:1d:4d:64  txqueuelen 1000  (Ethernet)
        RX packets 868292  bytes 83284768 (79.4 MiB)
        RX errors 0  dropped 30642  overruns 0  frame 0
        TX packets 116332  bytes 88937151 (84.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.8  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 24:6e:96:1d:4d:64  txqueuelen 1000  (Ethernet)
        RX packets 836716  bytes 69457429 (66.2 MiB)
        RX errors 0  dropped 3327  overruns 0  frame 0
        TX packets 69795  bytes 86384026 (82.3 MiB)
        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0
br-1851d5d79b78: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.21.0.1  netmask 255.255.0.0  broadcast 172.21.255.255
        inet6 fe80::42:4aff:feb1:9570  prefixlen 64  scopeid 0x20<link>
        ether 02:42:4a:b1:95:70  txqueuelen 0  (Ethernet)
        RX packets 199  bytes 11906 (11.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 404  bytes 125001 (122.0 KiB)
        TX errors 0  dropped 56 overruns 0  carrier 0  collisions 0
br-7092b668af83: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 172.20.255.255
        ether 02:42:23:dd:4d:54  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 295 overruns 0  carrier 0  collisions 0
br-859cc085c417: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255
        inet6 fe80::42:9eff:fe66:20bd  prefixlen 64  scopeid 0x20<link>
        ether 02:42:9e:66:20:bd  txqueuelen 0  (Ethernet)
        RX packets 7725  bytes 1069677 (1.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3494  bytes 573148 (559.7 KiB)
        TX errors 0  dropped 127 overruns 0  carrier 0  collisions 0
br-b70b924d0f34: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.31.200.1  netmask 255.255.255.0  broadcast 172.31.200.255
        ether 02:42:62:51:26:96  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 295 overruns 0  carrier 0  collisions 0
br-c4e2ba15c192: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.31.201.1  netmask 255.255.255.0  broadcast 172.31.201.255
        ether 02:42:3c:90:ba:6a  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 287 overruns 0  carrier 0  collisions 0
br-ed301ccddf5b: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:4b:13:4d:61  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 278 overruns 0  carrier 0  collisions 0
eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 24:6e:96:1d:4d:64  txqueuelen 1000  (Ethernet)
        RX packets 868292  bytes 83284768 (79.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 116332  bytes 88937151 (84.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xda680000-da6fffff  
eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 24:6e:96:1d:4d:65  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 22 overruns 0  carrier 0  collisions 0
        device memory 0xda700000-da77ffff  
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 3522  bytes 381900 (372.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3522  bytes 381900 (372.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vhost1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 02:15:b9:0d:da:81  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  • Author

Seems I had fixed it and did not even know it since docker and vms were turned off ><

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.