BBriner

@sse450 I'm wondering if it was a problem with the ML150 G9 + unRAID compatibility or if you really had the bad luck of having two defective motherboards. The reason is that I got myself a ML150 G9 very cheap and after having read your posts I am afraid of trying unRAID on it.

That's the reason the workaround works. Unfortunately the LE Docker cannot generate a certificate with the "*". The LE Docker can only generate the certificate with the CN as "mydomain.com" or "hostname.mydomain.com" if setup as I mentioned.

I've managed to find a workaround. The workaround is to set the LE Docker variable "Only Subdomains:" to "True" and in the list of "Subdomain(s):" to make sure your unRAID server-name is the first one. With this workaround the generated LE Certificate will be issued to "server-name.domain.tld" and unRAID internal NGINX won't redirect to "https://domain.tld"

In fact it is exactly the opposite. It does not work because unRAID redirects to a wildcard domain without adding the server name.

Same here. Copying the LE docker cert "priv-fullchain-bundle.pem" to "/boot/config/ssl/certs/server-name_unraid_bundle.pem" works when typing https://server-name.domain.tld, however unRAID wrongly redirects the http://server-name.domain.tld to https://domain.tld. Did you automate the import from pfSense to unRAID? If so, would you mind sharing your script?

Thanks! Problem solved!

You uninstall the advanced buttons plugin. It's incompatible Thanks. Guess what? I can't remove Advanced Buttons too!

My system is not updating the User Scripts plugin. I also tried to remove it in order to install it again without any success. It comes back to the same status. The same was also happening with the CA Plugin but I managed to update it directly in the Apps tab. Can the User Scripts plugin be manually updated or removed via command line?

I started from scratch everything (Docker, Duplicati Jobs, Script) and now it is working fine. Probably something very silly was happening.

Container Path: /source Host Path: /mnt/ In the Container, run-script-before: /source/user/Documents/Scripts/SendMessage.sh "Duplicati Job Started" Script SendMessage.sh #/bin/bash curl -k -s \ -X POST \ https://api.telegram.org/botfoobarfoobar:FooBarFooBar/sendMessage \ -d text="$1" \ -d chat_id=12345678 \ exit 0

The path is accessible from outside and inside the container and I can run it without any problem from the shell inside the container. I also tried to copy the script to a path that is only accessible inside the container and the same error shows up.

Is someone using any of the script options (--run-script-before / --run-script-before-required / --run-script-after)? I am always getting an error: The script "/path/to/script/foobar.sh" returned with exit code 255. I've searched for error code 255 without much luck.