Everything posted by aptalca
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Check your site config. You probably have a redirect somewhere
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
What php.ini did you create? Only modify the php local and restart. You don't need anything else
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
?? You didn't mention you already made changes to enable reverse proxy. That requires a whole another set of troubleshooting methods. Https is not a valid option for validation. Check the docs
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
That was an annoying forced change by letsencrypt done to reduce their server load at peak times. I guess they forgot that many people have scripts that are not run by cron. We pushed an emergency update last night to remove cert renewal during container start
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Is wordpress set up in the letsencrypt container or are you reverse proxying? I have them set to 64MB the same way and it works
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
With letsencrypt, you're trying the https address, right? Log suggests nginx is started and there are no errors. What happens when you try to connect?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Make sure that your ip is set correctly on your dns provider and that there is a cname created and set up for the "server" subdomain. If all looks good, you can try stopping the letsencrypt container, create an nginx container with the same exact port mapping, and see if you can reach it through the domain and ports 80 and 443
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Post a log
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Do "docker ps" and post the line containing letsencrypt
-
[Support] Linuxserver.io - DuckDNS
Ipv6 is not supported in this image
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I think you mean proxy and not redirect (they have very different meanings for webservers) If you post your config we'll take a look
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Is the host ip/port in the proxy pass directive
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Use only lowercase in container names otherwise nginx can't resolve them
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
No alpine package for the module
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
It seems to be an apache module? So no plans
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
That's a dns hostname resolution thing. Not nginx's fault. Use all lowercase in container names or define a network alias for the container
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
First set it to the regular bridge and set up your port forwards if you like. Save and exit. Go into the container settings one more time, change it to proxynet, don't enter an ip and hit save. Unraid doesn't recognize your proxynet as a custom bridge network (assumes it is macvlan) so if you try to change port mappings after selecting proxynet, unraid won't do it properly.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Not sure how duo works but ldap auth is already included. For radius, there is no alpine package in the repo.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
No, you can reverse proxy anything through the ip address.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Sure, you just use the ip of the vm in the proxy_pass directive
-
[Support] Linuxserver.io - Ombi
Reverse proxy it and then use your domain name in that field
-
[Support] Linuxserver.io - DuckDNS
Glad to hear it works now
-
[Support] Linuxserver.io - DuckDNS
It sounds like your duckdns.conf is messed up somehow. It is only supposed to contain two lines, and two items each, separated by an equal sign, no spaces. Check to see if it's the correct format. You can also pm me the contents (I believe duckdns lets you recreate the token) Also, are there any special characters in your token other than hyphen?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
We don't support that
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Actually, it was something you did within the last 2-3 months. The update only caused a forced validation due to expiring certs, and that process failed. Check your port forwarding on your router