Jump to content

Help on reverse proxy on Synology thanks


cnsixeyes
Go to solution Solved by cnsixeyes,

Recommended Posts

cnsixeyes

I'm trying to use https for remote connections using Synology reverse proxy and I don't have a   certificate

 

Here what I did so far:

1. Setup DDNS on my router ✔️

2. Create a reverse proxy setting on port 8921 to redirect to localhost:8096 ✔️

3.  Setup port forwarding on my router to forward port 8921 to my NAS port 8921 ✔️

4. Setup emby advance settings, I set  the secure connection mode to "Handled by reverse proxy". ✔️

but it didn't work,   Did I miss a setting somewhere?  Thanks for the help!

image.png.48e1e157c8234e122847c970ea079dcd.png

However, if I use local IP instead:

image.png.5de8c258169bb47b12ffc95dd52ab84a.png

 

screenshot my settings:

image.png.202a391ec613cbb5d004f4cbc4e69d38.png

image.png.6ec6e0c3374f8d5a71f8259225e5e15e.png

Link to comment
Share on other sites

Hi, do the requests show up in the emby server log? that will help tell you if it's even making it to emby server, which i would guess not.

Perhaps keep it simple and start http only first just to get the reverse proxy sorted out, then add https after that.

Link to comment
Share on other sites

  • Solution
cnsixeyes
48 minutes ago, Luke said:

Hi, do the requests show up in the emby server log? that will help tell you if it's even making it to emby server, which i would guess not.

Perhaps keep it simple and start http only first just to get the reverse proxy sorted out, then add https after that.

hi,thanks. 

I checked the logs,there is  no sign of the requests.

Maybe i should check the router again.

--------------

1.Checked the Attack Defence AGAIN, I found this:

image.thumb.png.f37d6032a4027104439b45aa35110eb9.png

All because of my sloppiness…… Permit the port 8921, problem solved!

Thanks Luke!

image.thumb.png.08cc3e45d8c72a9927a93052fde367a3.png

 

Link to comment
Share on other sites

On 4/1/2021 at 2:28 AM, cnsixeyes said:

hi,thanks. 

I checked the logs,there is  no sign of the requests.

Maybe i should check the router again.

--------------

1.Checked the Attack Defence AGAIN, I found this:

image.thumb.png.f37d6032a4027104439b45aa35110eb9.png

All because of my sloppiness…… Permit the port 8921, problem solved!

Thanks Luke!

image.thumb.png.08cc3e45d8c72a9927a93052fde367a3.png

 

HI, thanks for the feedback. Glad you were able to resolve it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...