aptalca

Unfortunately the Joe L script no longer works. Various errors including lacking strings support and others

What about stress testing a new disk? I like to run it through three rounds of preclear to rule out manufacturer defects. Is it possible through the unraid gui without the plugin or Joe L's script?

Full log?

Ah, I see. Well then even if it's a networking issue or something else, plex server log should tell what's wrong

This container does not recognize "tls-sni" = "true", so something else you did must have fixed it.

The second screenshot looks like your router is forwarding port 80 to port 80 on unraid for tcp, and port 81 to 81 on unraid for udp. What you need is to forward port 80 to port 81 for tcp. Right now, letsencrypt servers are connecting to your unraid web gui

If it's repeating "Starting Plex Media Server." that means plex is crashing and is restarted by the container. Check the plex server logs in your config folder. Likely a corrupt database.

You might want to read the info more closely. VALIDATION=true is not a valid option. You need "http", "dns" or "tls-sni" (tls-sni currently disabled by letsencrypt for most users)

I did get your message but your issue is not the ports. Your container is somehow set to use tls validation and that's why you are getting the error. Either your image is old (from before we implemented the HTTPVAL variable) or your settings are incorrect. Is there perhaps a space after the true in that variable? Can you post your docker run command that is shown after you save the settings and a new container is created?

Unraid gui uses port 80. Change your http port in the container to something else like port 81 and on your router forward port 80 to 81 on unraid EDIT: Oops didn't realize the container has its own ip The issue suggests that the validation server is connecting to a different webserver. Check your ip setting and make sure there isn't another machine on that ip you set for the container EDIT2: I also realized that you are trying to validate "duckdns.org". You need to read the info carefully (unless you are the owner of duckdns.org, which I doubt)

If you set HTTPVAL to true and you're still getting that error, it means you need to update the image, or there is another HTTPVAL directive in your docker run/create command that is not set to true

Set HTTPVAL to "true" not "True"

Nothing wrong with your cert. You have a duplicate site config. Move it elsewhere

Not sure, but probably. All official modules are included. Try it and see. If they are not in and we can add them, we will.

@CHBMB I know you have a supermicro board so I'll add my $0.02 I bought a fresco logic pci-e card because it was recommended by Oculus. However, it caused issues with my supermicro board (X9-srl-f). Basically, whenever I shut down the server, it would restart back up when this card was plugged in (only with linux, though). That caused issues during a power outage as you can imagine. I tried the same card on a different mobo, an asrock with intel pentium, same unraid os and it shuts down properly. YMMV I then bought this Rosewill (Renesas chipset) and it worked great: https://www.amazon.com/gp/product/B011LZY20G/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 I have a powered hub hooked up to it and passed through to a Win10 VM for gaming needs (mouse, keyboard, controller, usb headset, etc.) I can't remember for sure whether I tried to pass it through to OSX to be honest. I haven't touched OSX in a while.

Read the last few pages or the docker info

If you set HTTPVAL to true and you're still getting that "authenticator does not support. . ." error, you might need to update your image. Click on the check for updates in unraid gui and update the image

On android, connect to 10.1.2.40:9081 that is what you mapped on the host

Why don't you post the validation error referenced in the snippet you posted?

In the calibre gui, when you enabled the content server, did you set the port to 8081? It seems you set it to 9080. Inside the container, it has to run at port 8081. Then you map it to whatever port you like in the container settings. From the outside, you connect to that port that you set. It's all in the readme

You mapped 8081 to 9081, not 9080. Use that

Calibre server is accessible at your unraid ip and whatever port you mapped to 8081 in the container

Docker info contains a very simple permanent solution (unless your ISP blocks port 80, which you did not state whether it is the case or not)

Glad to hear it

Has nothing to do with the certbot version. Read the last few pages here, and the docker info