drfsrich

Members
  • Posts

    2
  • Joined

  • Last visited

drfsrich's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Running into an issue where I can't access the WebUI since at least yesterday. I have been able to access the WebUI within the last 2 weeks or so. Unraid 6.9.2, latest version of the container. When I try to connect to the IP:8112 I get "the connection was reset" in Firefox/Chrome (from two different machines). No obvious errors in logs: "2021-12-21 06:48:58,406 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2021-12-21 06:48:58,406 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2021-12-21 06:48:58,420 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-12-21 06:48:59,441 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-12-21 06:48:59,453 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 " ifconfig on the container shows tun0 up and passing a small amount of data. (<100mb). Plex has new content delivered via this in the last day. The last entry in supervisord.log is "2021-12-21 07:44:33,369 DEBG 'start-script' stdout output: 2021-12-21 07:44:33 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2021-12-21 07:44:33 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2021-12-21 07:44:33 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA2" I'm stuck -- Any suggestions as to what to look at next? Thanks!
  2. Ran into the "No Soup For You" error with inability to access the server from anywhere. Tried a couple of things but my eventual fix was in the Preferences.xml . For some reason my allowed IP range showed 192.168.0/255.255.255.0. I modified it to 192.168.0.1/255.255.255.0,, restarted the container and I'm back in.