November 15, 20169 yr THIS IS RESOLVED... I have documented in a later posts but in short PFSense was blocking internet to UnRaid due to the MAC address change. It was messing with me as my VM still had internet access as well as full LAN access.. I missed it. I forgot the basics of trouble shooting.. ________________ Will do my best to describe my issues. I am not entirely sure I understand what is happening right now though so feel free to ask questions. Was running 6.2.3 just upgraded to 6.2.4. I have Dockers and Windows VM. I replaced the Motherboard, CPU and RAM on the weekend. Everything went well and seemed to be working. Today I tried to access my plex docker via the internet and the server is missing. I remoted into VM and attempted to access the server and I could see Plex via local lan, but not via the internet. I have PFSense running and it was my first suspect. Plex is reporting that under network that is is accessible via the internet on the local admin page. Now I screwed up though. At one point it I tried to connect to plex and I selected to delete the server. I clicked ok. Now I cannot see the server at all locally or remotely. I cannot seem to find a way to re-register the server again within Plex. Any guess as to how to do this? The docker is still running just not registered with Plex I believe the overall issues is related to a change in network interfaces. I see in the plex docker log that is registering on some unknown IP's Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.1.3 on br0.IPv4. UnRaid is running on 192.168.1.3. The others are not used. I thought I better ask before I monkey with the network settings and wreck any more. A few other things I have noticed: Dockers will not update I am getting a Network timed out while trying to connect error Navigation seems slow moving between tabs in the Unraid manager Many many many thanks in advance for any direction, advice or questions that lead me in the right direction... Below is the PLEX Log and I have also attached the unraid logs. -------------------------------------------- ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... Atempting to upgrade to: wget: unable to resolve host address 'downloads.plex.tv' ######################################################## # Upgrade attempt failed, this could be because either # # plex update site is down, local network issues, or # # you were trying to get a version that simply doesn't # # exist, check over the VERSION variable thoroughly & # # correct it or try again later. # ######################################################## [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. 6 3000 /config/Library/Application Support d dbus[283]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.3. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.1.3 on br0.IPv4. Server startup complete. Host name is tower.local. Local service cookie is 1416527172. tower-syslog-20161115-1352.zip
November 15, 20169 yr Author Not making any progress. Realized I post just the logs and not the diags so attaching those now. Trying to figure out what the 'Registering new address record for 192.168.122.1 on virbr0.IPv4.' is why its coming up... More reading... Thanks for reading, Mike
November 16, 20169 yr Author Well break time for dinner and sports with the kids.. I think I might backtrack a little and attack a more describable problem as I am hopeful it is all related.Well that and I am lost... I cannot update my dockers - they all show as update ready (CP, Dolphin, DuckDNS, Plex, SAB, Sonarr). When I click the update bottom it goes to "Pulling Image" for about 30s or so then shows this: "Pulling image: linuxserver/couchpotato:latest TOTAL DATA PULLED: 0 B Error: Network timed out while trying to connect to https://index.docker.io/v1/repositories/linuxserver/couchpotato/images. You may want to check your internet connection or if you are behind a proxy." This is true of all the dockers with the same message.. The internet is working. I cannot see any filtering or blocking going on. I can access the server from other computers on the LAN. Its like unraid cannot hit the internet for some reason... Thoughts? Mike
November 16, 20169 yr Author Please mark as resolved..... If in doubt go back to the basics. In my last post I stated that the internet is working. Bad assumption on my part. I did a ping test from UnRaid - no DNS, no traffic outbound through PFSense. I am nota PFSense expert so it took me awhile to find some logging and errors related to UnRaid. Further digging - I had a static IP on UnRaid and a reservation in PFSense. PFsense did not like that an device using the assigned IP address was coming from a unknown MAC on the new Motherboard. I had already blown out the Network config on UnRaid by the time I figured it out. Thanks to all those that took the time to read. This in the end is not an UnRaid issue but network related.. It appears that things are mostly good. Side note. UnRaid does not run well when the internet is not working apparently. Eveything lags and it takes a lot of time to navigate the screens. Cheers, Mike
November 16, 20169 yr Side note. UnRaid does not run well when the internet is not working apparently. Eveything lags and it takes a lot of time to navigate the screens. It's probably your browser/desktop. I've worked with unRaid while I was taking my LAN apart, as long as the master internal DNS was down, things took forever to access. but once it was up, everything was smooth sailing.
November 16, 20169 yr Author Good call.. I have posted that I figured it out but your guess is on the right track.. PFSense was blocking Internet access due to a changed MAC address... I will update the OP so people don't need to waste more time.. Thanks for the reply! Side note. UnRaid does not run well when the internet is not working apparently. Eveything lags and it takes a lot of time to navigate the screens. It's probably your browser/desktop. I've worked with unRaid while I was taking my LAN apart, as long as the master internal DNS was down, things took forever to access. but once it was up, everything was smooth sailing.
Archived
This topic is now archived and is closed to further replies.