![]() ![]() Ifconfig inside the container shows I have an IPv4 address from Mullvad, which SABnzbd shows as the local IPv4 address I've restarted the container at least 20 times in the course of troubleshooting ![]() I've always used the Mullvad DNS servers, but have also tried 1.1.1.1,1.0.0.1 My binhex-deluge container has no problems, using the same VPN setup and I have no problems with any of my other containers or with the host I turned Debug logging on, but the logfile doesn't seems to be telling me anything:Ĭontainer has worked flawlessly until yesterday, though I probably hadn't used it in about a week before that SABnzbd "Status and Interface Options" screen says "Connection Failed!" for Public IPv4 address and Nameserver / DNS Lookup. I've spent about 2 hours on this and done a lot internet searching, but haven't found anyone having this problem recently. I just started having a DNS problem with this container and I've maxed out my limited Linux chops trying to figure it out. Just gets stuck in this restart loop.Īnyone know how to fix this? It was 100% working like a year ago with the same setup. If I add items to the queue after some idle time, it never reconnects. This was "fixed" by the user by routing through a privoxy container, but that cant be the only solution, right?Īfter restarting the container, everything works fine (as long as downloads are active). 10:44:31 SIGHUP received, process restarting 10:44:31 Network unreachable, restarting ![]() 10:44:31 write UDP: Network is unreachable (code=101) Part of the log after the internet is up: But I failed to find how to get them to work on privoxyvpn. I've tried sabnzbdvpn and nzbgetvpn, all giving me the same issue. Once the internet connection was down or it lost connection after being idle for some time, it wouldn't re-establish connection even when the internet was up or tasks were imported waiting for being downloaded. I hope these suggestions help you resolve the connectivity problems you are experiencing.After running a day, another problem came up. Remember to exercise caution when making changes to your system's security settings and consult official documentation or support channels for detailed instructions. They can provide further guidance and assistance specific to their products and services. It's possible that a recent update or configuration change might have affected the connectivity.Ĭontact Support: If the issue persists, it may be helpful to reach out to the support teams of Kaspersky, Sabnzbd, or Giganews. Double-check the server addresses, ports, usernames, passwords, and SSL settings if applicable. Sabnzbd and Giganews Settings: Review the settings in Sabnzbd and Giganews to ensure they are correctly configured. You can try restarting your router and other network devices to refresh the connections. Verify that your Wi-Fi connection to Google Nest and the network settings on your Synology are correct. Network Configuration: Ensure that your network connection is stable and properly configured. If the issue is resolved when Kaspersky is turned off, it indicates that the antivirus software is likely causing the problem. Temporary Disabling: As a temporary solution for troubleshooting purposes, you can try disabling Kaspersky antivirus and check if you can access Sabnzbd and connect to Giganews. You may need to whitelist or add exceptions for these applications to ensure they can establish connections. Look for any firewall or network-related settings that could be interfering with the connections. Kaspersky Settings: Check the settings of Kaspersky antivirus and make sure it is not blocking the connections to Sabnzbd or Giganews. Here are a few suggestions to troubleshoot the problem: ![]()
0 Comments
Leave a Reply. |