Emby server on synology ds923+ Unable to reach server

[GFellows 2]

Hi I set up an Emby server on my Synology ds923+ NAS a few days ago and shared it with a friend over remote connection. It worked fine without issue for over a day, but as of yesterday he can't connect to it from the LG TV app with the error "unable to reach server"

I tested with the android app version on my mobile network and had the exact same problem of "unable to reach network"

The local network works fine on my LG TV, as does the web interface on my PC.

I tried to problem solve it but couldnt find a solution, hoping someone here can help me. Was going to buy Emby premiere but if its not working seems kinda pointless to buy the upgrade.

[Neminem 1518]

Check you router, and see if has changed your WAN ip address.

If thats the case try with your new address.

Also check Open Port Check Tool -- Verify Port Forwarding on Your Router (canyouseeme.org)

Other wise check Connectivity

[GFellows 2]

My WAN IP address is unchanged.

I went to canyouseeme.org on my PC thats on the same network as my NAS and tried to test port 8096 but I get the message Error: I could not see your service on XX.XX.XXX.XX on port (8096)
Reason: Connection timed out

If I have to set up port forwarding on my router why did it work flawlessly for almost 2 days before this started?

[GFellows 2]

to add to that every port I checked had the same error message.

Is it possible my routers built in firewall has blocked the ports automatically because of the traffic on that port?

[Neminem 1518]

Check you routers port forwarding.

[GFellows 2]

Yeah I'm setting it up now, will report back if it works. Thanks for the help

[GFellows 2]

Yeah its all working thanks 

Dunno why it worked at first though and then suddenly stopped

Edited June 27, 2024 by GFellows

[Neminem 1518]

It might be a fluke.

But check your nas has a static ip address.

And is reserved in you router.

[GFellows 2]

ok will do thanks

[Luke 42077]

Hi, has this helped?

[GFellows 2]

Yeah my problem is fixed, was a port forwarding issue

Edited June 29, 2024 by GFellows