Everything posted by aptalca
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
You shouldn't need to force a renewal. Auto renewals are attempted daily. Check the log/letsencrypt folder to see what's going on
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Start here:
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Map a new folder in the container settings, say /mnt/user/www on the unraid side and /www on the container side. Then in your nginx site config, set the root directive to /www
-
[Support] Linuxserver.io - OpenVPN AS
I have 2 openvpn servers set up on mine. One on the router (pfsense), which is my main connection, and another on unraid as a docker container, which is my backup. I also have chrome remote desktop enabled on a windows vm on unraid as a backup to the backup
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
For the logrotate, you can map it as a path so container side it will be /etc/logrotate.d/fail2ban and host side would be wherever your custom file is at on your unraid. For the actions and filters, just put your new configs into the respective folders under /config as they are already made available for user customization. I used recidive in the past where regular bans were short lived (5mins) but if an ip got banned 3 times in a 10 hr period, they would be banned for a whole week. Never did anything longer than that.
-
[Support] Linuxserver.io - OpenVPN AS
I personally think it's a bad idea to expose the openvpn-as gui. If someone brute forces it, they can create their own vpn user and get on to your lan
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Why are you trying to modify the logrotate config file?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Also, forward the port 443 and then go to https://www.yourcustomsubdomain.duckdns.org and if you see the placeholder page, letsencrypt is working fine. Then you can set up nextcloud reverse proxy
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Sounds like somebody didn't read the readme. Read the readme under the folder /config/nginx/proxy-confs and it will tell you how to enable the preset proxy confs (hint: you just rename the file) Each proxy conf also tells you what you need to change (if any) in the external app.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
No naxsi package module in alpine 3.8 repo
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I believe you can just enable in the ssl.conf
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Not sure about security but the main benefit of ldap is you can have different authentication levels for users and groups easily
-
[Support] Linuxserver.io - Ombi
?? The main advantage of bridge is to be able to map whatever port you want. Bridge vs br0 vs host makes no difference for outside access
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Remove that bit from nginx.conf, open the default site config and you'll see the message about https redirect at the top
-
[Support] Linuxserver.io - Ombi
Why don't you put all of them on bridge instead?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Sounds like you just had to retrace your steps to identify the issue. Glad it works now
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
This isn't the thread for the video guide so you'll have to provide more info on what exactly you did
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
You can use dnschecker.org to see propagation
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Are you using the preset proxy confs?
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Set an A record for cdkauffmann.com and set it to your IP address
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
On the surface it looks about right. Actually you had to repeat the ssl info because it is in a different server block.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Glad to hear it worked
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Go to WordPress admin, settings, general and you'll see two fields for wp address and site address. My guess is they are set up with www
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
That seems totally stock. I'm assuming your wordpress is being served in the www folder. You must have a redirect in wordpress. Did you set the website url as www.domain.com in wordpress settings? There could also be browser cache when 301 redirects are involved. Try a new browser or incognito
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
It's called default It's under /config/nginx/site-confs