January 20, 20179 yr When using Fix Commom problems plugin, 1 error and 2 warning appear.... any idea for these?
January 20, 20179 yr Try this http://lime-technology.com/forum/index.php?topic=48508.msg465303#msg465303
March 14, 20179 yr Started seeing this recently, so happy to find a post about it until I followed the link to setting up the DNS servers with Google's. That doesn't really answer the issue. I run a DNS server on pfSense (firewall). It uses Google as it's forwarder. All my computers use my firewall's DNS server without issue. Also, I'm able to update plugins, install docker apps, update unraid, etc... so it's obviously able to resolve DNS. So what's the deal here? Thanks in advance, Adrian
March 14, 20179 yr The warning is from a failure to ping github.com Since plugins, etc all use github to pull from, possibly the issue is because if you're running pfSense as a VM on unRaid then it's not up and running when the plugin does its tests at boot up.... Either way, at the time of the test FCP was unable to ping github. Ignore it if you want....
March 14, 20179 yr 3 hours ago, Squid said: The warning is from a failure to ping github.com Since plugins, etc all use github to pull from, possibly the issue is because if you're running pfSense as a VM on unRaid then it's not up and running when the plugin does its tests at boot up.... Either way, at the time of the test FCP was unable to ping github. Ignore it if you want.... I run pfSense as a VM in VMWare and it's pretty much always up. Can I force this test? Is it the same as a rescan?
March 14, 20179 yr Just now, Squid said: Rescan will rerun all the tests. ok, well I ran that and the extended and it still reports the same issue. My DNS is definately up. I was also able to install 2 APPs that pull from github without any issues.
March 14, 20179 yr So ping resolves the name, and it transmits the packets, but 0 received. Mystery deepens....off to check the firewall, but it is able to resolve and download apps/updates.
March 14, 20179 yr 1 minute ago, Adrian said: So ping resolves the name, and it transmits the packets, but 0 received. Mystery deepens....off to check the firewall, but it is able to resolve and download apps/updates. Yeah, a ping was the simplest solution (and involved by far the least amount of overhead) in testing for connectivity. Sounds like you can safely ignore the error however if you can't figure out what pfSense is up to.
March 14, 20179 yr Mystery solved. It's a firewall rule I have to route traffic from unraid through a VPN. It was supposed to be disabled so I'm not sure how, but somehow it got enabled. Even though ping should be working through it, I guess something else is wrong. Maybe while it should utilize ping initially it could fallback to something else if ping fails just to make sure? Not a big deal, but you can see where it caused some confusion with what it was reporting and what everything else was showing was conflicting a bit.
November 7, 20187 yr Stumbled upon this, as I am having this issue and thought it might be related. Any help would be appreciated:
Archived
This topic is now archived and is closed to further replies.