Jump to content

Access to the synology domain


klapvogn
Go to solution Solved by Luke,

Recommended Posts

klapvogn

Hi,

I am trying to get my Synology DS2411+ to let me connect to it with it's domain

https://emby.grotten.synology.me


I have followed various guides I have have gotten this : 
syno_emby.png.ab1858c3507ca9d05d6ca889631c49e4.png 

And when I ping the address I get 10.0.0.54 And I how no clue why ?

Link to comment
Share on other sites

matrixn
3 hours ago, klapvogn said:

Hi,

I am trying to get my Synology DS2411+ to let me connect to it with it's domain

https://emby.grotten.synology.me


I have followed various guides I have have gotten this : 
syno_emby.png.ab1858c3507ca9d05d6ca889631c49e4.png 

And when I ping the address I get 10.0.0.54 And I how no clue why ?

The hostname should be 127.0.0.1 or localhost, never external ip or internal one from your intranet!

Link to comment
Share on other sites

matrixn
3 hours ago, klapvogn said:

So like this :
syno_emby02.png.ead5d70a76d3b865709faf4f1c31d183.png

I am unsure about 'External Address
syno_emby03.png.c48a24d9558fc4d35d1c1b43be6a4070.png

The reverse proxy is set correctly now, but your external address is an issue ( 10.0.0.54 - this looks to me like a corporate proxy or intranet ) is an internal ip address. you should set there the external ip address ( the one you see when you browse from within that network to this address - (https://whatismyipaddress.com/)

Link to comment
Share on other sites

klapvogn
Posted (edited)

Hi,

I have manged to get it to working. by using my remote server like this: 

1 : DDNS is disabled
2 : Reverse Proxy is like this:
3  : all SSL certificates are handled by my cloudflare tunnel on the remote server

Source HTTP/2 Destination
https://domain.tld:5443 (DSM) enabled https://localhost:5080
https://domain.tld:9001 (Portainer) enabled https://localhost:9000
https://domain.tld:8097 (Emby) enabled https://localhost:8096


At my cloudflare instance I have :

Public hostname Service
emby.domain.tld http://<HOME IP>:8096
portainer.domain.tld http://<HOME IP>:9000
grotten.domain.tld http://<HOME IP>:5080

 

Edited by klapvogn
Link to comment
Share on other sites

klapvogn

I noticed that Emby connect does not work, no idea if it has something to do with docker..

all I get is the docker ip:8096

Link to comment
Share on other sites

On 3/24/2024 at 9:37 AM, klapvogn said:

I noticed that Emby connect does not work, no idea if it has something to do with docker..

all I get is the docker ip:8096

Hi, what makes you think Emby Connect doesn't work?

What exactly do you mean by "all I get is the docker ip:8096" ?

Link to comment
Share on other sites

klapvogn

Hi,

What I mean is that I only get
emby01.png.be88eb1295d57b7cb804c0e104f23f70.png

Thats the docker ip which It can't connect to, and for the ip in the emby dashboard it show https://domain.tld:8920 which does not work for me, I need to remove the :8920 then it will work

Link to comment
Share on other sites

  • Solution

Then it sounds like you want to set the public facing https port in emby server network settings to 443. 

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...