dseguin 0 Posted February 3, 2022 Posted February 3, 2022 Hi all, I have been a happy camper with Emby for the past weeks. I've previously resolved with your help a secure connection to Emby (HTTPS Remote access to Emby using Chromecast). Helas, the secure remote connection is now broken... I'd like to start off by saying that nothing has changed on the Synology NAS server. Its primary functions are backing up computers in my home and streaming with Emby. Issue : Accessing the Emby server remotely using HTTPS (port 8920) now results in a "Sorry, cannot access this page - IP xxx.xxx.xxx.xxx has refused the connection" when using a web browser and a "Connection Failure" message when using the mobile application. There is no issue accessing remotely when using the public HTTP port. It is only when the Secure Connection Mode of Emby is set to: "Required for all remote connections" that it fails (this was perfectly working before). What has been done so far : Rebooted NAS server and router Verified forward secure port 8920 on router Verified that Synology NAS server can be accessed remotely through SSL connection (it uses a different port than Emby but NAS can me managed remotely via HTTPS) Verified that the certificate was still valid (Let's Encrypt certificate converted to PKS12 on sslfofree website) Reexported/Reconverted new PKS12 certificate with password Upgraded Emby server to 4.7.0.22 beta Verified that port 8920 can be accessed remotely by using the http://www.canyouseeme.org/ site Domain name my_nas_server.synology.me can be resolved to the correct IP address when pinged Tried using the IP address instead of the domain name on Emby server What have I missed ? Thanks !
seanbuff 1316 Posted February 3, 2022 Posted February 3, 2022 6 hours ago, dseguin said: Verified that the certificate was still valid (Let's Encrypt certificate converted to PKS12 on sslfofree website) Reexported/Reconverted new PKS12 certificate with password Just a thought, but when did you do this? As I believe Let's Encrypt just revoked a bunch of certs a little over a week ago (28th Jan 2022) -- you may have received an email about it. Also you'll want to supply an Emby Server log covering the connection issues. https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/
Bert 49 Posted February 4, 2022 Posted February 4, 2022 Not sure if this is helpful or not but I had a similar issue. Turned out ATT updated the firmware on the modem/router which I had intentionally crippled to just a modem (there technically is no bridged mode). Spent hours trying to figure it out before I realized I had to reconfigure their equipment.
Carlo 4561 Posted February 5, 2022 Posted February 5, 2022 (edited) On 2/3/2022 at 11:21 AM, dseguin said: What have I missed ? Hi, we haven't heard back from you. Did you get this figured out or do you still have an issue? If not send me a private message with a link to this thread and the URL or your Emby Server. I can try to see if I can get to your login page which will narrow things down quite a bit. If needed, we can setup a remote support session and I can login with you on your desktop and we can look at several things together. Carlo Edited February 5, 2022 by cayars
dseguin 0 Posted February 5, 2022 Author Posted February 5, 2022 Hi Carlo, The issue is still there. I've tried renewing the certificate, exported and converted with the same result. I've also upgraded the firmware on my router, no cigar. The new thing now, is that port 8920 is showing as an error on Canyouseeme.org. I'm starting to suspect my ISP. I'll contact them and see if I can make progress. I'll take you up on your offer if the problem persists. I'll also update this thread accordingly. Thanks !
dseguin 0 Posted February 6, 2022 Author Posted February 6, 2022 Me again. The issue has been resolved. It was the router all along. What I did : deleted the redirection port to 8920, rebooted the router, added the 8920 redirection port, it did not work, rebooted the router again and it now operates properly. Must have been a corrupted redirection table on the router. I now know where to look for if something like this happens to me again (at least with the current router). Thank you all for your input !
Luke 42078 Posted February 7, 2022 Posted February 7, 2022 16 hours ago, dseguin said: Me again. The issue has been resolved. It was the router all along. What I did : deleted the redirection port to 8920, rebooted the router, added the 8920 redirection port, it did not work, rebooted the router again and it now operates properly. Must have been a corrupted redirection table on the router. I now know where to look for if something like this happens to me again (at least with the current router). Thank you all for your input ! Thanks for the feedback !
Carlo 4561 Posted February 7, 2022 Posted February 7, 2022 On 2/6/2022 at 9:46 AM, dseguin said: Thank you all for your input ! One thing you might want to check on is to make sure the internal IP of your server doesn't change. The best way to accomplish this is using a DHCP reservation. The process is different on every router but all are similar. Either you select the host from a drop down or you enter the MAC address of the Server and then assign an IP you want it to always receive. Without doing that it's quite possible the server picked up a different IP address and of course port forwarding is now going to the "wrong place".
dseguin 0 Posted February 7, 2022 Author Posted February 7, 2022 Hi Carlo, The server internal IP is already static. Thanks for your input !
Carlo 4561 Posted February 8, 2022 Posted February 8, 2022 That good to know. Guess the router just needed a reboot.
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