CyberMew

Sorry but I don't understand, ah so you mean so we can't ever do something like https://ombi.domain.com:12345 because https overwrites the 12345 port with 443? If so that is ok for me, since I want https://ombi.domain.com to point to http://192.168.1.55:12345. The problem now is I'm getting ERR_CONNECTION_REFUSED when accessing https://ombi.domain.com. I manage to solve Point 1 by adding this server block of code in case someone is looking for it too: server { listen 80 default_server; server_name _; return 301 https://$host$request_uri; }

I got it working lets encrypt part now, but however the server part doesnt seems to be working.. Currently ombi.domain.com is pointing to my server's wan ip address. I have portforwarding done for 12345. If I access http://ombi.domain.com:12345, it loads correctly. However if I do https://ombi.domain.com:12345, it redirects me back to http. I actually wanted it to: 1. when accessing http, redirect to https 2. when access subdomain, it loads ombi, no manual input of port required. This is my current default file: server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name ombi.*; # removed the default ssl stuff here for brevity client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.55:12345; } } Not sure if I am doing this correctly?

I have a main domain that is under hosting by dreamhost and bought/handled by namecheap. My www.domain.com is already https by lets encrypt under dreamhost hosting. What should I do in order to get mysubdomains.domain working under our lets encrypt, no matter the ports? Currently I have ddns to sub1.domain.com pointing to namecheap name servers and namecheap is pointing the subdomain to my unraid machine via A + Dynamic DNS Record. Hence something like sub1.domain.com:9091 is pointing to my transmission docker without issues. However I want it to be directed/protected by https, and same if I want sub2.domain.com (CNAME to sub1.domain.com). Do I need to have hosting for those subdomains or something? Do I have to turn off SSL for my domain in dreamhost for it to work?

6.5.3

I just upgraded to the latest python 2.7.14 via the nerd pack (not sure what python version was running before nor how it was installed), but for some reason subliminal broke. easy_install too, any idea how I can revert back or fix this?

Thanks! That is really helpful, the /mnt trick seems to be very useful (I created another host path in settings, hope it didn't break anything that also uses /mnt internally), though I guess giving the whole /mnt might be a little too much. The link that you gave is also very useful for understanding as well. I'm already used to sab so I'm going with that but I'm changing over to Radarr from CP soon since CP isn't that reliable for me sometimes.

My current setup is such that Sabnzbd docker volumes is pointing to /mnt/cache/appdata/sabnzbd/complete-download for Downloads and /mnt/cache/appdata/sabnzbd/incomplete-download for Incomplete Downloads. So from my understanding so far, Sonarr needs to point it's container /downloads path to /mnt/cache/appdata/sabnzbd/complete-download instead of what I am currently setting it as (/mnt/cache/appdata/sonarr/downloads)? Assuming the above is correct, then how would I get Sonarr to move the downloaded files to it's final destination? I am also assuming it's through the /tv path in Sonarr? So this would mean I need to change ALL of my current config in Sonarr from /mnt/user/TVShows/* to /tv/TVShows/* right? Thank you very much for your help!

Thanks, think that's the way to go for now. I finally got time to configure this again, and having some confusion in making it work similar to Phaze plugin. With Phaze plugin we had direct access to the file system, so the Categories had their path in absolute format. However with docker, and that I also moved Sonarr from Phaze over to docker, Sonarr will not have access to Sabnzbd's final download folder. How would Sonarr monitor the tv category and the file path (/Downloads that's visible in Sabnzbd) and move the file (that Sonarr can't see I think?) in the correct folder that's been set inside Sonarr?

Yea was playing around. Any idea how to use port 9090 as the default or is this just the way it is for this docker?

I set Port 1 to 7979, Port 2 to 9090 (the default), went into sabnzbd settings and edited the port from 8080 to 9090, but it didnt work, it's stuck with 8080. Even tried editing the config.ini directly, no go. Seems like there's just no way to switch the ports..

I'm trying to shift from PhaZe plugins to Dockers, and for sabnzbd, I'm used to using port 9090. However in this Docker, there are 2 ports being shown, 8080 and 9090. Why is there 2 of the ports and how can I make it only use 9090? 8080 is currently taken up by unifi already.

Copied over from plexpy the database files and renamed them to tautulli and also copied over the config file to the new tautulli folder, no issues. Seems to be working great.

Sorry I thought I had replied but to answer your question no I didn't have any errors. I think I had, but I just deleted the files and tried again a few times and then it worked.

Thanks! This docker worked great.

Which docker is the latest and maintained? I followed one of the posts and the node is so old..

I've already stopped this container. Ombi is not working well with mono (iirc) and the author is trying to rewrite everything. I'm getting frequent app crashes causing it to relaunch or the app opening many file handles which causes everything to lock up after some time. The app could be better but at this stage it is not useable at all for me. It works fine in a windows environment though.

Thanks, fixed it. It was a direct copy and paste oops ?. Now I'm wondering why the redirection is no longer working. No errors in logs too..

Any idea why I'm getting these in the log: nginx: [emerg] unknown "unraid" variable

Awesome thanks! Anyway I though it's suppose to be automated? Why the need for manual update?

Nvm. I switch back to stable. And now 2.2 is released but the docker is not updating to the latest version. The logs is still downloading 2.1.1336.

Is there a current workaround?

If I switched to early access preview branch how do I update the software?

Thanks, I got it to load now. And I had to do port forwarding. Now I need to find out how to block http requests or redirect to https version. Any idea how do I edit the 443 page?

Yea it says could not connect to server if I tried to access the ssl port or non ssl port. Then docker died. Something like this happened: /var/run/s6/etc/cont-init.d/50-config: line 105: cd: /config/keys/letsencrypt: No such file or directory there are no other errors, just warnings.

Thanks. I did and it created fine. How do I know if it's working? I tried to access my Sub domain with the http port or even the 443 port but nothing happened..