markpainter 9 Posted June 5 Posted June 5 Hi Folks. Been running Emby on my Synology DS220+ nas for a couple of years now without any issues. I have just moved my IP to a new one without a fixed IP address. Since then I have been having all kinds of remote access issues. I have set up a no-Ip account and set that as the DDNS server in the NAS and sometime it works ok. But several of my family members are having problems connecting with EMBY connect - as am I at work. If I add the server manually ie http://*******.ddns.net I immediately get the "Unable to connect right now" message as soon as press enter - it doesn't even try. However on my phone it connects immediately - even though it's using the same wi-fi. Is there a "Do this, Do that" to get it working. Incidentally, I have tried an alternative to Emby on the same NAS (Where I came from to Emby!) and it connects first time every time with their connect software. I REALLY don't want to go back there, but if I can't get this sorted, I may have to
Luke 42708 Posted June 10 Posted June 10 Quote If I add the server manually ie http://*******.ddns.net I immediately get the "Unable to connect right now" message as soon as press enter - it doesn't even try. Hi, what makes you think it doesn't even try?
markpainter 9 Posted June 11 Author Posted June 11 Hi Luke. I think it may be settling down now. However, I still have some odd things happening Using Emby connect it shows my two servers with their local IP, not their remote so clicking on them fails unless I am at home. If I go to add server and put in the details it fails immediately. However, if I then click on the green link that shows the same details in the "fail to connect" message it connects and works perfectly:- As I said, it's probably something I am doing wrong, hence me asking for help! I have checked that the Ports are forwarded in the router as required. It's only since I have a new ISP that this happening. I used to have a fixed IP, but now I use a ddns.net address . Any hints or tips would be appreciated.
Luke 42708 Posted June 11 Posted June 11 Your third screenshot gives you instructions of what to do. Actually it gives you four options. Those are your solutions. Which one would you like to proceed with?
markpainter 9 Posted June 11 Author Posted June 11 Hi Luke Thanks for your reply, and I get that, and yes I can connect that way after typing the info into the top part and it failing. . I just wondered why it show the servers local IP, rather than its remote access IP, and I also why it doesn't connect when I put the info in where it asks. I just thought that I had set something up incorrectly as I assumed it would connect via clicking on my server name, rather than having to type the address in every time I want to watch or listen to anything. But it is working, and thanks for your reply.
markpainter 9 Posted June 12 Author Posted June 12 Ahhh! Now when I go in, it goes directly to my server if I click on it's name remotely. Thanks for your assistance - I think it must have just been teething problems.
markpainter 9 Posted June 14 Author Posted June 14 ** Additional ** After a lot more reading, I now know why the alternative works so much easier on the out of the box experience, by using their relay service. Now I know that, it's definitively only Emby for me! 1
Luke 42708 Posted June 16 Posted June 16 On 6/14/2026 at 5:52 AM, markpainter said: ** Additional ** After a lot more reading, I now know why the alternative works so much easier on the out of the box experience, by using their relay service. Now I know that, it's definitively only Emby for me! Thanks for the feedback !
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now