-
Unable to connect to GUI for longer than 2 minutes
Thanks for the nudge here; I have this set up as a static address but somehow one of my APs was given that address via DHCP
-
Unable to connect to GUI for longer than 2 minutes
I just looked at my switch data, and it looks like for some reason it's reporting that both eth0 and IPMI are running off of the same switch port. Not sure if that's just poor reporting from Ubiquiti (Edgeswitch24 Lite), or if something changed somehow on my motherboard. It's a X11SSM-F with eth0, eth1, and IPIMI all cabled to the switch. Losing GUI access is from multiple computers on my network. I just tried using my attached keyboard/monitor and so far there doesn't appear to be a problem
-
jamesp469 started following [Support] Linuxserver.io - Mylar , Unable to connect to GUI for longer than 2 minutes , UNRAID Losing Connection and 1 other
-
Unable to connect to GUI for longer than 2 minutes
Hello, after a recent power outage, my server has been experiencing issues. The logs show a graceful shutdown was completed, however after rebooting I lose GUI access after 1-2 minutes. Access will re-enable periodically, however there are extremely long periods where I am unable to access. This is also impacting all docker access, specifically noticed when using SABnzbd and Plex. I was running 6.11 previously, then downgraded back to 6.9 just in case that was a factor. If someone could take a look at my diagnostics and see what I'm missing here I would appreciate it. unraid-diagnostics-20240206-1451.zip
-
UNRAID Losing Connection
I'm having the same issue, running 6.11.5; GUI access disappears after a few minutes, comes back shortly after. Plex stops playback after 5 minutes, etc. Only change to my network was a safe shutoff (from UPS power) during a long term power outage.
-
Multiple issues - unable to write to cache, /var/log full
Thanks, I thought I cleared out a decent chunk of space (~100GB) but maybe I'm wrong there. For the high metadata, could that be from Plex?
-
Multiple issues - unable to write to cache, /var/log full
Hello, hope someone is able to help me figure this one out. I've been having the /var/log full error for a bit of time now; rebooting always kicks the can down the road for a month or two. But now that error is being coupled with some other ones, and I'm not sure where to start looking. Attached is my diagnostics, thanks in advance. unraid-diagnostics-20220302-0840.zip
-
[Support] Djoss - Nginx Proxy Manager
You need to change "-----BEGIN PRIVATE KEY-----" to "-----BEGIN RSA PRIVATE KEY-----" in your key crt file to get this to work. No idea when the requirement changed, but this fixed the issue for me last night.
-
[Support] Linuxserver.io - Mylar
Anyone else having this issue?
-
[Support] binhex - rTorrentVPN
I'm having an issue with RSS feeds over VPN. The provider I am pulling the RSS feeds from requires that the same IP address used to set up the feed is the same IP address used to load the feed/download from. I am running this container on my server, and set everything up using my desktop using the VPN feed. The issue I am running into is that, when my desktop is not on VPN and I attempt to reload the feed through the container's GUI (container is on correct VPN IP), I get errors that the IP does not match the VPN ID. I've ran multiple checks with checkmyip.torrentprivacy.com, and the container's external IP is still showing as the correct VPN ID. However, if I log into my VPN service on the desktop and try to reload the feed, it works perfectly. This is only an issue with RSS; when I download torrents off the VPN-connected desktop, disconnect from VPN, and load them to the rTorrent container, they download as expected. I will leave the feed alone for a few weeks to see if it is able to automatically pull from the provider, but am a bit befuddled as to why this isn't working as (I) expected.
-
jamesp469 started following Docker tab hangs in 6.8
-
Docker tab hangs in 6.8
After upgrading to 6.8, my docker tab hangs with no resolution. Actual docker URLs are still accessible; diagnostics attached. I'm also seeing the following error in the log: Dec 11 09:09:09 unRAID nginx: 2019/12/11 09:09:09 [error] 7631#7631: *21 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.190, server: , request: "GET /plugins/dynamix.docker.manager/include/DockerContainers.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "MYADDRESS.unraid.net", referrer: "https://MYADDRESS.unraid.net/Docker" Also, all of my plugins are showing as status "unknown" and seem to hang, with the following error: Dec 11 09:16:03 unRAID root: Fix Common Problems: Error: Unable to communicate with GitHub.com Thanks! unraid-diagnostics-20191211-0917.zip
-
Unraid OS version 6.8 available
I'm seeing this issue as well, plus all of my installed plugins are listed as status "unknown". Diagnostics attached, thanks! unraid-diagnostics-20191211-0917.zip
-
[Support] Linuxserver.io - Mylar
I'm running into issues where Mylar regularly disables my search providers. After digging into the logs, it looks like it occurs after daily API limits are hit (WARNING DAILY API limit reached. Disabling provider usage until 12:01am) however the provider usage is not automatically re-enabled. I have always had to manually enable the provider. Is this something I should go to the Mylar team on, or something that can be managed at the docker level (force re-enabling search providers)
-
jamesp469 started following Data recovery services on a parity drive?
-
[Support] Linuxserver.io - Mylar
I'm having issues with my main indexer regularly being disabled in this container. It doesn't disable for a short time period, it disables the indexer permanently until i manually enable it. Anyone else having this issue? 2019-02-28 02:00:15WARNINGUnavailable indexer detected. Disabling for a short duration and will try again. 2019-02-28 02:00:15WARNINGUnable to retrieve search results from dognzb [Status Code returned: 503] 2019-02-27 19:22:19WARNING[ERROR] string index out of range 2019-02-27 18:08:40WARNING[ERROR] string index out of range 2019-02-27 17:37:07WARNING[ERROR] string index out of range 2019-02-27 17:37:07WARNING[ERROR] string index out of range 2019-02-27 17:31:52WARNING[ERROR] string index out of range 2019-02-27 17:16:38WARNING[ERROR] string index out of range 2019-02-27 07:09:26ERRORCould not locate exceptions.csv file. Make sure it is in datadir: /config/mylar
-
[Support] Linuxserver.io - Radarr
Thank you! Changing /mnt/user/appdata/radarr/ to /mnt/cache/appdata/radarr/ has appeared to solve the issue. Edit - I did not delete/remove any data
-
[Support] Linuxserver.io - Radarr
Just the config path, which is "/mnt/user/appdata/radarr"
jamesp469
Members
-
Joined
-
Last visited