commander-flatus

A tracker I use heavily does not support Deluge 2.0 (the tracker is MaN if that matters). I'm trying to migrated to this docker, but I have 500 torrents that need to be moved (with labels and subdirectories). Has anyone done this? Is there an easy way?

I removed www.x.net. I still get 502 both inside the network and from the outside when using x.net/nextcloud. I can access it fine from inside the network on 192.168.1.99:1443/nextcloud My ISP does not block ports. My nginx log from swag: 2020/12/16 07:13:20 [error] 455#455: *211 nextcloud could not be resolved (110: Operation timed out), client: 174.235.137.23, server: _, request: "GET /nextcloud/ HTTP/2.0", host: "polydipsia.net" 2020/12/16 07:35:05 [error] 455#455: *276 nextcloud could not be resolved (110: Operation timed out), client: 192.168.1.1, server: _, request: "GET /nextcloud/status.php HTTP/1.1", host: "polydipsia.net:443" 2020/12/16 07:36:49 [error] 455#455: *309 nextcloud could not be resolved (110: Operation timed out), client: 192.168.1.1, server: _, request: "GET /nextcloud/status.php HTTP/1.1", host: "polydipsia.net:443" I'm open to reinstalling nextcloud, there's nothing special in the container. I have a concern there's something wonky in the settings. I'm running the most updated version (19, I believe). Can you point me to a tutorial on networking config with swag and nextcloud using swag's custom networks? This Unraid server has been up for years and I only do light maintenance. From my reading, the default bridge network isn't really recommended anymore (I believe it was at the time). Once again, thank you for the assistance.

Thank you for taking time to reply to my question. I tried that. I still get a 502 error when accessing via my custom domian. My SWAG nginx log shows: 2020/12/16 04:38:19 [error] 455#455: *1 nextcloud could not be resolved (110: Operation timed out), client: 192.168.1.1, server: _, request: "GET /nextcloud/ HTTP/2.0", host: "x.net" My nextcloud nginx error log shows: 020/12/16 04:38:37 [error] 375#375: *23 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.69, server: _, request: "GET /nextcloud/ocs/v2.php/apps/text/workspace?path=%2F HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.99:1443", referrer: "https://192.168.1.99:1443/nextcloud/index.php/apps/files/"

Can someone help me with this? Previously had Nextcloud working with Letsencrypt. Upgraded to SWAG and changed my local network numbering (went from 192.168.69.x to 192.168.1.x) and now I cannot get SWAG to get from my external domain to the local Nextcloud docker. I use a subfolder config. Here are what I think are the relevant details: First the log error shows: 2020/12/15 19:40:58 [error] 451#451: *12 nextcloud could not be resolved (110: Operation timed out), client: 192.168.1.1, server: _, request: "GET /nextcloud/ HTTP/2.0", host: "x.net" I have my Unifi security gateway mapping port 443 to the local network port 444 for SWAG: I can reach my Nextcloud instance on the local network on port 1443: I have used the default subfolder config in SWAG: ## Version 2020/12/09 # Assuming this container is called "swag", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['swag'], # 'overwritewebroot' => '/nextcloud', # 'overwrite.cli.url' => 'https://your-domain.com/nextcloud', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it. # 1 => 'your-domain.com', # ), # Redirects for DAV clients location = /.well-known/carddav { return 301 $scheme://$host/nextcloud/remote.php/dav; } location = /.well-known/caldav { return 301 $scheme://$host/nextcloud/remote.php/dav; } location /nextcloud { return 301 $scheme://$host/nextcloud/; } location ^~ /nextcloud/ { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; rewrite /nextcloud(.*) $1 break; proxy_max_temp_file_size 2048m; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_redirect off; proxy_ssl_session_reuse off; } Naturally, I appropriately renamed it to nextcloud.subfolder.conf I also edited the Nextcloud config as recommended in the nextcloud.subfolder.conf: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'x', 'passwordsalt' => 'x', 'secret' => 'x', 'trusted_domains' => array ( 0 => '192.168.1.99:1443', 1 => 'www.x.net', 2 => 'x.net', ), 'trusted_proxies' => array ( 0 => 'swag', ), 'overwritewebroot' => '/nextcloud', 'overwrite.cli.url' => 'https://x.net/nextcloud', 'dbtype' => 'mysql', 'version' => '18.0.6.0', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.99:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'x', 'dbpassword' => 'x', 'installed' => true, 'maintenance' => false, 'theme' => '', 'loglevel' => 0, 'mysql.utf8mb4' => true, ); In the browser, I keep getting "502 Bad Gateway" The Nextcloud error log shows this: 2020/12/15 19:41:53 [error] 374#374: *156 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.69, server: _, request: "GET /nextcloud/ocs/v2.php/apps/text/workspace?path=%2F HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.99:1443", referrer: "https://192.168.1.99:1443/nextcloud/index.php/apps/files/" I'm starting to lose my mind. Greatly appreciate any assistance. Happy Holidays and thanks!

I have shares mounted from an esxi host and I think it only allows NFS. Thanks for your help!

Can anyone help me? This is a Dell r720. Seems like something with networking or Docker but I'm having trouble narrowing it down. Any help is greatly appreciated. tun-diagnostics-20200613-0657.zip

Trying to display an image in a directory of images using this. I have a directory of jpg files. I've got this index.php in there: <?php $dirname = "/camera/"; $images = glob($dirname."*.jpg"); foreach($images as $image) { $list[] = $image; #echo '<img src="'.$image.'" /><br />'; } sort ($list); echo "<br><img src="."'".array_pop($list)."'"."><br><br>"; ?> I've tested the above and it works with php called from the shell. So this folder is in the docker at /camera/ here's my site config: upstream backend { server 192.168.69.94:19999; keepalive 64; } server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name _; location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'xxx' ssl_prefer_server_ciphers on; client_max_body_size 0; location /camera { root /; index index.php; } location = / { return 301 /htpc; } location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.69.94:8989/sonarr; } location /tautulli { include /config/nginx/proxy.conf; proxy_pass http://192.168.69.94:8181/tautulli; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.69.94:7878/radarr; } location /htpc { include /config/nginx/proxy.conf; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://192.168.69.94:8085/htpc; } location /downloads { include /config/nginx/proxy.conf; proxy_pass http://192.168.69.94:8112/; proxy_set_header X-Deluge-Base "/downloads/"; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.69.94:1443/nextcloud; } } It continues to give me the following error message: 2019/08/08 20:34:36 [error] 368#368: *5 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.69.1, server: _, request: "GET /camera/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "xx.net"

Thanks. Appreciate your rapid response. Everything works now. In case anyone comes across this response please note that you have to put “cloudflare” in the DNS plugin box for the docker. Sent from my iPhone using Tapatalk

Is there currently any kind of tutorial or work-around for making this work with an ISP that blocks all traffic on port 80 inbound? Since they disabled TLS-SNI validation and now require either HTTP (only works with port 80 open) I'm stuck. I did look into DNS validation but having that update dynamically seems non-trivial. Anyone? I miss using nextcloud as I was able to get at my whole server, securely, from anywhere in the world.

As the description indicates, every time you update / reinstall the container you have to reset the password. As a reminder, you do this from the Cli. docker exec -it openvpn-as passwd admin Also, you will have to re-add any uses you use beyond admin too. docker exec -it openvpn-as adduser <user> Nice and quick though!! Isn't this a huge security risk? Sent from my iPhone using Tapatalk

I found that the recent update reset the admin password to default. I've updated it again, but how do I avoid this with future updates? Sent from my iPhone using Tapatalk