NeoMatrixJR

Don't worry then. found an alternative

My apologies if I missed this or the answer should be obvious, but is there any way to put my VPN clients on the same subnet as the rest of my LAN pc's or assign IPs from my router's DHCP? I have applications that look for 2 machines to be on the same LAN (or as some state...on the same WiFi <facepalm>) and they won't work over VPN in my current configuration. Also, should I want to expand beyond 2 clients...is there a different...non-AS docker I should be using?

any way to specify if you want canary build? I ran an update on mine to canary, then it downloaded the latest docker image and now I can't get into the web interface...it says "the database has version 5 but the largest supported version is 4"

Any chance you've had time to take a look at this? Not a big deal right now...just remembered this is on my "to fix" list.... Thanks!

Got it sorted...kind of. Transmission VPN docker was eating all traffic forwarded from my router to my server....not sure how to fix yet except turn off that docker...which hasn't been used in a while...so that's fine for now.

Running your Transmission VPN docker...whenever it's up and running it seems somehow it's eating traffic directed at other dockers. Running nginx on container 80, host 8081, and traffic forwarded from 80 --> 8081 on my router...no traffic ever reaches my nginx docker while transmission is up. Oddly, it's only external traffic. Traffic from within my network directed at 8081 gets to the appropriate docker fine.

Docker Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "EMAIL"="<redacted>" -e "URL"="<redacted>.us" -e "SUBDOMAINS"="www,<sd1>,<sd2>" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "VALIDATION"="http" -e "DNSPLUGIN"="" -e "HTTPVAL"="true" -e "PUID"="99" -e "PGID"="100" -p 8080:80/tcp -p 4343:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt Forwarding Container log: [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... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=redacted.dns SUBDOMAINS=www,<sd1>,<sd2> EXTRA_DOMAINS= ONLY_SUBDOMAINS=false DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=<redacted> STAGING= Backwards compatibility check. . . No compatibility action needed 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d www.redacted.dns -d <sd1>.redacted.dns -d <sd2>.redacted.dns E-mail address entered: <redacted> http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for <sd2>.redacted.dns http-01 challenge for <sd1>.redacted.dns http-01 challenge for redacted.dns http-01 challenge for www.redacted.dns Waiting for verification... Cleaning up challenges Failed authorization procedure. www.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.redacted.dns/.well-known/acme-challenge/edxukoZRwU7EPlVpHFg142PTBBrqyU2G94dp_KmApA0: Timeout, redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://redacted.dns/.well-known/acme-challenge/hMixnVqD8nuDQ8WFP4rYw2NL-lWDNx-gqifbSt0Yy8Y: Timeout, <sd1>.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://<sd1>.redacted.dns/.well-known/acme-challenge/gjtxzSA3iVJOr5-uEKmtJaFH_1F-u9aG1g_03Km8fYI: Timeout, <sd2>.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://<sd2>.redacted.dns/.well-known/acme-challenge/IzNN34bA1ALo-7NdbqWlN63vQNvvo4PP-pvea9FCpKE: Timeout IMPORTANT NOTES: - The following errors were reported by the server: Domain: www.redacted.dns Type: connection Detail: Fetching http://www.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: redacted.dns Type: connection Detail: Fetching http://redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: <sd1>.redacted.dns Type: connection Detail: Fetching http://<sd1>.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: <sd2>.redacted.dns Type: connection Detail: Fetching http://<sd2>.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA 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. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

have LE docker on unRAID 6.4. Was working previously...checked it yesterday and no joy. Attempts to http validate my domain/subdomains fails. Can't connect via HTTP. Firewall/ports/etc. set up ok (was working previously). I docker exec'd in to bash and I can't see that nginx is even running or listening on any ports. Did a config backup, full remove/remove image/wipe config and re-install...still no joy. HELP!