truetype

Dope..... Thanks, tried with 442 and now running at least!

I see the last update made it though for most of us... I've read about the last 5 pages and I seem to be the first with this issue "port already in use". I get "Execution Error" which means I cannot even start the docker. I've updated to unraid 6.4.0, does it have something to do with it? See below in box and/or screenshot. I've tried to change the 443 port to like 445 but same error then... Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "EMAIL"="*****@******.***" -e "URL"="********" -e "SUBDOMAINS"="www,*******," -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -e "HTTPVAL"="true" -p 81:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt 078c988ab78bd5a856f7a2781cadaaca44e54611c5f91b03c896236175364696 /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (8c666828f2c390c48772f4d9a78444293262b1bd6cf74c3aaf9edc400a71f669): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use. The command failed.

How's it going with this? I'd be needing that too... +1

I just pressed update and it fixed itself

Let's see, let's see It's below the Advanced Settings, sorry didn't open that up. But I mapped it to my cache drive "/mnt/user/appdata/plex". A problem I've noticed now is all the settings I had from PhAzE's plugins... Which media that is watched or not, all my friends who's watching will have to start over too :3

Lol, I just choose it as Host and added the paths I believe ;o Here's a screenshot of the settings, Plex is running now anyway. https://gyazo.com/f3a0d5f273ba0a914005ef95239a8916

Great, that makes perfect sense, that's how I had it setup with PhAzE's Plex Plugin. Now I have installed it, though it says "Not Available" under the version column in the Docker Tab in unraid. Isn't that strange?

Alright, but I am going to follow jonp's guide to transcode to RAM I have about 20 dockers and this is actually the first time I believe that I have to create mappings when installing a docker.

I think it's kinda hard to understand how I should apply it to the template? So if I understood it correctly, while I read under the Parameters, and I need to do the following: Run the container in Host mode. Add as many paths as I need to my media (they call it "data" under the parameters, but I guess it doesn't matte what ever I call it) Movies, TVs etc. Add path to /transcode that's about it?

Alright, thx! By the way, should it be run in host or bridge? Does it matter really?

Seems not to be as easy as 1, 2, 3 tho. The template says I should point /media to my media folder, but there's no where in the template to type in the media. Do I have to create the variable myself? The Plex's Official docker seems to have a perfect template. What you think? @Squid Maybe I can just use Plex's Official Docker's template with LSIO's container instead ;O

Ooh, great with autoupdate. I'll go with LSIO's then I guess the installation is simple as 1, 2, 3 by just reading in the template going to install it now

I'd like to try Kodi aswell, but as I've understood it there's no transcoding in Kodi yet. I mean, Plex is still the better of the two? Yes that's right, same with the LSIO team, they are quick and very kind around here. Like Squid Hey Squid! Yeah, I've seen that the LSIO's is more popular. Not by much though. But as wgstarks says above the Plex's Official release came a little late, and that would be a plausible reason. But I'm wondering because I'm here now, migrating from PhAzE's Plex Plugin and therefore I wonder if it's going to be the same thing with LSIO's Plex Docker since there is a Official one now, and most likely that will be more and more popular making LSIO's Plex Docker slowly fading away. I don't know

Yeah you're right, there's also one from Limetech's repository. Though now I brought up the 2 most popular ones. Do you use the binhex one? I agree with both of you, LSIO's dockers and team are really awesome, that's exactly my experience too. Though it might be no point to use another one now when Plex themselves have an official docker, I'm wondering. But I guess I'll stick with LSIO once again, they never brought me down before and it seems they are more focused on unraid too. *EDIT* I found this: https://forums.plex.tv/discussion/250871/i-was-already-using-the-linuxserver-io-docker-before-do-i-need-to-switch And I've decided to go with Plex's offical docker.

Hey folks! I have been using PhAzE's Plex plugin for a long time and now I've decided to go over to docker instead since PhAzE is slowly turning away from the plugin support anyhow. So which one do you think I should use? LSIO's docker or Plex's Official one? ~TrueType

Solved it! For future reference it might help some lost souls: Ok, so I decided to go on my own and I realized if I used Filezilla on my PC I could see all the files. I plugged in my new USB device and formatted it to Fat32 named UNRAID. Stopped the array and connected to my server via Filezilla and started copying everything from /boot to the new USB except the "System Volume Information" folder since I assumed this is containing all the GUID files or something. I made it bootable by using the make bootable .bat in admininstation mode. Plugged the USB into my server, booted up and continued following the guide. All working fine, just a noticeable bit slower to reach the webgui now as it seems... ~TrueType

Hey, I've just bought a new USB memory, more precisely a Sandisk Cruzer Fit from the recommendations list of recommended USB. Now following the procedure HERE. This is the first time I am replacing my original key. Step 2: restore a complete backup of previous flash drive to new device. Which is the best way to do this? I suppose plugging in the original USB with my new USB into my PC and copy/paste isn't the best way? Is it best to just plugin the new USB-drive into my unraid-server while running and SSH into the server and just use the cp command to copy the /boot folder into the new flash drive? Thanks in advance! ~TrueType

If anyone else out there sees this. CHBMB and I tried alot of different approaches and finally solved it by reinstalling it completely.

Nope, no Cloudflare, just straight to the domain.

Please look at the screenshot I took before.

Ok, but that's really strange because my other subdomains are configured all the same with A-records at my domain provider, and it gave no errors when I did it for the first time yesterday. You think I should just delete the A-records and readd them again and see if that solves it?

I am sorry, here comes the log for docker. Notice that every subdomain worked before, until I added home.domain.com. ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.domain.com -d nextcloud.domain.com -d couchpotato.domain.com -d sickbeard.domain.com -d muxi.domain.com -d guacamole.domain.com -d sabnzbd.domain.com -d plexpy.domain.com -d home.domain.com Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created Saving debug log to /var/log/letsencrypt/letsencrypt.log An unexpected error occurred: The request message was malformed :: Certificate already revoked Please see the logfiles in /var/log/letsencrypt for more details. Generating new certificate WARNING: The standalone specific supported challenges flag is deprecated. Please use the --preferred-challenges flag instead. Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for domain.com tls-sni-01 challenge for www.domain.com tls-sni-01 challenge for nextcloud.domain.com tls-sni-01 challenge for couchpotato.domain.com tls-sni-01 challenge for sickbeard.domain.com tls-sni-01 challenge for muxi.domain.com tls-sni-01 challenge for guacamole.domain.com tls-sni-01 challenge for sabnzbd.domain.com tls-sni-01 challenge for plexpy.domain.com tls-sni-01 challenge for home.domain.com Waiting for verification... Cleaning up challenges Failed authorization procedure. guacamole.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to XX.XXX.XXX.XXX:443 for tls-sni-01 challenge IMPORTANT NOTES: - The following errors were reported by the server: Domain: guacamole.domain.com Type: connection Detail: Failed to connect to XX.XXX.XXX.XXX:443 for tls-sni-01 challenge To fix these errors, please make sure that your domain name was entered correctly and the DNS A record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. /var/run/s6/etc/cont-init.d/50-config: line 108: 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. And after this I try to go back to the template and delete "home" in order to get back to as it were. But then the log looks like this. ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.domain.com -d nextcloud.domain.com -d couchpotato.domain.com -d sickbeard.domain.com -d muxi.domain.com -d guacamole.domain.com -d sabnzbd.domain.com -d plexpy.domain.com Generating new certificate WARNING: The standalone specific supported challenges flag is deprecated. Please use the --preferred-challenges flag instead. Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for domain.com tls-sni-01 challenge for www.domain.com tls-sni-01 challenge for nextcloud.domain.com tls-sni-01 challenge for couchpotato.domain.com tls-sni-01 challenge for sickbeard.domain.com tls-sni-01 challenge for muxi.domain.com tls-sni-01 challenge for guacamole.domain.com tls-sni-01 challenge for sabnzbd.domain.com tls-sni-01 challenge for plexpy.domain.com Waiting for verification... Cleaning up challenges Failed authorization procedure. plexpy.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to XX.XXX.XXX.XXX:443 for tls-sni-01 challenge IMPORTANT NOTES: - The following errors were reported by the server: Domain: plexpy.domain.com Type: connection Detail: Failed to connect to XX.XXX.XXX.XXX:443 for tls-sni-01 challenge To fix these errors, please make sure that your domain name was entered correctly and the DNS A record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. /var/run/s6/etc/cont-init.d/50-config: line 108: 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. In order to get it working as it was before, I have to delete the letsencrypt folder in Appdata and replace it with my backup which I luckily did right before I tried to add home in the template.

I tried that but got a lot of errors in the log and the docker shutdown itself.

I have a complete working setup today with my domain.com, and I got nextcloud.domain.com. How do I add another subdomain? Like foobar.domain.com? Can I do this with a certbot command? ~TrueType

Please help, I am currently locked out from Muximux. I enter the settings in Muximux and enabled auth but I did not change any of the standard username or passoword and when I accidently reloaded the page I came to Muximux login and I am now prompt to enter a username and password. Anyone know the standard username / password? Or can check in the settings what's the standard? I've tried so many combinations including "admin" as username and "Muximux" as password. *EDIT* I solved it by changing in the settings.ini.php file at the authentication line to false.