mmenanno

Hey team! Wondering if anyone might have an advice on how to fix my proxy config for the stash app. I followed some of the other conf files as examples when creating it: # make sure that your dns has a cname set for stash server { listen 443 ssl; listen [::]:443 ssl; server_name stash.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app stash; set $upstream_port 9999; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } It works for the most part with a very small exception, when I access the app through the reverse proxy I get these errors in the logs: Wondering if anyone might have advice on how I can alter my conf file to support the calls being blocked there. Thanks!

I'm having the same thing with the HOOBS container. If I use Bridge or Host the WebUI option shows up, as soon as I switch to br0 (which I need to do for the container to work for me) the option disappears. I'm curious if you test on that docker if you can replicate the behaviour as well or if it works as intended for you. It seems to be container specific (I have no idea why) but the WebUi doesn't disappear if I use br0 on the linuxserver plex docker as an example. Here is an applicable XML for my HOOBS one: my-HOOBS.xml

That didn't work but I got a new router today and it magically works, so I guess something was set wrong in the old one.

Yup I can get into the interface if I manually type out the IP and port number, still no better luck with the "Accessory not found" error though.

Am I doing something wrong still here? I tried assigning it an IP. But when I do, it seems to think there are no longer any port mappings? And it still doesn't work when I try using the code. The WebUI option on the docker also disappears (even with fixing the typo in the template)

Are there specific network requirements for this? I got the docker all set up but whenever I scan the QR code I get "Accessory not found" after it tries for awhile. I've already forwarded all the ports on my router.

Sorry i flip flopped some wording there but yes that is how I have it set up. The remote one is in host mode. I replaced the line to make it: proxy_pass http://192.168.0.88:32400; which is the host ip, and in the plex server settings I filled in "Custom server access URLs" with my domain https://plex.thedomainiamusing.xyz:443 But then I run into: The instances of Cerberus (the desired remote plex instance) are duplicated https://monosnap.com/direct/Zm2FD9Pzdj1X3hIpBg3sQNB2FvQHys trying to click any of my libraries just reloads the plex dashboard and trying to click either of the two instances listed in activity gives me a no soup for you error: https://monosnap.com/direct/PbS0MMy3GDvqYhIoKoc8cJly0yA7Rj Both these servers work fine directly from the local ip or launched though the plex.tv page. Only have these issues behind the letencrypt reverse proxy. Not sure what would cause this.

Hopefully someone here can help me out. I've been having an odd issue. First I'll give some details about my setup. My server has two instances of plex: plex which is run in Host mode. plex-eros which is run in br0 bridge mode. https://monosnap.com/direct/GhwdEpmQ069JRyrl9oXW7rwe0pE59g Only plex is shared with others and needs to be accessible outside my network with the reverse proxy. If I leave https://$upstream_plex:32400 in the config then I get a "502 Bad Gateway" error If I configure it as if I'm in bridge mode and make it: https://192.168.0.88:32400 I am then able to load the plex page, log into my user but then things get weird. The instances of Cerberus (the regular plex instance) are duplicated https://monosnap.com/direct/Zm2FD9Pzdj1X3hIpBg3sQNB2FvQHys trying to click any of my libraries just reloads the plex dashboard and trying to click either of the two instances listed in activity gives me a no soup for you error: https://monosnap.com/direct/PbS0MMy3GDvqYhIoKoc8cJly0yA7Rj Both these servers work fine directly from the local ip or launched though the plex.tv page. Only have these issues behind the letencrypt reverse proxy. Any idea what I'm doing wrong?

Perfect! Thanks for all your help! Any idea on if there a way within letsencrypt to auto forward http to https? So if I type in transmission.mydomain.com it goes to https://transmission.mydomain.com? EDIT: Nevermind found it in the defaut file in the site-confs folder.

Furthering my setup, I'm trying to get my reverse proxy set up for all my services. I did transmission first, removing .sample from the config name, restarting lets encrypt and it worked beautifully. However the second one I went to do was sonarr, and after removing .sample from the sonarr.subdomain.conf.sample and restarting letencrypt, the log started spamming this error: nginx: [emerg] unexpected end of file, expecting "}" in /config/nginx/proxy-confs/sonarr.subdomain.conf:36 Which I can't really figure out why since the character it is asking for seems to be exactly where it should be and I haven't changed any settings on it: # make sure that your dns has a cname set for sonarr and that your sonarr container is not using a base url server { listen 443 ssl; server_name sonarr.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_sonarr sonarr; proxy_pass http://$upstream_sonarr:8989; } location ^~ /api { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_sonarr sonarr; proxy_pass http://$upstream_sonarr:8989; } Anyone know what is going on here? Also is there a way within letsencrypt to auto forward http to https? So if I type in transmission.mydomain.com it goes to https://transmission.mydomain.com ?

Ahhhhh I see, I misunderstood the settings in my router and thought that was the case with how I had it set. Internal to external port forwarding is under "Virtual Servers" in my router. All working now though!

So I am so lost in where I am going wrong here and I hope it is something obvious that I'm just missing. Below is the log I get from the docker My unraid network settings: My LetsEncrypt docker settings: My port forwarding in my router: Based on other posts here I've already checked and made sure my ISP doesn't block port 80. I also tested to make sure the port forwarding is working correctly by temporarily putting another docker on the ports I have letsencrypt set to and it was accessible externally from both, so the forwarding looks correct. My server is using duckdns to keep my IP updated. Anyone know what might be going on here or have things I can try?

That worked perfectly! Thanks!

Anyone have any suggestions on this yet? I'm now on unRAID 6.5.0 and Fix Common Problems 2018.03.14b and the issue still persists.

When I first set up the plugin I accidentally told the plugin to ignore the FTP warnings. I don't want this to be the case any more however whenever I click the Monitor Warning/Error button, the items stay. What is strange about this is if I tell it to ignore the warning on other items, I am able to set them to Monitor again just fine, it is just these two items that are stuck. This has persisted through multiple restarts, rescans, and versions of the plugin. I'm currently on unRAID 6.4.1 and Fix Common Problems 2018-02-14 Any help to get these monitoring again would be great.