LumberJackGeek

Members
  • Content Count

    113
  • Joined

  • Last visited

Community Reputation

1 Neutral

About LumberJackGeek

  • Rank
    Member

Recent Profile Visitors

355 profile views
  1. It just happened again, this time in 5 days after a restart. This is very aggravating.
  2. dataserver2-diagnostics-20210215-1356.zip I launched the console right before collecting diagnostics, here is the error that I see in the syslog every time I try launching the console. Feb 15 13:56:36 Dataserver2 nginx: 2021/02/15 13:56:36 [error] 6076#6076: *3518011 connect() to unix:/var/run/ttyd.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.86.45, server: , request: "GET /webterminal/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "dataserver2", referrer: "http://dataserver2/Tools/Diagnostics" More detail
  3. I've tried this, the only fix is to reboot the server, and it will just happen again 2-4 weeks later and then I will have to reboot again, rinse, repeat, that seems to be the pattern now. I only access the server from 1 device.
  4. Bumping this, when it happens I also get an HTTP 502 - Bad Gateway error when I try using the console Every time I launch the console and it's broken and I Get the 502, this error is logged out in the logs: Jan 31 18:23:55 Dataserver2 nginx: 2021/01/31 18:23:55 [error] 13698#13698: *5011035 connect() to unix:/var/run/ttyd.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.86.45, server: , request: "GET /webterminal/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "dataserver2", referrer: "http://dataserver2/Dashboard" Jan 3
  5. Ahh so those endpoints do not support port forwarding? I suspect that's the issue others are hitting. I assumed (wrongly) since it was in that next-gen pack that meant it supported port forward Thanks for the info!
  6. Bump, still not having any luck with the next gen stuff
  7. I am also getting this. I tried both US Atlanta and US Florida, neither worked. What endpoint(s) have you tested that work for you? [warn] Unable to successfully download PIA json payload from URL 'https://10.13.112.1:19999/getSignature' using token
  8. Hi everyone, I noticed that today suddenly my CPU usage stopped showing up. It's been 69 days since my last unRAID system reboot, so that might fix it, but "netdata" docker still shows my CPU usage so this seems like something wrong with unRAID itself that caused it to stop rendering the data. Everything is always at 0% now.
  9. Ok so wait, I need to create a start.sh file, and place it in my /config directory, which is appdata/binhex-makemkv, and start.sh should have this in it? #!/bin/sh pacman -S --noconfirm usbutils pkill makemkv /home/root/start.sh & /home/root/start.sh & /home/root/start.sh &
  10. Hey I am trying to track down an issue with a tracker and announcements. How do I enable logging in Deluge via the docker? I tried adding this to the "Extra Paramters" via advanced view, but I keep getting that the path isn't found. I also tried enabling the "Debug" option in the actual docker, but from what I can telI can't get torrent log info? https://dev.deluge-torrent.org/wiki/Faq#HowdoIstartthedaemonwithloggingenabled '-d -L debug -l /mnt/user/appdata/binhex-delugevpn/logs' '-d -L debug -l /config/logs'
  11. Still no dice for me but maybe I am not trying the correct params?