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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

NAS is only reachable through home network, not through the internet

parazit
in General Support

Featured Replies

Hello everybody!

 

My Unraid NAS was working without any problems until yesterday and suddenly, i couldn't reach my docker containers through the internet anymore.

It looks like everything is working - docker containers are up and running, i can reach my files but only through my home network, not through the internet.

 

Unfortunately find a solution to this problem and wanted to ask in the forum.

 

Does anybody know, what could be the problem?

 

Unraid version: 6.11.5 (edit: updated to 6.12.3 - problem persists)

 

Jul 20 22:23:21 Unraid kernel: docker0: port 4(veth4b51b07) entered forwarding state
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface br-02641c16abe3.IPv6 with address fe80::42:c8ff:fe9b:27e.
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: New relevant interface br-02641c16abe3.IPv6 for mDNS.
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: Registering new address record for fe80::42:c8ff:fe9b:27e on br-02641c16abe3.*.
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface vethe2cd57e.IPv6 with address fe80::d4e2:c2ff:fe00:7fd4.
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: New relevant interface vethe2cd57e.IPv6 for mDNS.
Jul 20 22:23:21 Unraid  avahi-daemon[7805]: Registering new address record for fe80::d4e2:c2ff:fe00:7fd4 on vethe2cd57e.*.
Jul 20 22:23:21 Unraid rc.docker: mariadb: started succesfully!
Jul 20 22:23:21 Unraid kernel: docker0: port 5(vethc21bcf6) entered blocking state
Jul 20 22:23:21 Unraid kernel: docker0: port 5(vethc21bcf6) entered disabled state
Jul 20 22:23:21 Unraid kernel: device vethc21bcf6 entered promiscuous mode
Jul 20 22:23:21 Unraid kernel: docker0: port 5(vethc21bcf6) entered blocking state
Jul 20 22:23:21 Unraid kernel: docker0: port 5(vethc21bcf6) entered forwarding state
Jul 20 22:23:22 Unraid kernel: docker0: port 5(vethc21bcf6) entered disabled state
Jul 20 22:23:22 Unraid kernel: eth0: renamed from veth38e0a0e
Jul 20 22:23:22 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc21bcf6: link becomes ready
Jul 20 22:23:22 Unraid kernel: docker0: port 5(vethc21bcf6) entered blocking state
Jul 20 22:23:22 Unraid kernel: docker0: port 5(vethc21bcf6) entered forwarding state
Jul 20 22:23:22 Unraid rc.docker: Redis: started succesfully!
Jul 20 22:23:22 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered blocking state
Jul 20 22:23:22 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered disabled state
Jul 20 22:23:22 Unraid kernel: device veth3b5b586 entered promiscuous mode
Jul 20 22:23:22 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered blocking state
Jul 20 22:23:22 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered forwarding state
Jul 20 22:23:22 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface veth4b51b07.IPv6 with address fe80::7849:bff:fe55:cf65.
Jul 20 22:23:22 Unraid  avahi-daemon[7805]: New relevant interface veth4b51b07.IPv6 for mDNS.
Jul 20 22:23:22 Unraid  avahi-daemon[7805]: Registering new address record for fe80::7849:bff:fe55:cf65 on veth4b51b07.*.
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered disabled state
Jul 20 22:23:23 Unraid kernel: eth0: renamed from veth2b1e54e
Jul 20 22:23:23 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3b5b586: link becomes ready
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered blocking state
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 2(veth3b5b586) entered forwarding state
Jul 20 22:23:23 Unraid rc.docker: nextcloud: started succesfully!
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered blocking state
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered disabled state
Jul 20 22:23:23 Unraid kernel: device vethced977a entered promiscuous mode
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered blocking state
Jul 20 22:23:23 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered forwarding state
Jul 20 22:23:24 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered disabled state
Jul 20 22:23:24 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface vethc21bcf6.IPv6 with address fe80::1ce3:f6ff:fe57:b05a.
Jul 20 22:23:24 Unraid  avahi-daemon[7805]: New relevant interface vethc21bcf6.IPv6 for mDNS.
Jul 20 22:23:24 Unraid  avahi-daemon[7805]: Registering new address record for fe80::1ce3:f6ff:fe57:b05a on vethc21bcf6.*.
Jul 20 22:23:24 Unraid kernel: eth0: renamed from vethec4677f
Jul 20 22:23:24 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethced977a: link becomes ready
Jul 20 22:23:24 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered blocking state
Jul 20 22:23:24 Unraid kernel: br-02641c16abe3: port 3(vethced977a) entered forwarding state
Jul 20 22:23:25 Unraid rc.docker: OnlyOfficeDocumentServer: started succesfully!
Jul 20 22:23:25 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered blocking state
Jul 20 22:23:25 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered disabled state
Jul 20 22:23:25 Unraid kernel: device veth3a3f803 entered promiscuous mode
Jul 20 22:23:25 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered blocking state
Jul 20 22:23:25 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered forwarding state
Jul 20 22:23:25 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered disabled state
Jul 20 22:23:25 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface veth3b5b586.IPv6 with address fe80::8886:23ff:fe26:468b.
Jul 20 22:23:25 Unraid  avahi-daemon[7805]: New relevant interface veth3b5b586.IPv6 for mDNS.
Jul 20 22:23:25 Unraid  avahi-daemon[7805]: Registering new address record for fe80::8886:23ff:fe26:468b on veth3b5b586.*.
Jul 20 22:23:26 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface vethced977a.IPv6 with address fe80::2441:26ff:fe6e:7e1.
Jul 20 22:23:26 Unraid  avahi-daemon[7805]: New relevant interface vethced977a.IPv6 for mDNS.
Jul 20 22:23:26 Unraid  avahi-daemon[7805]: Registering new address record for fe80::2441:26ff:fe6e:7e1 on vethced977a.*.
Jul 20 22:23:27 Unraid kernel: eth0: renamed from vethda209d1
Jul 20 22:23:27 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3a3f803: link becomes ready
Jul 20 22:23:27 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered blocking state
Jul 20 22:23:27 Unraid kernel: br-02641c16abe3: port 4(veth3a3f803) entered forwarding state
Jul 20 22:23:27 Unraid rc.docker: transmission: started succesfully!
Jul 20 22:23:28 Unraid kernel: atlantic 0000:04:00.0 eth0: atlantic: link change old 0 new 10000
Jul 20 22:23:28 Unraid kernel: br0: port 1(eth0) entered blocking state
Jul 20 22:23:28 Unraid kernel: br0: port 1(eth0) entered forwarding state
Jul 20 22:23:29 Unraid  avahi-daemon[7805]: Joining mDNS multicast group on interface veth3a3f803.IPv6 with address fe80::1871:4ff:fe78:26bb.
Jul 20 22:23:29 Unraid  avahi-daemon[7805]: New relevant interface veth3a3f803.IPv6 for mDNS.
Jul 20 22:23:29 Unraid  avahi-daemon[7805]: Registering new address record for fe80::1871:4ff:fe78:26bb on veth3a3f803.*.
Jul 20 22:23:30 Unraid kernel: atlantic 0000:04:00.0 eth0: atlantic: link change old 10000 new 0
Jul 20 22:23:30 Unraid kernel: br0: port 1(eth0) entered disabled state
Jul 20 22:23:33 Unraid  ntpd[1124]: Deleting interface #2 br0, 192.168.178.28#123, interface stats: received=24, sent=24, dropped=0, active_time=63 secs
Jul 20 22:23:33 Unraid  ntpd[1124]: 216.239.35.0 local addr 192.168.178.28 -> <null>
Jul 20 22:23:33 Unraid  ntpd[1124]: 216.239.35.4 local addr 192.168.178.28 -> <null>
Jul 20 22:23:33 Unraid  ntpd[1124]: 216.239.35.8 local addr 192.168.178.28 -> <null>
Jul 20 22:23:33 Unraid  ntpd[1124]: 216.239.35.12 local addr 192.168.178.28 -> <null>
Jul 20 22:23:45 Unraid kernel: atlantic 0000:04:00.0 eth0: atlantic: link change old 0 new 10000
Jul 20 22:23:45 Unraid kernel: br0: port 1(eth0) entered blocking state
Jul 20 22:23:45 Unraid kernel: br0: port 1(eth0) entered forwarding state
Jul 20 22:23:45 Unraid unassigned.devices: Using Gateway '192.168.178.1' to Ping Remote Shares.
Jul 20 22:23:45 Unraid unassigned.devices: Waiting 5 secs before mounting Remote Shares...
Jul 20 22:23:46 Unraid  ntpd[1124]: Listen normally on 3 br0 192.168.178.28:123
Jul 20 22:23:46 Unraid  ntpd[1124]: new interface(s) found: waking up resolver

unraid-diagnostics-20230720-2241.zip

Edited by parazit

  • Quote

    Du you have a NAT (Port-forwarding) rule in your Router that allows access from the Internet?

  • Quote
    • Author
    12 minutes ago, Jaeggrono said:

    Du you have a NAT (Port-forwarding) rule in your Router that allows access from the Internet?

    yes i do. I checked them and they are still the same.

  • Quote

    • 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...
    Go to topic listing

    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.