in ,

How to Setup a Reverse Proxy in OMV with Let’s Encrypt SSL for Sabnzbd, Radarr, Sonarr and Transmission

Setup a Reverse Proxy with Let's Encrypt SSL

In the previous pages of this tutorial I’ve shown you how you can make the OMV plugins Transmission, SABnzbd, Sonarr and Radarr accessible over the web with a Let’s Encrypt SSL-encrypted Reverse Proxy.

If you’re not into how-to’s or you’re not a stranger to Nginx and Terminals, I included the complete configuration file on this page. So you can start digging into it yourself.

A Complete Configuration-file for a Reverse Proxy in OpenMediaVault

This file should be located under /etc/nginx/openmediavault-webgui.d. Make sure to replace nas.yourdomain.com with your NAS’ web address and the IP with your NAS’ local IP.

filename: apps.conf

server_name nas.yourdomain.com 192.168.xxx.xxx;
location /sabnzbd {
proxy_pass https://localhost:9080/sabnzbd;
}
location /sonarr {
proxy_pass http://localhost:8989/sonarr;
}
location /radarr {
proxy_pass http://localhost:7878/radarr;
}
location /transmission {
proxy_pass http://localhost:9091/transmission;
}
location /nginx_status {
stub_status on;
access_log off;
}
view raw apps.conf hosted with ❤ by GitHub

Written by Daan van den Bergh

Magento 2 Back-end Developer with a passion for trainlifting, airplane-gliding, hunting trees and creating fake hobbies.

12 Comments

Leave a Reply
  1. You don’t need Sonarr’s “Enable SSL” if you’re implementing the HTTPS encryption with Let’s Encrypt at the reverse proxy level, I assume.

  2. While I appreciate the time you took to write this article, the title is incredibly misleading. I came here for info on sonarr reverse proxying yet I can only find sabnzbd, with a configuration that will result in a imperfect configuration at that.

  3. This tutorial is outdated. You should consider revising it as certain things changed in Letsencrypt interface.

  4. Hi Daan,

    Thanks so much for your useful guide! I set this up months ago and it’s been working perfectly up until yesterday. I haven’t changed any settings but it’s just stopped working :( I rebooted my router, double checked the port forwarding was still in place, checked the certificate was still valid etc and nada :( I can see that DuckDNS is working correctly also, it’s correctly obtaining my WAN IP.

    Do you have any ideas?

  5. I’m a bit confused when you say that the NAS needs to be accessible from outside. So if I want to access OMV, I need to type for example mydomain.com:portToMyNAS. Then my router will forward this request to my NAS and the login page will be displayed. Is this what you mean?

    Also isn’t this a security risk – shouldn’t we use an VPN service instead of leaving it directly open to the public internet?

    • If you want to use a VPN, then using a reverse proxy isn’t relevant IMO. You can just access your NAS from inside your VPN.

      But to answer your question. It’s not necessarily a security risk if OMV (your NAS’s IP, on port 443/80) is accessible over WAN.

  6. Hi Daan,
    I’ve successfully installed the certificate, and installed sonarr – used your config for the ngnix. The problem is that i get the following web page when I try to load mydomain.com/sonarr: https://imgur.com/a/HUxfC16 (this image shows my internal IP, but the same thing happens if I use my domain)

    I’ve port forwarded port 80 and 443 in my router to my OMV server. Also the OMV server has ports 80 and 443 setup (in general settings > web administration).
    What am I doing wrong?
    Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.