[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

I ended up setting up Cloudflare and got it working that way.

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

4 minutes ago, bdillahu said:

 

I think I had the same problem... I had a variable in "show more settings" called HTTPVAL: - it was set to True as I had had to do that sometime in the past I believe. I changed it to "false" and started getting some stuff working.

 

Haven't finished testing, but wanted to pass it on.

No HTTPVAL in my command.  Here it is.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='letsencrypt' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e 'EMAIL'='XXXXXXXX' -e 'URL'='duckdns.org' -e 'SUBDOMAINS'='XXXXXXX,' -e 'ONLY_SUBDOMAINS'='true' -e 'DHLEVEL'='2048' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'PUID'='99' -e 'PGID'='100' -p '81:80/tcp' -p '444:443/tcp' -v '/mnt/cache/appdata/letsencrypt/':'/config':'rw' 'linuxserver/letsencrypt'

d3a3282f734239ff8f7722288607e7cb56b6cd74a45022ed17f02f97b32a8b77

The command finished successfully!

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

1 hour ago, aptalca said:

 

Try changing the config folder location to /mnt/cache or /mnt/disk (longshot) 

Tried that. Still no luck.  

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

3 hours ago, aptalca said:

 

Are you sure there isn't something else running on port 81 on unraid?

 

According to your log, letsencrypt servers cannot reach your container when they try to connect to your domain on port 80, which could be that your dns is not set up correctly, or duckdns is forwarding to the wrong ip, or your router is not forwarding to the correct lan ip or port, or your container is not listening on the right port. 

 

You can temporarily put up a regular nginx container (while letsencrypt container is down) with the same ports and try to connect to it through your domain on port 80 and see if you get the default placeholder page

I put up a regular nginx container with the same ports, and I was able to connect to it fine.  Removed the nginx container and recreated the LE container, and still had the same error, so i think my forwarding is fine.  

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

@d2dyno  I tired forwarding my domain name to my duckdns and then removed subdomains, but it still isnt working.

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

I am having issues with my install.  It was working a few months ago, but then it was turned off for awhile and I upgraded the OS twice and updated the Docker.  It was no longer working,  Everything seems to be set up correctly, and I never changed any of the settings.  I tried recreating the docker and removing the appdata folder.