[SOLVED] Unable to Communicate with Github (OS running slow with network issues)

[nationapn]

Help me unRAID gurus; you're my only hope! 

 

I am running unRAID 6.8.3 as a relative novice (lots of SpaceInvaderOne videos).  It's been working reliably until we had a thunderstorm last night that knocked out power.  Fortunately, my computer/array seem fine...I am running a UPS that shut down the system gracefully.  However, I now have an "Unable to Communicate with Github error, my dockers won't update, and particular services (like Plex) are only accessible from the LAN.  I have reset my router (and noticed my IP address changed...I manually changed it to match on duckdns.org (even though the client is supposed to do that automatically).  I have tried multiple solutions recommended on various threads (double-checking DHCP set to yes in network cfg file, changing DNS to 8.8.8.8 and 8.8.4.4, etc., but I am out of ideas.  I very much appreciate any help those more unRAID savvy than I can provide.  NOTE: I run a reverse proxy with custom: proxynet and point ports 443 and 80 to 446 and 81, respectively, for letsencrypt.

[nationapn]

Sooo, I was able to fix my own problem, but it wasn’t particularly easy...I’ll post the solution here in case anyone else experiences the same issue in the future.

 

After lots of troubleshooting, I was convinced my server config was ok.  Though I had rebooted the router, I had not yet reset it to factory settings.  That did the trick.  Of course, then I had to completely re-do port forwarding.  Also, I had a new LAN IP for the unRAID server, so I had to reconfigure many of my docker apps that used APIs to communicate with one another (Lidarr, Radarr, Sonarr, Deluge, Sab, Organizr, etc).

 

All good now, but it would have been nice to have that Friday evening back!