Lynxphp

Thanks for your answers and sorry for my late response. Yes. Could this be causing the issue? I have to keep my ISP router on as it provides the TV connection. My pfsense box is in the DMZ of the ISP router. With this setting, I don't need to forward the ports from the ISP to the pfsense box. Yes Thanks for the tip. I tried it. Still no luck getting local access... My Custom options in the DNS Resolver (which is enabled) now look like this: server: private-domain: "unraid.net" local-zone: "nextcloud.XXX.duckdns.org" redirect local-data: "nextcloud.XXX.duckdns.org 3600 IN A 19.16.17.101" Are there any other troubleshooting steps I could take? Or steps to provide you guys with more accurate information regarding my issue ? oh. I guess I'll have to change that :(. Thanks for the heads up.

I already posted a few days ago regarding setting up letsencrypt for nextcloud and got from no access at all to remote access only, which i am very happy about. Remote access works perfectly with duckdns but i still can't get local access and that is what i am trying to fix. I will try to summarize the relevant information here. I run a pfsense router which is in the DMZ behind my ISP router. Both have NAT enabled. I have port forwarding rules setup and as remote access works, i tend to think that they are not the problem. I have a host override setup in pfsense: Here are the results of nslookup and tracert from a computer within the same network (behind pfsense) as the unraid server on which letsencrypt and nextcloud are running: My interpretation is that the dns override works as it is correctly resolved with the external (internet) ip. Is that correct? Or should a local dns lookup response be the local ip adress? The fact that the dns seems to work leads me to believe that the problem lies with my configuration of letsencrypt (possibly nextcloud?). Here is the result of a tracert showing the connection timing out: My current configuration of LE and nextcloud: appdata/letsencrypt/nginx/site-confs/nextcloud server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } } appdata/nextcloud/www/nextcloud/config/config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'XXX', 'passwordsalt' => 'XXX', 'secret' => 'XXX', 'trusted_domains' => array ( 0 => '19.16.17.101:444', 1 => 'nextcloud.XXX.duckdns.org', ), 'dbtype' => 'mysql', 'version' => '16.0.1.1', 'overwrite.cli.url' => 'https://nextcloud.XXX.duckdns.org', 'overwritehost' => 'nextcloud.XXX.duckdns.org', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '19.16.17.101:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'XXX', 'dbpassword' => 'XXX', 'installed' => true, ); I am quite a networking newbie. I have tried to read and inform myself as much as i could, but i can't seem to figure this out. Any help would be greatly appreciated.

Im starting to think that my port 80 is blocked by my ISP. I'm not sure how bad this is, as i can still reach nextcloud externally on 443. I tried all the NAT reflection options with rebooting after each change, but still no succes..

Thanks for the tip @blaine07. I have no problems reaching nextcloud externally, which leads to me to think that my port forwarding rules are okay. It's only internally that the connection times out. Heres a screen of my rules:

Thanks for your correction. I previously used mydomain.duckdns.org to reach nextcloud directly. I now made the change in the nextcloud and letsencrypt config to have nextcloud at nextcloud.mydomain.duckdns.org. I can reach nextcloud remotely, but still not locally (timeout) :(. Here is my Host override in the DNS resolver:

Thanks for the suggestion. I still can't get local acces...

Thanks! I got remote access! However, still no access from the local network. I only setup my pfsense router after moving (with my new ISP router that doesnt support NAT loopback). I never got local access working with this ISP router. I tried unchecking "block private networks and loopback addresses" (both on WAN and LAN) but no change. canyouseeme.org reports that port 443 is open, 80 is not. I tried setting up a NAT forward rule to be able to gain local access, but no succes: Any suggestion?

Hi I previously had a working nextcloud instance with reverse proxy, but i kept having problems after i moved and got a new ISP router. I have made several unsuccesful attempts in the past months to get it working so tonight i'm finally posting here and hope someone can help. Nextcloud is setup and works just fine on the local network. Let's encrypt is able to get new certs and to renew old ones. My issues lies with setting up the reverse proxy to access nextcloud with my duckdns URL. It times out whenever i try to reach the site from behind the pfsense router, the internet or behind the isp router. I would very much appreciate any help or suggestion. Below i posted my config. My network: The Pfsense Router is in the DMZ of the ISP router Here are my port forwards in both routers (first ISP router then pfsense) NAT loopback is enabled in the pfsense port forwards. Here is my letsencrypt template: appdata/letsencrypt/nginx/site-confs/nextcloud server { listen 443 ssl; server_name XXX.duckdns.org; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ###ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://19.16.17.101:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } appdata/nextcloud/www/nextcloud/config/config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'XXX', 'passwordsalt' => 'XXX', 'secret' => 'XXX', 'trusted_domains' => array ( 0 => '19.16.17.101:444', 1 => 'XXX.duckdns.org', ), 'dbtype' => 'mysql', 'version' => '16.0.1.1', 'overwrite.cli.url' => 'https://XXX.duckdns.org', 'overwritehost' => 'XXX.duckdns.org', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '19.16.17.101:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'XXX', 'dbpassword' => 'XXX', 'installed' => true, );

I have also been trying to get synpase to work on my unraid box (still running 6.6.7). I installed Postres without a problem. I'm having a similar issues as you relink with the synpase docker. I downloaded a clean homeserver.yaml from https://raw.githubusercontent.com/matrix-org/synapse/master/docker/conf/homeserver.yaml When i start Synpase, it immediately crashes. I joined a screenshot of my container template and here is the console log for the synapse container: Traceback (most recent call last): File "/usr/local/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/local/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/local/lib/python3.6/site-packages/synapse/app/homeserver.py", line 661, in <module> main() File "/usr/local/lib/python3.6/site-packages/synapse/app/homeserver.py", line 656, in main hs = setup(sys.argv[1:]) File "/usr/local/lib/python3.6/site-packages/synapse/app/homeserver.py", line 329, in setup config_options, File "/usr/local/lib/python3.6/site-packages/synapse/config/_base.py", line 362, in load_or_generate_config generate_keys=generate_keys, File "/usr/local/lib/python3.6/site-packages/synapse/config/_base.py", line 380, in read_config_files yaml_config = self.read_config_file(config_file) File "/usr/local/lib/python3.6/site-packages/synapse/config/_base.py", line 140, in read_config_file return yaml.safe_load(file_stream) File "/usr/local/lib/python3.6/site-packages/yaml/__init__.py", line 162, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.6/site-packages/yaml/__init__.py", line 114, in load return loader.get_single_data() File "/usr/local/lib/python3.6/site-packages/yaml/constructor.py", line 41, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.6/site-packages/yaml/composer.py", line 35, in get_single_node if not self.check_event(StreamEndEvent): File "/usr/local/lib/python3.6/site-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.6/site-packages/yaml/parser.py", line 143, in parse_implicit_document_start StreamEndToken): File "/usr/local/lib/python3.6/site-packages/yaml/scanner.py", line 116, in check_token self.fetch_more_tokens() File "/usr/local/lib/python3.6/site-packages/yaml/scanner.py", line 260, in fetch_more_tokens self.get_mark()) yaml.scanner.ScannerError: while scanning for the next token found character '%' that cannot start any token in "/config/homeserver.yaml", line 5, column 2 Traceback (most recent call last): File "/start.py", line 76, in <module> subprocess.check_output(args + ["--generate-keys"]) File "/usr/local/lib/python3.6/subprocess.py", line 356, in check_output **kwargs).stdout File "/usr/local/lib/python3.6/subprocess.py", line 438, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['python', '-m', 'synapse.app.homeserver', '--config-path', '/config/', '--keys-directory', '/data', '--generate-keys']' returned non-zero exit status 1. Would really appreciate any tip as to how to setup synapse. One part of it is setting up my let's encrypt reverse proxy to work with it. To answer your question, afaik you just paste your command in the "Post Arguments" section of the container template (in advanced view).

Works like a charm! Thanks. I don't use my main nextcloud instance (which is hosted on unraid) to store the key, but rather a free provider https://woelkli.com/en where i only keep a duplicati encrypted backup of some stuff. I'm aware it's not an ideal solution, but it will do for my needs.

Thanks for the excellent video! I adapted your idea to a file hosted on a nextcloud service, accessing the file with curl via webdav: curl -u user:pass -o /root/keyfile https://mynextcloud.com/remote.php/webdav/keyfile This works flawlessly. However, it takes a few seconds to complete (usually around 5-7s). The thing is, this seems to be too long for unraid, as it tries to open the encrypted drives before the key is downloaded (that is my understanding at least). The array fails to autostart (see log below), but if i start it manually a few seconds later, it manages to open the key file, open the drives and start the array. May 29 22:21:42 BackupTower emhttpd: shcmd (33): udevadm settle May 29 22:21:43 BackupTower emhttpd: Opening encrypted volumes... May 29 22:21:43 BackupTower emhttpd: shcmd (35): /usr/sbin/cryptsetup luksOpen /dev/md1 md1 --key-file /root/keyfile May 29 22:21:43 BackupTower kernel: device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: [email protected] May 29 22:21:43 BackupTower root: Failed to open key file. May 29 22:21:43 BackupTower emhttpd: shcmd (35): exit status: 1 May 29 22:21:43 BackupTower emhttpd: shcmd (37): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --key-file /root/keyfile May 29 22:21:43 BackupTower root: Failed to open key file. May 29 22:21:43 BackupTower emhttpd: shcmd (37): exit status: 1 May 29 22:21:43 BackupTower emhttpd: shcmd (39): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --key-file /root/keyfile May 29 22:21:43 BackupTower root: Failed to open key file. May 29 22:21:43 BackupTower emhttpd: shcmd (39): exit status: 1 May 29 22:21:43 BackupTower emhttpd: Missing encryption key May 29 22:21:43 BackupTower kernel: mdcmd (40): stop May 29 22:21:43 BackupTower kernel: md1: stopping May 29 22:21:43 BackupTower kernel: md2: stopping May 29 22:21:43 BackupTower kernel: md3: stopping May 29 22:21:43 BackupTower avahi-daemon[9011]: Server startup complete. Host name is BackupTower.local. Local service cookie is ********* Any suggestion as to how i could either set a delay on the autostart or maybe force a new array start a few seconds later? Any help would be much appreciated.

Hi, I allow myself to quote a post i made about a week ago which got lost in the conversation and to which i never got a reply. In the meantime I'm running the apps i need in a win10 VM with perfect privacy's VPN software. However i'd really like to use dockers to save resources. Would appreciate any tip!

Hi, First of all, a big thanks to you binhex for your work and for disseminating it freely. I am using perfect privacy VPN and have tried setting up delugeVPN with it. Unfortunately i can't seem to get it working. I put one .ovpn from my VPN provider in the openvpn folder of Deluge. I removed the following lines from the .ovpn file: tun-ipv6 down /etc/openvpn/update-resolv-conf up /etc/openvpn/update-resolv-conf I also set the NAME_SERVERS to the dns server from perfect privacy for the location I chose (Zurich). However, the page of the webgui is still blank Any idea as to what my issue is? supervisord.log

I didn't touch the permissions. I just wiped everything and reinstalled the nextcloud docker. I can now install apps in the webui from the local IP, but not from mysubdomain.duckdns.org I also have the following security warnings when accessing the ui from duckdns: I had managed to fix this warnings in my previous install by commenting some lines in a nextcloud config file. But i now wonder if this also has to do with my issue installing apps? Does it have something to do with my whole letsencrypt / duckdns / nextcloud setup? Any ideas suggestion?

That's what i thought as well.. I also posted on nextclouds support forum. If I get an answer there i'll report back here (and vice versa). Could it have with unraid permissions to do?