danimal86

First of all, sorry for placing this in the General Support area. I couldn't find a page for the Plex Inc Docker and my search for "Plex Remote Access" didn't come up with anything plex related. I had remote access working fine for years but all of a sudden i was noticing that my remote streams were limited to 2mbps and it looked like it was going through the Plex Relay and my server wasn't reachable remotely. I have upnp enabled in my asus router but it still doesn't seem to work. I tried setting up a port forwarding (external & internal ports set to 32400 and internal ip 192.168.1.99) and selected the Manually Specified Public Port in plex, but it still doesn't work. Anyone have any ideas? I haven't changed anything network related for years, so i dont think its a double NAT issue, but i dont completely understand it. Edit: i had a remote stream going and it was playing indirect The only think i have changed recently is installed jellyfin, so i deleted the docker and when i checked back on Remote Access in plex it was all green, but now its back to red. Edit2: This is bizarre. I have a vpn setup through built in wireguard. I have Sabnzbd setup to go through the vpn (i use ssl but cant be too safe) but plex is on Host mode. I went and dissabled the vpn on wireguard and BAM! All green and running a remote test it all working fine. How the hell did that affect my plex?

Thank you! Cant believe i didn't put 2 & 2 together with that setting. Seems like it could be helpful to have that more towards the top with the other settings. Thats really what i want to do, kinda fine tune the days to keep on cache so it keeps cache around 80% full, ( seems like i ingest 1tb/month, so that would leave some extra room in there) and it will keep drives from spinning up and have fast play times.

Could use some advice: I run two 2tb m.2's in raid0 for my cache. I would like to keep files on the cache drive for as long as possible before the mover takes over and puts them on the array. Seems to work fine, it will fill up to around 80ish % then all of a sudden, bam....moves everything to the array. This has been happening for a while, and its really hard to diagnose, because it take a bit of time to fill up the cache Here's my mover settings Here's my tuning settings: Is it something i have setup wrong? Ultimately i'd like to have it keep 60 days worth of media on the cache, then move it to the array. I'm a little confused on what to have "Only move at this threshold of used cache space" set to if i only want the 60 day old media kept

Got it figured out. Go into CA Backup Appdata v2.5 and uder the Backlup/Settings tab, go down to the bottom to Show Advanced Settings, and uncheck Firefox to stop when backing up appdata.

i tried using the stopwatch and it had reset itself, so it wasn't the appdata backup I'll give it a try again and see if it will not reset overnight. Edit: it reset overnight

Dang, i didn't even think about this. Yes i do, i remember running into a problem with Lucky Backups that it would disconnect when my appdata backups, nightly. I'll set it to Exclude the Firefox appdata folder during my daily backups. @Djoss I bet this is the problem. Going to try the stopwatch again.

I just checked on it, and the stopwatch had reset itself to the Stopwatch or Countdown homepage. So it seems like it is something with firefox resetting.

Thats a great idea! I've got it running now.

I didn't think about that. Any way to track that? I think for the most part i'll just have to set it up the day of....Not the biggest issue in the world. Thanks for your help

Sorry, i should have explained it a bit better. I have 2 computers: PC 1 is the Unraid Machine PC 2 is my Windows gaming/personal Machine I use PC2 to configure my unraid server (PC 1) and mess with plex/arr's via chrome browser. I open the Firefox docker (a chrome tab opens with firefox) and i have my airline (southwest) check in page as the homepage. I enter my information and a countdown clock starts. When i'm done using PC 2, i shut it down. PC 1 still stays running (it never shuts down). It looks like this before i shutdown PC 2: When i come back the next morning and fire up PC 2 and open chrome, all my unraid tabs (dashboard/plex/arrs/firefox) automatically open and on the firefox browser, the countown clock and the fields i entered are no longer there. It looks like this in the morning (the timer had not expired, it should still have countdown time remaining) My goal with using the docker was so that i could have the browser stay open forever and i could just load all my flight info into it and not worry about remembering to check in. I hope this explains it a bit better. Any ideas? Edit: I just noticed there was a docker container update...i just updated, i'll post if it fixed it.

So i setup firefox yesterday and shut down my gaming pc, woke up this morning and the browser had been reset back to the homepage. Does it have anything to do with a separate pc accessing it? I looked at the logs, and most of the way down, i can see a time stamp of 3am and then another stamp of 6:44 when i turned on my gaming pc and looked at the firefox browser: [xvnc ] Tue May 23 03:06:27 2023 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: created VNC server for screen 0 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'app'... [app ] Mozilla Firefox 109.0.1 [supervisor ] all services started. [xvnc ] Tue May 23 06:44:15 2023 [xvnc ] Connections: accepted: /tmp/vnc.sock [xvnc ] Tue May 23 06:44:16 2023 [xvnc ] SConnection: Client needs protocol version 3.8 [xvnc ] SConnection: Client requests security type None(1) [xvnc ] VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 [xvnc ] VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888 [xvnc ] ComparingUpdateTracker: 0 pixels in / 0 pixels out [xvnc ] ComparingUpdateTracker: (1:-nan ratio)

I'll check tomorrow (seems the issue happened overnight) and see if anything shows up. Right now, i dont see any errors in the logs: [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-openbox.sh: executing... [cont-init ] 10-openbox.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-check-snd.sh: executing... [cont-init ] 55-check-snd.sh: sound not supported: device /dev/snd not exposed to the container. [cont-init ] 55-check-snd.sh: terminated successfully. [cont-init ] 55-firefox.sh: executing... [cont-init ] 55-firefox.sh: terminated successfully. [cont-init ] 56-firefox-set-prefs-from-env.sh: executing... [cont-init ] 56-firefox-set-prefs-from-env.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated successfully. [cont-init ] 89-info.sh: executing... ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ │ │ │ Application: Firefox │ │ Application Version: 109.0.1-r0 │ │ Docker Image Version: 23.04.1 │ │ Docker Image Platform: linux/amd64 │ │ │ ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯ [cont-init ] 89-info.sh: terminated successfully. [cont-init ] all container initialization scripts executed. [init ] giving control to process supervisor. [supervisor ] loading services... [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'nginx'... [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'logmonitor'... [supervisor ] service 'logmonitor' is disabled. [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.13.1 - built Apr 16 2023 16:56:42 [xvnc ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12013000 [xvnc ] Mon May 22 03:06:16 2023 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: created VNC server for screen 0 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'app'... [app ] Mozilla Firefox 109.0.1 [supervisor ] all services started. [xvnc ] Mon May 22 06:40:21 2023 [xvnc ] Connections: accepted: /tmp/vnc.sock [xvnc ] Mon May 22 06:40:22 2023 [xvnc ] SConnection: Client needs protocol version 3.8 [xvnc ] SConnection: Client requests security type None(1) [xvnc ] VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 [xvnc ] VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888 [xvnc ] ComparingUpdateTracker: 0 pixels in / 0 pixels out [xvnc ] ComparingUpdateTracker: (1:-nan ratio)

Thats a good idea. I just looked at the logs in the "error" file i see: ATTENTION: default value of option mesa_glthread overridden by environment. And a bunch of these in the "output" : Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libEGL initialize failed (t=0.357819) |[1][GFX1-]: glxtest: GLX extension missing (t=0.357922) [GFX1-]: glxtest: GLX extension missing Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libEGL initialize failed (t=0.357819) |[1][GFX1-]: glxtest: GLX extension missing (t=0.357922) |[2][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=0.792826) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libEGL initialize failed (t=0.357631) [GFX1-]: glxtest: libEGL initialize failed Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libEGL initialize failed (t=0.357631) |[1][GFX1-]: glxtest: GLX extension missing (t=0.357853) [GFX1-]: glxtest: GLX extension missing Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libEGL initialize failed (t=0.357631) |[1][GFX1-]: glxtest: GLX extension missing (t=0.357853) |[2][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=0.786093) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=0.835898) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=0.790332) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D

I didn't change any settings within firefox, and from what i recall i didn't really change anything on the docker settings. The only thing i added was an extra parameter --restart=always as recommended by someone else, but i think that just starts the docker I did load the TamperMonkey extension within firefox. I setup a few firefox tabs and came back the next day or two later and just one tab was open and it was back at the homepage. I'll set it up again and see.

Its not closing or exiting itself, it just reverts back to its homepage.