Reverse proxy, Forbidden 403 error

Currently reading
Reverse proxy, Forbidden 403 error

2
1
NAS
DS220+
Operating system
  1. Windows
Mobile operating system
  1. Android
I am relatively new to reverse proxy. I have a personal domain, mydomain.net, and I am setting up reverse proxies for each docker container on my system. For example, Portainer should be accessed with 'port.mydomain.net'.

My reverse proxy (for all sites) is set up similarly to as follows:
1700064597962.png


However, when I attempt to access it through subdomain.mydomain.net, I keep coming back to:

Forbidden
You don't have permission to acccess this resource.

If I use 192.168.1.234:9000, I can access the docker container without issue. The weird thing about this is that it has worked, and just when I think I had figured it out, it doesn't work. If I reboot the NAS, for example, it stops working. What am I doing wrong? I would love to be able to access everything without having to use the nasname.synology.me tld to access everything.
 
Solution
I presume 1) your domain DNS records point to your current WAN IP; 2) you have opened port 443 to your NAS; and 3) have no NAS firewall rules interfering… If so, try using your NAS IP in place of “localhost” and see if that helps.
I presume 1) your domain DNS records point to your current WAN IP; 2) you have opened port 443 to your NAS; and 3) have no NAS firewall rules interfering… If so, try using your NAS IP in place of “localhost” and see if that helps.
 
Upvote 0
Solution
If you are trying to access the NAS from the a LAN device then your router may not support local loopback: which is a mechanism whereby it recognises LAN outbound requests destined to its WAN IP and, for destination ports that it has forwarding rules, routes the request back to the local destination device.
 
Upvote 0
I presume 1) your domain DNS records point to your current WAN IP; 2) you have opened port 443 to your NAS; and 3) have no NAS firewall rules interfering… If so, try using your NAS IP in place of “localhost” and see if that helps.
I think it was point 1 that was messing me up. And it was a simple fix, honestly. We'll have to see if I continue to have success on future endeavors, but thank you for your quick troubleshooting guide!
 
Upvote 0

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.

Old thread notice: There have been no replies in this thread for quite some time. The last reply was on .
The content in this thread may no longer be relevant. It might be better to open a new thread instead.

Similar threads

  • Question
Ofc you can make a single compose for this no problem. Personally I like to separate front end apps from...
Replies
10
Views
1,086
I accessed to log and when I trying connect I have message: "SSTP_DUPLEX_POST...
Replies
9
Views
1,522
  • Solved
Glad it’s working. Now you can help the next person! No reward necessary 😎
Replies
14
Views
2,115
The thing is... Too many users freeload off Marius and then come to the forums for assistance. Give Marius...
Replies
4
Views
1,624
I'm hoping someone can help confirm if this is an issue with my set up, or an issue introduced by DSM 7. I...
Replies
0
Views
1,140
I don't want to use NPM or any other software; I found a solution that works with Synology's built-in...
Replies
4
Views
2,417

Welcome to SynoForum.com!

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

Registration is free, easy and fast!

Back
Top