Latest Server Update Disabled "Allow Remote Connections"

[Luke 42077]

21 minutes ago, JulesC said:

80 and 443

None of this has changed

That doesn't really answer much. What rules did you setup in your router port forwarding? 

[JulesC 51]

Service Name	External & Internal Port	Internal IP Address
HTTP	80	my IP address
HTTPS	443	my IP address

Here is my Port Forwarding

[Happy2Play 9780]

But don't both those default ports go to DSM not Emby?  @FrostByte@cayars

[FrostByte 5392]

DSM is on port 5000

What network ports are used by DSM services? - Synology Knowledge Center

[JulesC 51]

7 minutes ago, Happy2Play said:

But don't both those default ports go to DSM not Emby?  @FrostByte@cayars

Yes, they go to DSM directly. This is where I'm using Synology's Reverse Server and Web Station to redirect and manage Ports.

[JulesC 51]

@Luke @FrostByte @cayars and others

My Emby Server has been running perfectly on my Synology NAS for over a year with the ability to connect from any device via my domain name. However, a couple days ago my family advised my they were unable to connect - received Connection Failure messages.

What I've Tried or Confirmed:

• Removed my custom domain and connecting to my public IP address

• I have checked my Ports that are being forwarded using canyouseeme.org and they are both working.

• The IP address for my NAS has not changed (it's a static IP).

• Confirmed my domain has an A Record entry point at my Emby server

• Firewall has appropriate ports open

• Tried on 3 different remote devices and 1 of them in another state.

Current Set-up:

• Running Emby server version 4.7.8.0 on Synology NAS DS 1520+
• For SSL/HTTPS, I use Let's Encrypt Cert
• Using Synology's Reverse Proxy and their Web Station app to redirect remote access requests from DSM to Emby. 

Please let me know if you need any additional information. Thank you.

[Happy2Play 9780]

With nothing working via domain name that suggest an issue there and not Emby.  Your domain address is unreachable.

I see the certificate is valid but does not resolve to current IP address.

[Happy2Play 9780]

May need to see a server log also.

 

[JulesC 51]

12 minutes ago, Happy2Play said:

May need to see a server log also.

 

Thank you @Happy2Play See attached.

embyserver.txt

[Luke 42077]

2 hours ago, JulesC said:

Service Name	External & Internal Port	Internal IP Address
HTTP	80	my IP address
HTTPS	443	my IP address

Here is my Port Forwarding

Are you sure the internal IP address is correct and hasn't changed?

If your external ssl port is 443 then why were you trying 8920 before?  Do the external port numbers match the corresponding public port numbers in emby server network settings?

[JulesC 51]

@Luke So sorry for all the chaos with this issue.  I checked again and confirmed the IP Address has indeed changed.

All is working now!!! Thank you all for your support and patience. I greatly appreciate it.

[Carlo 4560]

Glad you got it working.  

What I would suggest is making the current IP on your NAS assigned by DHCP a reserved address.

If you reserve that IP for only the NAS it will never change, nor will you have this issue again!

Carlo

[JulesC 51]

PLEASE SEE MESSAGE BELOW

Edited November 4, 2022 by JulesC

[JulesC 51]

17 hours ago, cayars said:

Glad you got it working.  

What I would suggest is making the current IP on your NAS assigned by DHCP a reserved address.

If you reserve that IP for only the NAS it will never change, nor will you have this issue again!

Carlo

Thank you @cayars Yes, I would definitely like to avoid this chaos in the future

I have a static IP assigned to my NAS, so not sure how they got out of sync. What am I missing? Appreciate your help.

[Luke 42077]

4 minutes ago, JulesC said:

Thank you @cayars Yes, I would definitely like to avoid this chaos in the future

I have a static IP assigned to my NAS, so not sure how they got out of sync. What am I missing? Appreciate your help.

It's possible you setup those rules a long time ago prior to setting up the static ip. Hard to say.

[JulesC 51]

@Luke I had a Static IP address for my NAS, but I didn't have a Static IP address for my Router.  I just added a Static IP address to my Router, so now I'll have a Static WAN IP address and hopefully avoid this from happening in the future.  Thanks again for ALL your help.

[Carlo 4560]

5 hours ago, JulesC said:

@Luke I had a Static IP address for my NAS, but I didn't have a Static IP address for my Router.  I just added a Static IP address to my Router, so now I'll have a Static WAN IP address and hopefully avoid this from happening in the future.  Thanks again for ALL your help.

Perfect.

It sounds like they gave you an IP all for you but left you in an IP pool where the router could still pull other IPs.  How you addressed it should have you covered but if something seems weird in the future connection wise, check your WAN IP.

[JulesC 51]

@cayars Thank you