SgtSeamonkey

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SgtSeamonkey

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, the issue is now resolved and I don't think it was an issue with my VPN, I think it was a Plex issue. Upon returning home I had the same issue until I updated PlexPass to the latest version. After that I was able to see and claim my server. It was still a little finicky, I jumped back and forth between plex.tv and the local address webpages. Refreshing and logging in a few times. Eventually I was able to claim the server and everything is now back to normal. I did not have to change any settings.
  2. Totally identical. No different than using the direct address over VPN.
  3. Alright, I'm back with another issue and it's certainly a misunderstanding on my part that has caused it. My ISP recently changed my IP address and I didn't recognize it - I thought I was hacked therefore I changed my Plex password and force logged-out all devices. I also updated to the latest Plex version. Logging in seemed to work with the new password so I looked no deeper and went out of town on a business trip. Now I'm sitting in the hotel room trying to connect and unable to. I assumed I had to disconnect and re-claim my server so I logged into my VPN - I now have full access
  4. Update 1/28/21: New PSU is installed. Haven't tested extensively but I ran two movies at once on different platforms through Plex, transcoding both, for ~20min. Did not see a crash. I'm fairly confident this was the issue after watching my UPS display occasional spikes of ~260w while I was testing.
  5. Sorry, I meant that PCPP estimates my full build will consume around 244w. I just did some research and realized that my PSU was the stock one that came with my case (IP-S265AU7-2) - it's a crappy 265w Bronze that I probably intended to upgrade and forgot about. I just purchased a 500w Gold (SS-500L1U). I'll report back here when it arrives and I install it. I suspect you're correct, the PSU is likely my issue which would explain my brown-out type shutdown during high CPU loads.
  6. For anyone else who might be following this or for future search help I will update with my findings: Response on Plex app support thread: "this sounds to me like a hardware issue, my guess would be memory or psu but a full diagnostics dump may tell you what the cause is, you are best off posting in general support as this wont be related to this docker image and there are people with more systems knowledge than me on there, link to general:- https://forums.unraid.net/forum/55-general-support/" Diagnostic logs appear to start from the first startup after the crash - no
  7. Yeah, I tried general support first and got no response. My initial thought was hardware, possibly power draw or thermals but I couldn't find any issues. I will look into the full diagnostic dump. Thank you for the response! Update 1/28/21 - Looks like the issue was the power supply. Haven't tested extensively but during initial testing after upgrading PSU I have not yet seen the issue.
  8. I've been inconsistently crashing while watching movies through Plex. I'm not sure the extent of the crash, I lose connection to my server, run downstairs to check it and it's still powered on. By the time I return upstairs the connection is restored but the array is stopped. Happens inconsistently. I watched multiple episodes of a TV show in a row multiple nights in a row without issue. Sometimes I can watch an entire movie, other times I can only watch minutes. Turned on Syslog mirror to flash but I'm not sure what to look for, nothing is standing out. I recent
  9. I've been inconsistently crashing while watching movies through Plex. I'm not sure the extent of the crash, I lose connection to my server, run downstairs to check it and it's still powered on. By the time I return upstairs the connection is restored but the array is stopped. Happens inconsistently. I watched multiple episodes of a TV show in a row multiple nights in a row without issue. Sometimes I can watch an entire movie, other times I can only watch minutes. Turned on Syslog mirror to flash but I'm not sure what to look for, nothing is standing out. I recently upgr
  10. Is that for the subdomain issue? I keep getting a 502 Bad Gateway error - none of my other subdomains are having an issue. Although I did have to change port 8118 to 8119 (which I may have done incorrectly) since 8118 is being used by deluge. I have both deluge and qbittorrent because the deluge version isn't whitelisted by a private tracker I use. When I search "iptable" in supervisord.log I see many instances of this: With the only differences between them being the timestamps and the "4" and "8" on lines 4 & 5.
  11. I just added this docker today and was able to get it up and running. Was on the WebUI (via 192.168.1.69:8080) without issue, but wasn't able to connect, and still can't, from my subdomain (qbittorrent.WEBSITE.com). In my troubleshooting I went into the QBitTorrent Options -> WebUI and turned on the WebUI and set the IP address and port to match my Unraid QBitTorrent docker. After this I immediately lost connection to the WebUI and have not been able to get it back. I imagine setting the WebUI in the QBitTorrent options to match the Docker caused a conflict, but now I'm not sure how to
  12. Hey guys, so I recently started using a wireless USB drive to store dashcam/security cam footage from my Tesla following this guide: https://www.reddit.com/r/teslamotors/comments/au0f3h/accessing_tesla_dashcam_and_sentry_mode_video/ I set the USB drive to a static IP address through my router (192.168.1.159) and was able to connect to the drive and map it as a network drive through windows explorer: \\192.168.1.159\files\TeslaCam So now the part where I'm stuck is trying to backup/sync this folder with a folder on the Unraid server. The options I've considered are: - Setu