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

On 3/6/2018 at 5:13 PM, Nickglott said:

Hello all,

 

So I am in the process of securing my sevrer with SSL. Currently I have everything configured with letsencrypt and works. My only problem I seem to have is Emby. It works and it forwards http to https, the cert is good and everything works and loads but it is horribly slow. Not going through Nginx (straight ip+ssl port) it works just as expected except obviously an invalid cert from missing domain. So the problem has to lie within Nginx and/or the reverse proxy. Any help would be greatly appreciated and am wondering if anyone else has been having any issues like this.

 

 

Having the same issue myself. emby is running very slow. Unfortunately I don't have a solution yet.

[Call traces found on server]

I did assign IPs to some of my dockers after upgrading to 6.4 (I basically had to in order to get the SSL cert for the webui) That's interesting that it's causing these call traces to happen.

[Call traces found on server]

Fix common problems is reporting that call traces have been found. I looked at the syslog but I couldn't interpret what the call trace was. Any help is appreciated!

System:

Unraid 6.4

Xeon E3-1231v3

2x 8GB ECC DDR3

7x HGST 4TB HDDs

1x WD RED 8TB HDD

Samsung 250GB SSD (cache)

 

skynet-diagnostics-20180125-1146.zip

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

Count me among the dead. My ISP blocks port 80 so httpval doesn't seem to work. Not really sure what to do?

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

I upgraded to 6.4 and it screwed up my reverse proxy setup after adding the new cert to unraid itself. I saw earlier in this thread the suggestion to give the letsencrypt docker its own IP and to forward 443 to the new IP.

 

This fixed it not loading, but I still couldn't access some of my dockers (emby, ubooquity, etc) via my duckdns reverse proxy. I then found that giving each docker its own IP address and updating the "nginx\site-confs\default" file with the new addresses fixed the issue. Is this the "correct" way of doing things or is there a better way? 

[New Emby Docker]

edit: installed update. working great now. thanks!

 

 

Still getting this error with the latest version. Has the update not been pushed out yet?

 

[[DEPRECATED] Linuxserver.io - Rutorrent]

Is there a way to change the autowatch frequency? It seems to be random in how long it will take to grab a torrent from my watch folder. Sometimes it's a few minutes, and other times it's 10 minutes or more..

 

edit: answered my own question. first:

docker exec -i -t rutorrent bash

then 

vi /var/www/localhost/rutorrent/plugins/autotools/conf.php

Change $autowatch_interval = 300; to whatever you want. I changed mine to 30 seconds.

 

Type

:wq

 to save. 

 

This setting will survive a container restart, but it will revert back to 300 seconds anytime the container is updated or if you edit container settings so you'll need to do these steps again in those situations.

 

 

       

[Preclear plugin]

Anyone else getting

 

find: '/tmp/.preclear/' : No such file or directory

 

error after upgrading the plugin?

 

Also getting this error after upgrading plugin on 6.2rc3

 

I am getting this as well. I'm on 6.2rc4

[[Request/Done] Let's Encrypt Container]

No it's no solved , same issue for transmission.

 

 

Skickat från min iPhone med Tapatalk

 

Peter,

 

I added a trailing slash at the end of /rutorrent in the config and it seems to be working now. I tested from my phone  disconnected from the wifi and also from my computer connected to a vpn. Hope it fixes your issue as well.

 

location /rutorrent/ {

[[Request/Done] Let's Encrypt Container]

I have got reverse proxy to work, but rutorrent page looks strange? it' the same on other as well, but sabnzbd is OK.

 

my settings for rutorrent

 

 location /rutorrent {
                auth_basic "Restricted";
                auth_basic_user_file /config/nginx/.htpasswd;
                proxy_set_header Authorization "Basic zyz1230";
                rewrite ^/rutorrent(/.*)$ $1 break;
                include /config/nginx/proxy.conf;
                proxy_pass http://192.168.0.190:9080/;
                }

 

 

Did you ever solve this? I'm having the same issue.

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

Just updated to 6.2rc4. I was running 6.1.9. I previously had my docker.img and appdata on an SSD mounted with the unassigned devices plugin. The docker.img is not recognized now. I tried deleting it and recreating but it would not create a docker.img on the ssd. I put in the path to the ssd, click apply, and nothing happens.

 

I tried creating a docker.img on the cache drive and it was successful. I deleted that image and tried again on the ssd, but no luck. I'd rather use the SSD for dockers, otherwise the cache drive stays spun up all the time because of the dockers I use.

 

edit: I'm just going to use the SSD as a cache drive and add the former cache drive to the array.