-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aptalca
-
-
2 hours ago, izarkhin said:
Alright, apparently I need more help. Previous post still applies, but I now switched from aptalca's old container to the new one and I can't seem to get certificates issued. Here is what I see in the logs:
[cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.mydomain.mynetgear.com E-mail address entered: [email protected] Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for mydomain.mynetgear.com tls-sni-01 challenge for www.mydomain.mynetgear.com Waiting for verification... Cleaning up challenges IMPORTANT NOTES: Failed authorization procedure. www.mydomain.mynetgear.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for www.mydomain.mynetgear.com
here is the docker run command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="mydomain.mynetgear.com" -e "SUBDOMAINS"="www," -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -p 8083:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt
mydomain.mynetgear.com is a fake domain, but the real one exists and worked fine with the old container. router is configured with dyndns and can see it. port 443 is forwarded on the router. what could be the problem?!
I don't see anything wrong with the container settings. Likely a dns setting issue. Both containers use the same exact method to validate
-
3 hours ago, FreeMan said:
Default and specific shows configs attached.
URL: shows.bds.ddns.us
It started out being reachable but slow - I've been able to access via my phone & desktop machine at home via WiFi & wired networks. I've also been able to access via phone & work computer from off the home network. For the last couple of weeks, it's been totally unreachable - a timeout every time.
This is what I'm getting from my wired PC on the home network and on my phone via cell service (WiFi off).
If you go to http://192.168.1.5:4040 on lan, it connects fine?
Nothing jumps out at me in the site config. You should check the nginx logs in the config folder to see what's going on
-
On 10/9/2017 at 12:09 AM, FreeMan said:
I'm getting very slow response times from my LE/NGINX server. Slow to the point that it times out.
I have shows.mydomain.ddns.us pointed at my binhex-libresonic docker on port 4040. That times out before I ever get the NGNIX login. However, when I reopen port 4040 at the router and direct it to my server, I get near instant access to my music/video library on my phone with WiFi turned off (i.e., ensuring I'm accessing externally) or with the phone on WiFi. Therefore I believe that it's an issue with the LE/N container, not with my internet connection in general (though Comcrap has been less than reliable the last couple of weeks), my internal network, or the server itself.
I have it working (some installation issues were resolved around pages 30-32ish), and I've accessed it via my phone and my computer at work, however, it's always been sluggish.
I'm not sure what you might need for diagnosis, so I'm attaching Diagnostics, let me know what else might be needed for trouble shooting.
You can start by posting your site config. And then provide more concrete info such as what address you're trying to access, domain or ip. Also clarify whether it's timing out every time, which would mean no access as opposed to slow loading. Also try each case through lan and wan to make sure it's not a dns loopback issue.
There are too many possibilities and not enough info to diagnose.
-
1 hour ago, theboing said:
Is there any chance to get a second instance running?
Second instance of what?
-
33 minutes ago, Quiks said:
Hi again.
I found when transferring my config from my nginx vm to here that I was getting the following message
nginx: [emerg] socket() [::]:443 failed (97: Address family not supported by protocol)
Does this imply that ipv6 is not supported? or is there something I'm missing/need to change
Thanks in advance!
Unraid doesn't support ipv6
-
1
-
-
2 hours ago, Squid said:
Easier and less painful to simply create a VM specifically for this and use hardware passthrough on the video card.
I did do just that to test and got our plex container to do hw encode with nvidia
But plex doesn't support hw decode on nvidia just yet
-
1
-
-
20 hours ago, Quiks said:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 4096 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d subnet1 -d subnet2 -d subnet3 E-mail address entered: email Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Renewing an existing certificate Performing the following challenges: tls-sni-01 challenge for domain tls-sni-01 challenge for subnet1 tls-sni-01 challenge for subnet2 tls-sni-01 challenge for subnet3 Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/domain/fullchain.pem. Your cert will expire on 2018-01-03. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le /var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
edit: I think I found the issue. This might be a problem on certbot's end. (not sure? maybe you can confirm?)
I typed my domain with a leading capital in the container's settings.
The symlink is pointing to a folder where the first letter in my domain is capital.
The folder that exists has no capitals.
so, the folder created for the cert was created differently than the symlink's destination path.
/mnt/disk2/appdata/letsencrypt/etc/letsencrypt/keys/live/Domain.com/
vs
/mnt/disk2/appdata/letsencrypt/etc/letsencrypt/keys/live/domain.com/
I did a mv domain.com Domain.com and it now seems to be working.
I guess I should go into the container settings and change to lower case and let it re-run
Thanks for pointing me in the correct direction with the broken symlink.
Yup, my first guess would have been a weird character in the domain name, but yeah capital letters would do that. In linux, everything is case sensitive. In urls, I recommend keeping everything as lowercase
-
1
-
-
22 hours ago, Quiks said:
What you're seeing, /config/keys/letsencrypt is just a symlink. The folder it points to doesn't exist. Both of your screenshots are partial and I can't see the important info so can't help you with what's going on there
-
7 hours ago, thomast_88 said:
I'm still having issues. Copied a 11GB file from my primary array, to the cache array (raid 1), and server load went to 25'ish before it ended, making my dockers / VMS crash. @johnnie.black I saw your tests earlier, and noticed you are using raid 0. Have you had any issues with raid 1, or maybe have any idea why this is happening?
@aptalca did you get all the issues fixed - and are you running raid 0 or raid 1?
I switched to a single disk xfs. No more issues
-
1
-
-
1 hour ago, Quiks said:
Try changing the config location to a /mnt/cache or /mnt/disk
I suspect it might be a symlink related issue
-
2 hours ago, LSL1337 said:
so HW transcode is OK, but when the encoder runs out of 'bandwith', everything goes to shit?
only solution is brute force (with more bitrate?), but for remote media streaming it's not viable, cos the only reason for the transcode, is to save bandwith.
I can't believe how people find this usable...
the picture above is not even the worst I've seen in the past 5 minutes.
and when there is a scene change... No B-frames or anything?
whatever, I'm getting off topic
again, HUGE tanks for the linux help!
What are you encoding from and to?
I just tested a stream and it looked pretty good. Guardians of the galaxy 2 10+mbps 1080p hw transcoded to 4mbps 720p on a G4600 (hd630) kaby lake.
I noticed that sometimes when I first start a stream, it looks like a 240p YouTube stream for about 30-60 sec and then it magically fixes itself.
-
On 10/2/2017 at 10:42 AM, jrdnlc said:
Just found this error in my docker log. Latest docker update I believe triggered it
wget: error getting response: Address family not supported by protocol run-parts: /etc/periodic/monthly/geoip: exit status 1 error: stat of /config/log/fail2ban/fail2ban.log failed: Permission denied error: stat of /config/log/letsencrypt/letsencrypt.log failed: Permission denied error: stat of /config/log/nginx/access.log failed: Permission denied error: stat of /config/log/nginx/error.log failed: Permission denied error: stat of /config/log/php/error.log failed: Permission denied
Figured out the logrotate issue. It is a remnant from a permission issue from a very long time ago. I guess you have had that container for a long time. The problem is, the "log" folder and the folders underneath that are missing the "x" permission. You can either give them the execute permission or simply delete the log folder, restart the container and it will create new folders with the correct permissions.
-
5 hours ago, jrdnlc said:
Just found this error in my docker log. Latest docker update I believe triggered it
wget: error getting response: Address family not supported by protocol run-parts: /etc/periodic/monthly/geoip: exit status 1 error: stat of /config/log/fail2ban/fail2ban.log failed: Permission denied error: stat of /config/log/letsencrypt/letsencrypt.log failed: Permission denied error: stat of /config/log/nginx/access.log failed: Permission denied error: stat of /config/log/nginx/error.log failed: Permission denied error: stat of /config/log/php/error.log failed: Permission denied
Wget issue is an alpine issue. I'm considering reporting it.
It seems logrotate is also having issues. Not a clue why
-
-
2 hours ago, WexfordStyle said:
So I have this docker set up.
I used this spaceinvdaerone guide initially: https://www.youtube.com/watch?v=I58LTMKyeYw
and then reinstalled the docker taking into account updated information from the forum and the github page: https://github.com/linuxserver/docker-plex
That said, I have everything setup and it appears to work properly and connect. The remote computer registers my unraid system external ip address when I check. However, when I try to access the unraid WebUI or any local network services they do not work.... Is there something I am missing?
Any help is greatly appreciated.
Check out the vpn settings / routing and make sure you give access to the local network
-
2 hours ago, LSL1337 said:
Hi guys,
how can I add custom lines to the command line which starts the docker image?
I only used the gui, I'm not really an advanced linux user.
Is there a place on the GUI, where I can edit the 'raw' launcher code for the docker?
I'd like to add a new line for me to enable USB DVB-C Tuner. It should work with docker, right?
ps: what can the restart line do? Can it be set to restart this image periodically by itself?
Thanks!
As long as unraid recognizes your usb device and loads the drivers, you can pass the device into the container through the container settings gui (select device under "Add another path, port or variable")
-
I simply mounted the letsencrypt key folder in the emby container. No need to copy anything
-
7 hours ago, matthope said:
Hello everyone,
Recently, I have remarked a bunch of bot entries in my nginx access log file. Before that, fail2ban bot filter seemed to work fine. So I have looked in my fail2ban log file and it's full of error. It is the config by default, I've never modified it. I've tried to update fail2ban and ip6tables, but I cant find any package manager in the docker. I wonder if anyone know how to fix that. Here the error message:
2017-09-21 16:13:21,035 fail2ban.server [261]: INFO -------------------------------------------------- 2017-09-21 16:13:21,035 fail2ban.server [261]: INFO Starting Fail2ban v0.10.0a1 2017-09-21 16:13:21,035 fail2ban.server [261]: INFO Daemon started 2017-09-21 16:13:21,038 fail2ban.database [261]: INFO Connected to fail2ban persistent database '/config/fail2ban/fail2ban.sqlite3' 2017-09-21 16:13:21,039 fail2ban.jail [261]: INFO Creating new jail 'nginx-http-auth' 2017-09-21 16:13:21,040 fail2ban.jail [261]: INFO Jail 'nginx-http-auth' uses poller 2017-09-21 16:13:21,041 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,041 fail2ban.jail [261]: INFO Initiated 'polling' backend 2017-09-21 16:13:21,042 fail2ban.filter [261]: INFO Added logfile = /config/log/nginx/error.log (pos = 7134, hash = e98d121622aabfa4a1a34b1d636c2af5) 2017-09-21 16:13:21,043 fail2ban.filter [261]: INFO Set maxRetry = 5 2017-09-21 16:13:21,043 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,044 fail2ban.actions [261]: INFO Set banTime = 600 2017-09-21 16:13:21,044 fail2ban.filter [261]: INFO Set findtime = 600 2017-09-21 16:13:21,047 fail2ban.jail [261]: INFO Creating new jail 'nginx-botsearch' 2017-09-21 16:13:21,047 fail2ban.jail [261]: INFO Jail 'nginx-botsearch' uses poller 2017-09-21 16:13:21,047 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,048 fail2ban.jail [261]: INFO Initiated 'polling' backend 2017-09-21 16:13:21,049 fail2ban.filter [261]: INFO Added logfile = /config/log/nginx/access.log (pos = 480286, hash = 7cdbb6fa5cd3b6fb68a493f221b06792) 2017-09-21 16:13:21,049 fail2ban.filter [261]: INFO Set maxRetry = 2 2017-09-21 16:13:21,050 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,050 fail2ban.actions [261]: INFO Set banTime = 600 2017-09-21 16:13:21,050 fail2ban.filter [261]: INFO Set findtime = 600 2017-09-21 16:13:21,054 fail2ban.jail [261]: INFO Creating new jail 'nginx-badbots' 2017-09-21 16:13:21,054 fail2ban.jail [261]: INFO Jail 'nginx-badbots' uses poller 2017-09-21 16:13:21,054 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,054 fail2ban.jail [261]: INFO Initiated 'polling' backend 2017-09-21 16:13:21,055 fail2ban.filter [261]: INFO Added logfile = /config/log/nginx/access.log (pos = 480286, hash = 7cdbb6fa5cd3b6fb68a493f221b06792) 2017-09-21 16:13:21,056 fail2ban.filter [261]: INFO Set maxRetry = 2 2017-09-21 16:13:21,056 fail2ban.filter [261]: INFO Set jail log file encoding to UTF-8 2017-09-21 16:13:21,057 fail2ban.actions [261]: INFO Set banTime = 600 2017-09-21 16:13:21,057 fail2ban.filter [261]: INFO Set findtime = 600 2017-09-21 16:13:21,065 fail2ban.jail [261]: INFO Jail 'nginx-http-auth' started 2017-09-21 16:13:21,066 fail2ban.jail [261]: INFO Jail 'nginx-botsearch' started 2017-09-21 16:13:21,068 fail2ban.jail [261]: INFO Jail 'nginx-badbots' started 2017-09-21 16:13:21,113 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-http-auth ip6tables -w -A f2b-nginx-http-auth -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-http-auth -- stderr: 2017-09-21 16:13:21,113 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,113 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,113 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,114 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,114 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,114 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,114 fail2ban.utils [261]: ERROR -- stderr: 'Could not open socket to kernel: Address family not supported by protocol' 2017-09-21 16:13:21,114 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-http-auth ip6tables -w -A f2b-nginx-http-auth -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-http-auth -- returned 1 2017-09-21 16:13:21,114 fail2ban.actions [261]: ERROR Failed to start jail 'nginx-http-auth' action 'iptables-multiport': Error starting action Jail('nginx-http-auth')/iptables-multiport 2017-09-21 16:13:21,125 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-botsearch ip6tables -w -A f2b-nginx-botsearch -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-botsearch -- stderr: 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR -- stderr: 'Could not open socket to kernel: Address family not supported by protocol' 2017-09-21 16:13:21,126 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-botsearch ip6tables -w -A f2b-nginx-botsearch -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-botsearch -- returned 1 2017-09-21 16:13:21,126 fail2ban.actions [261]: ERROR Failed to start jail 'nginx-botsearch' action 'iptables-multiport': Error starting action Jail('nginx-botsearch')/iptables-multiport 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-badbots ip6tables -w -A f2b-nginx-badbots -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-badbots -- stderr: 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: "modprobe: can't change directory to '/lib/modules': No such file or directory" 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: "ip6tables v1.6.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)" 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: 'Perhaps ip6tables or your kernel needs to be upgraded.' 2017-09-21 16:13:21,138 fail2ban.utils [261]: ERROR -- stderr: 'Could not open socket to kernel: Address family not supported by protocol' 2017-09-21 16:13:21,139 fail2ban.utils [261]: ERROR ip6tables -w -N f2b-nginx-badbots ip6tables -w -A f2b-nginx-badbots -j RETURN ip6tables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-badbots -- returned 1 2017-09-21 16:13:21,139 fail2ban.actions [261]: ERROR Failed to start jail 'nginx-badbots' action 'iptables-multiport': Error starting action Jail('nginx-badbots')/iptables-multiport
EDIT: Those errors are present since 2017-07-25 at least (no more log after this date).
We have a PR waiting to be merged to fix that. Until then, see here:
-
1
-
-
10 minutes ago, Addy said:
I found this http://prntscr.com/gnozw0 in the plex settings, however the episode im testing with still wont play (I assume this is the same thing)
That seems like the plex transcoder is having issues with those files. You should ask on the plex forums. They'll probably ask for the logs and maybe a sample file.
-
5 hours ago, Addy said:
I wish!
It writes nothing to the log about the playback/error
Maybe because it never actually errors it just continually loads forever http://prntscr.com/gnd4lm
As I said, its a very select few episodes.. not a huge problem but I hope it doesn't get worse. I also tested the same episode on the android plex app and on my desktop
That's the docker log. The plex server log is in the config folder
-
1
-
-
You can check the plex server log
-
2 hours ago, isvein said:
localhost: another domain or subdomain?
As far as I can see, one letsencrypt docker can only be used for 1domain and its subdomains.Support for multiple domains was added in July
-
1
-
-
3 hours ago, localhost said:
Hi,
Been running letsencrypt for the last few days now, all working smoothly with the single domain I set it up on.
I would like to add another domain now but can't see how. Just from looking around all I can see in the files config wise is a file called 'donoteditthisfile.conf' otherwise all the files look default.
In this file there is a param 'ORIGEXTRA_DOMAINS=""' I'm wondering can it be as simple as adding it here?
I've found loads of tutorials for how to do this but they're all installs in a full operating system environment and the setup looks quite difference using the unraid docker.
Thanks
Dude, the file is literally named "donoteditthisfile.conf" so no, do not edit it, lol.
Check the docker hub or the github page for this image. It tells you how to add additional domains (hint: optional settings)
-
8 hours ago, Nomad007 said:
Hi guys struggling a little trying to get some basic services to run. I followed this guide
So far port 443 is open and I see the nginx web page but I cant get sonarr and/or radarr to work.
Typing https://DOMAIN.duckdns.org/sonarr and https://DOMAIN.duckdns.org/radarr show the same default nginx page.
URL base for sonarr is “/sonarr”
URL base for radarr is “/radarr”both services have been restarted.
Here is the cut down default file I currently am using. Which is based off the guide.
Im sure its something simple i am missing but i cant see it. any advice?
Clear your browser cache. The = in location blocks results in permanent redirects. Your browser may have cached that from before
[Support] Linuxserver.io - Plex Media Server
in Docker Containers
Posted
Read through the last couple of pages