Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

Issues using subdomains to access applications with reverse proxies

As an Amazon Associate, we may earn commissions from qualifying purchases. Learn more...

3
1
NAS
DS920+
Operating system
  1. macOS
  2. Windows
Mobile operating system
  1. iOS
Hi everyone!

I've been stuck for a while configuring my DSM to access applications using subdomains. Specifically, I'd like to reach Radarr by going to radarr.[domain].nl. I was able to successfully set up access to my DSM by going to server.[domain].nl by opening ports 443 and 80 and creating a CNAME record that forwards to the DDNS.

Here's a screenshot of my reverse proxy settings for Radarr. I also have an SSL certificate for each subdomain using Let's Encrypt.

1730914625120.webp


The issue I'm facing is that whenever I go to radarr.[domain].nl, I get a 403 error.

1730914752873.webp


Has anyone experienced a similar issue, or does anyone have ideas on what I might be missing? Any help would be greatly appreciated!

Thanks in advance!
 
Try 2 things.

On the destination side, change the protocol to HTTP (from https), as radarr by default works on non-HTTPS. On top of this, for the hostname change localhost to your NAS local IP. See if these changes will make a difference.
 
Last edited:
Thanks for you quick reply! And it works indeed, kinda. When I go to radarr.domain.nl it goes by default to http://radarr.domain.nl which gives me the same error. When I manually type https:// it works! So I think we're almost there! :)

Do you know how to always go to https:// when typing the url?

Thanks again!

edit: I also did the same with request.domain.nl which leads to Overseerr. That one does automatically direct to https. I don't know why, they have the exact same settings other than the port number
 
The http setting just need to be in the destination parameter. The source still needs to be https with a valid certificate. So you do actually target the url using https but the reverse proxy will internally push those requests onto http as radarr is running on http inside docker.
 
Yeeey I got everything working now! Thank you so much. Overseerr was installed using docker and Radarr using the Package Center. Overseerr worked instantly setting indeed https to http. For radarr i had to also enable HSTS.

Thanks again!
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

A simple enough task, but I’m missing something somewhere. I’m new to ipv6, so do please state the...
Replies
0
Views
246
Maybe use a single port over reverse proxy, and push all other services via that single port so you do not...
Replies
1
Views
1,008
Well Container Manager is the new front-end to Docker. I would expect it to be able to run DNSfilter in...
Replies
1
Views
775
  • Question Question
Just thought about another location to change IP if you have a specific app NAS control panel - Login...
Replies
1
Views
1,063
  • Question Question
I have been using subdomains like git.mydomain.synology.me blog.mydomain.synology.me for years. But this...
Replies
0
Views
211

Thread Tags

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending content in this forum

Back
Top