Gog

I'm far from a nginx expert but everything I check seems OK. Found @CHBMB's config problems on github but the only directive that seems to be needed, outside of the standard proxy.conf, is proxy_pass. Sorry...

You added it to the subdomain variable and registered a cname with your domain provider? You also have the custom network interface? Sent from my SM-G930W8 using Tapatalk

Good morning Did you create the custom network as explained in the proxy-confs/_readme ?

I want to do this too for my photo drive but from what i read it is not supported. It should be doable with external storage but I'm not there yet. Sent from my SM-G930W8 using Tapatalk

Try searching your mariadb appdata folder for "STATEMENT". You may have an orphan config file in there.

From your logs: impossible to write to binary log since BINLOG_FORMAT = STATEMENT But that should not happen since you set binlog_format=mixed I don't know why but in my config, that variable is under the [galera] section. I think I just uncommented there but the default config has it in [mysqld] like you. In any case, can you run the sql command "show variables like 'binlog_format'" on the DB, it will print the actual value of the parameter.

If you are going to go there, why not a rolling rule to switch to the next one line if you disconnect [emoji56] Sent from my SM-G930W8 using Tapatalk

Pick one I suggest nextcloud.tazire.duckdns.org because I don't know how to setup two letsencrypt on the same unraid you'll need to doublecheck config.php and nextcloud to make sure the domain is correct everwhere. I think the error ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container is because you are using a domain letsencrypt is not able to generate a key for but with the subdomain settings in letsncrypt, that should go away.

to access nextcloud, are you trying to use mynextcloud.duckdns.org or nextcloud.tazire.duckdns.org ? nextcloud.tazire.duckdns.org would be a subdomain. mynextcloud.duckdns.org would be a different domain and I think you need a separate letsencrypt instance for that.

I own my domain so not a pro with duckdns but I think the "Domain name" should be "tazire.duckdns.org" and "Subdomain(s)" should be "www,nextcloud"

Yes! config.php is the nextcloud file, custom.cnf is mariaDB, my bad. Assuming you replaced nextcloud.server.com in all the files by nextcloud.yourRealDomain.com and that port 4433 is forwarded to 443 in your nextcloud container, it looks good. 192.168.0.1 is your unraid's IP? nextcloud.txt should just be nextcloud though, no extension

Share your nextcloud custom.cnf and the letsencrypt file

Same behavior in and out of your LAN? When in the LAN, do you use the IP or the domain name? How does it resolve your domain from inside the LAN? Sent from my SM-G930W8 using Tapatalk

I can see an extra network layer adding delays on a resource intensive application but this is not it. Not for 20-30 seconds. It seems it takes time to reach the app. What about address resolution/DNS any chance your primary DNS server is on the fritz and it's timing out? Sent from my SM-G930W8 using Tapatalk Edit: typo

Good evening Can I suggest you update https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ to add the mariaDB binlog_format=mixed setting in the custom.cnf change and switch to using /letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf instead of copying the whole domain definition? There is one thing that I'm not sure I understand about the config. In nextcloud.subdomain.conf, I need to leave set $upstream_nextcloud nextcloud; proxy_pass https://$upstream_nextcloud:443; even though my container is configured on port 44333 (443 is letsencrypt) Is it the result of using the "private" docker network, reproxy0? It's resolving nextcloud:443 as 172.19.0.7:443, connecting through reproxy0? What is different about the network I defined versus the other docker network that are already defined? That would not work using the bridge network?

If nextcloud is accessible from outside your network, I doubt it's a port issue. Did you map the new drive in the nextcloud container definition? Sent from my SM-G930W8 using Tapatalk

Edit: Well, the GUI hates me but it seems the CLI is working we'll see what comes out in a bit.

I tried "sudo make me a sandwich" once but it was not a success. I'd like to see those Sandwich maker and relationship Manager modules Seriously my current headache is from managing container size in the image file. I have a leak somewhere but the commands and tools to diagnose are quite useless. The sandwich maker's uptime demands don't make for an easy work environment either. That being said it's probably not a match to the CA feature set. Sent from my SM-G930W8 using Tapatalk

Permissions look ok. Try to stop the container and edit core.conf with a unix-friendly editor like notepad++ add label to the plugin list, save the file and start the container

I googled your error and there is a guy saying it's related to deluge labels: https://github.com/Radarr/Radarr/issues/2502 Are you sure your labels are identical (check for case) in radarr and deluge? Anything in the deluge logs (appdata\binhex-delugevpn\deluged.log)?

Hi there In you deluge settings, in sonarr, does the test button work? Was the torrent fetched by sonarr? Under what label is it under in deluge? In Sonarr->activity, do you see it? In sonarr->system->logs do you see an entry about that file?

In your appdata\delugevpn folder, in core.conf, do you have something like this: "enabled_plugins": [ "Label" ], with label.conf containing the definition for all your label parameters? How are your permissions ? I'm like this: root@Tower:/mnt/cache/cache_only/appdata# ls -l drwxrwxr-x 10 nobody users 4096 May 31 00:00 binhex-delugevpn/ root@Tower:/mnt/cache/cache_only/appdata/binhex-delugevpn# ls -l -rw-rw-rw- 1 nobody users 2527 May 30 23:12 core.conf -rw-rw-rw- 1 nobody users 11765 May 31 00:00 label.conf

Well, I reinstalled everything and now I feel like a fool. It seems the Tautulli app doesn't support the basic authentication that I was enabling...

I had changed "enable http proxy" but not https. The only change I did on the proxy conf file was to remove the comments before the authentication parameters. I did a fresh tautulli reinstall just to be sure. That got rid of the weird https://_/tautulli/ but the android app is still not connecting. I guess I'm due for a fresh letsencrypt container too. Good thing that the new way of storing config makes that easy. I'll be back...

I'm trying to setup the reverse proxy for Tautulli. I'm posting here since I'm using the "standard" tautulli template. I can kick it to the other forum if you prefer. I hadn't touched the letsencrypt setup in a while so I reverted nginx\site-confs\default and nginx\nginx.conf to the default setup I got from the repo and moved my old default settings in proxy-confs subfolder and subdomain config files. Clean and easy setup, kudos on that one. I followed the instructions in nginx\proxy-confs\_readme and was able to get sonarr working with the samples as is. Tautulli on the other hand behaves a bit wonky. Disclaimer: tautulli reverse proxy never worked before, it's a new setup. All that to say that https://example.com/tautulli gets redirected to https://_/tautulli/ (that's in in chrome, can't be displayed in IE) while https://example.com/tautulli/home works. In letsencrypt error.log I see this: 2018/04/28 00:15:28 [error] 375#375: *105 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: pc_IP, server: _, request: "HEAD /tautulli/index HTTP/1.1", upstream: "http://internal_IP:8181/tautulli/index", host: "example.com", referrer: "https://example.com/tautulli/restart" http://internal_IP:8181/tautulli/index gets resolved to http://internal_IP:8181/tautulli/home when not going through the proxy. Everything else seems fine until I try to register the android app. When I register from http://internal_IP:8181/tautulli/settings#tab_tabs-android_app, everything works. If I register from https://example.com/tautulli/settings#tab_tabs-android_app, no dice, the device is not registered and doesn't work. Anyone has a clue? Thanks.