search

tom472 / mediabox

Container based media tools configuration
MIT License
428 stars 83 forks source link

deluge UI no longer accessible #109

Closed willstoeckel closed 3 years ago

willstoeckel commented 3 years ago

I'm getting a refused to connect error when trying to launch the deluge UI. I verified I had the latest code with a git pull and reran the mediabox.sh script. I tried selecting a different openvpn server as well. I checked that the process is running and there is a listener on tcp 8112. Platform is Ubuntu 18.04.5 LTS. Let me know if there any specific log files I can attach.

Bramblefoot commented 3 years ago

Look specifically at the logs for that container in portainer. Whenever deluge goes down for me, it's PIA and their exit node not port forwarding properly. Hope this helps.

Bill "Try not. Do, or do not. There is no try." - Yoda

On Sat, Sep 19, 2020, 1:52 PM willstoeckel notifications@github.com wrote:

I'm getting a refused to connect error when trying to launch the deluge UI. I verified I had the latest code with a git pull and reran the mediabox.sh script. I tried selecting a different openvpn server as well. I checked that the process is running and there is a listener on tcp 8112. Platform is Ubuntu 18.04.5 LTS. Let me know if there any specific log files I can attach.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tom472/mediabox/issues/109, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4VDLPMZVZO36LYAHCUIUDSGT4VNANCNFSM4RTFOBCQ .

willstoeckel commented 3 years ago

Thanks Bill. Did some digging and it does look like it's an issue with the PIA node. Maybe I'll see if I can manually edit or use their auto-generated config file. , 2020-09-19 16:55:54,904 DEBG 'start-script' stdout output:, [warn] Exit code '56' from curl != 0 or no response body received, [info] 1 retries left, [info] Retrying in 10 secs..., , 2020-09-19 16:56:06,260 DEBG 'start-script' stdout output:, [warn] Exit code '56' from curl != 0 or no response body received, exhausted retries, [warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz', exiting script..., , 2020-09-19 16:56:06,260 DEBG 'start-script' stdout output:, [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port..., , 2020-09-19 16:56:06,261 DEBG 'start-script' stdout output:, Sat Sep 19 16:56:06 2020 event_wait : Interrupted system call (code=4), , 2020-09-19 16:56:06,267 DEBG 'start-script' stdout output:, Sat Sep 19 16:56:06 2020 /usr/bin/ip addr del dev tun0 local 10.61.11.6 peer 10.61.11.5, , 2020-09-19 16:56:06,286 DEBG 'start-script' stdout output:, Sat Sep 19 16:56:06 2020 SIGINT[hard,] received, process exiting, , 2020-09-19 16:56:14,259 DEBG 'start-script' stdout output:, [warn] OpenVPN process terminated, restarting OpenVPN...,

willstoeckel commented 3 years ago

The only way I was able to get this to work was to edit the docker-compose.yml file and set VPN_ENABLED=no in the deluge section. I can use PIA VPN on the server itself but then that breaks the plex remote access. I'd rather just keep it split-tunneled to deluge if possible.

Bramblefoot commented 3 years ago

In my experience, It's just a reality with PIA. Their port forwarding goes down occasionally. And when that happens it affects deluge. I've found no solution and just have to ride it out when it happens. And once the PIA port forwarding comes back up, deluge just starts working again. Fortunately I rely more on usenet than torrents.

Good luck. Bill

"Try not. Do, or do not. There is no try." - Yoda

On Sat, Sep 19, 2020, 7:57 PM willstoeckel notifications@github.com wrote:

The only way I was able to get this to work was to edit the docker-compose.yml file and set VPN_ENABLED=no in the deluge section. I can use PIA VPN on the server itself but then that breaks the plex remote access. I'd rather just keep it split-tunneled to deluge if possible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tom472/mediabox/issues/109#issuecomment-695399408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4VDLJZSJTSSOT34HYSSWTSGVHP3ANCNFSM4RTFOBCQ .

willstoeckel commented 3 years ago

Thanks Bill. I found this update from PIA so it does look like it's the port forwarding. Leaving it here in case anyone else comes along with the same problem: https://www.privateinternetaccess.com/helpdesk/news/posts/important-updated-server-changes-and-related-issues

tom472 commented 3 years ago

Just an FYI - for all -- You can easily re-run .\mediabox/sh to choose / select a different PIA server when a location is having a Port-Forward issue.