Tuumke

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by Tuumke

  1. i have the same settings in web.conf =/
  2. @jonathanm root@NAS:/mnt/user/dockers/letsencrypt/nginx# cat proxy.conf ## Version 2018/05/31 - Changelog: https://github.com/linuxserver/docker-letsencrypt/commits/master/root/defaults/proxy.conf client_max_body_size 10m; client_body_buffer_size 128k; #Timeout if the real server is dead proxy_next_upstream error timeout invalid_header http_500 http_502 http_503; # Advanced Proxy Config send_timeout 5m; proxy_read_timeout 240; proxy_send_timeout 240; proxy_connect_timeout 240; # Basic Proxy Config proxy_set_header Host $host:$server_port; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Ssl on; proxy_redirect http:// $scheme://; proxy_http_version 1.1; proxy_set_header Connection ""; #proxy_cookie_path / "/; HTTPOnly; Secure"; # enable at your own risk, may break certain apps proxy_cache_bypass $cookie_session; proxy_no_cache $cookie_session; proxy_buffers 32 4k;
  3. Hi, Any posts on reverse proxying with nginx and blank screens? Kinda hard to read through 138 pages =/ Been searching google and tried different types of settings, all resulting in a blank page but working title bar.. location /deluge { proxy_set_header X-Deluge-Base "/deluge/"; include /config/nginx/proxy.conf; set $upstream_deluge 192.168.3.61; proxy_pass http://$upstream_deluge:8112/; It doenst matter if i use proxy_set_header and not set base in web.conf. If i set base in web.conf i even cant access the normal ui without reverse proxy. That also gives me a blank page and working title.
  4. I'm trying to use find and run a execdir on .rar files for mass unpacking but i'm getting the error that . is in the $path. Should'nt that be removed? "find: The current directory is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove the current directory from your $PATH (that is, remove "." or leading or trailing colons)" https://askubuntu.com/questions/621132/why-using-the-execdir-action-is-insecure-for-directory-which-is-in-the-path
  5. Can anybody help me with setting up FTPS or SFTP with ProFTPd? I cant seem to find an easy working guide out there
  6. Yes! Or change the organizr to /organizr? But then i need to see if i can somehow edit the base of organizr..
  7. Having troubles with the LE container All i did was edit the site-config/default and uncomment the 80 to 443 redirect with nano. [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 Server ready nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 nginx: [emerg] duplicate location "/" in /config/nginx/site-confs/default:28 -edit- Found the culprit. All the proxy-conf subfolder conf files have a /servicename and organizr just has the /