MrLinford

I use EMBY and will be looking to do the same thing

Thank you for sharing!! Apart from Plex pannel (as i don't use it) this will be used daily.

Holy Cow! I would love to see the full release when you can.

On to my next issue, challenges are failing for some reason today at 06:50:02[8/26/2022] [6:50:02 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation today at 06:50:02Failed to renew certificate npm-10 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-11 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-12 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-13 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-15 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-16 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-17 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-18 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-19 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-20 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-21 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-22 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-23 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-24 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-26 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-27 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-8 with error: Some challenges have failed. today at 06:50:02Failed to renew certificate npm-9 with error: Some challenges have failed. today at 06:50:02All renewals failed. The following certificates could not be renewed: today at 06:50:02 /etc/letsencrypt/live/npm-10/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-11/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-12/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-13/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-15/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-16/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-17/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-18/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-19/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-20/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-21/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-22/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-23/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-24/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-26/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-27/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-8/fullchain.pem (failure) today at 06:50:02 /etc/letsencrypt/live/npm-9/fullchain.pem (failure) today at 06:50:0218 renew failure(s), 0 parse failure(s) today at 06:50:02 today at 06:50:02 at ChildProcess.exithandler (node:child_process:399:12) today at 06:50:02 at ChildProcess.emit (node:events:526:28) today at 06:50:02 at maybeClose (node:internal/child_process:1092:16) today at 06:50:02 at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) Checking the letsencrypt.log

OK, fixed it following this post: https://community.letsencrypt.org/t/solved-another-instance-of-certbot-is-already-running/44690

Done that, even restarted the server.

I have just gone to create a new host and it failed. Here is the log: 2022-08-23 19:51:27,153:DEBUG:certbot._internal.main:certbot version: 1.27.0 2022-08-23 19:51:27,153:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/bin/certbot 2022-08-23 19:51:27,153:DEBUG:certbot._internal.main:Arguments: ['--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-40', '--agree-tos', '--authenticator', 'webroot', '--email', '<REMOVED>', '--preferred-challenges', 'dns,http', '--domains', 'eveinsight.brothercraig.ddns.me'] 2022-08-23 19:51:27,153:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot) 2022-08-23 19:51:27,165:DEBUG:certbot._internal.lock:A lock on /var/log/letsencrypt/.certbot.lock is held by another process. 2022-08-23 19:51:27,165:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 126, in _try_lock fcntl.lockf(fd, fcntl.LOCK_EX | fcntl.LOCK_NB) BlockingIOError: [Errno 11] Resource temporarily unavailable During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/certbot", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.9/site-packages/certbot/main.py", line 19, in main return internal_main.main(cli_args) File "/usr/lib/python3.9/site-packages/certbot/_internal/main.py", line 1728, in main log.post_arg_parse_setup(config) File "/usr/lib/python3.9/site-packages/certbot/_internal/log.py", line 107, in post_arg_parse_setup file_handler, file_path = setup_log_file_handler( File "/usr/lib/python3.9/site-packages/certbot/_internal/log.py", line 161, in setup_log_file_handler util.set_up_core_dir(config.logs_dir, 0o700, config.strict_permissions) File "/usr/lib/python3.9/site-packages/certbot/util.py", line 183, in set_up_core_dir lock_dir_until_exit(directory) File "/usr/lib/python3.9/site-packages/certbot/util.py", line 157, in lock_dir_until_exit _LOCKS[dir_path] = lock.lock_dir(dir_path) File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 259, in lock_dir return LockFile(os.path.join(dir_path, '.certbot.lock')) File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 45, in __init__ self.acquire() File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 60, in acquire self._lock_mechanism.acquire() File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 112, in acquire self._try_lock(fd) File "/usr/lib/python3.9/site-packages/certbot/_internal/lock.py", line 130, in _try_lock raise errors.LockError('Another instance of Certbot is already running.') certbot.errors.LockError: Another instance of Certbot is already running. 2022-08-23 19:51:27,165:ERROR:certbot._internal.log:Another instance of Certbot is already running. I also noticed, after check, in the docker logs the renewals are also failing.

Thank you so much. This is such a good QOL plugin:

I got this all setup now for my own home server, not a plex use but emby. Thank you for the work you have put in though to deliver this. Now to look at why the docker images aren't loading: Already fixed it. Noticed the BASE URL being https://192.168.1.7, this needs changing to the unRAID API address. Might be worth a mention in the guide

@ElectricBrainUK Any idea what could make the above happen?

I have done this but still get "Failed with status code: undefined" Also get the same error's with IP

+1 from me to.

@fmp4m thank you for sharing this will be useful.

Got mine all setup but not showing Proxy Hosts

Hello people. I'm trying to setup HTTPS connect to the container. I have add a second port mapping on the container settings: But the container shows its only listening on 8989