Jump to content

Remote Access Stopped working


RyeDog
 Share

Recommended Posts

ok so i want to give as much info as i can here. i have been using emby for years and i love it. a week or 2 ago all remote access (with the exception of my cell phone) stopped working. in home still works fine. i have gone through all kinds of guides and tried asking on facebook and i have had no luck. a did a factory reset on my router and reconfigured it for both TCP and UDP port forwarding on 8096 and 8920. i  have firewall exceptions for those ports as well and for emby. i have a vpn but its set up with emby on a split tunnel and i have tried remote access with the VPN entirely disabled and still didn't work. on canyouseemeorg, my 8096 post is found, but my 8920 is not.  i have tried with automatic port mapping on and with it off. i have also tried it with with uPnP enabled and disabled. i'm at a loss and pretty frustrated with the whole thing, especially since it has worked fine in the past. any help would be greatly appreciated.

Link to comment
Share on other sites

Hello RyeDog,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:


Thank you.

Emby Team

Link to comment
Share on other sites

3 minutes ago, RyeDog said:

but my 8920 is not

Hi.  If you are trying to access via https, then that would be why that doesn't work.  So, the first step would be to figure out why that port forwarding is not working (at a network level).

@cayars

Link to comment
Share on other sites

7 minutes ago, ebr said:

Hi.  If you are trying to access via https, then that would be why that doesn't work.  So, the first step would be to figure out why that port forwarding is not working (at a network level).

@cayars

any suggestions on where to start?

Link to comment
Share on other sites

Q-Droid

Did you have https setup before? Is the cert still valid or expired? If you weren't using https (8920) before then focus on the http setup to troubleshoot.

 

Link to comment
Share on other sites

1 hour ago, Q-Droid said:

Did you have https setup before? Is the cert still valid or expired? If you weren't using https (8920) before then focus on the http setup to troubleshoot.

 

i don't believe i had https set up before. i just don't know what else to try at this point

Link to comment
Share on other sites

Q-Droid

Port 8920 will not show up if you haven't setup https, so it can be ignored.

If canyouseeme does detect port 8096 for the "Remote (WAN) access" URL in your Emby dashboard then it sounds like it's working or at least responding. It's possible your WAN IP changed so make sure the remote users have the correct one if you're not using DDNS. If using DDNS make sure it matches your WAN IP.

The fact that your phone works on the mobile network is a good indication that Emby is setup and working. The mobile apps are using the connection info provided by the server, the same info that's on the dashboard.

 

Link to comment
Share on other sites

4 hours ago, Q-Droid said:

Port 8920 will not show up if you haven't setup https, so it can be ignored.

If canyouseeme does detect port 8096 for the "Remote (WAN) access" URL in your Emby dashboard then it sounds like it's working or at least responding. It's possible your WAN IP changed so make sure the remote users have the correct one if you're not using DDNS. If using DDNS make sure it matches your WAN IP.

The fact that your phone works on the mobile network is a good indication that Emby is setup and working. The mobile apps are using the connection info provided by the server, the same info that's on the dashboard.

 

my phone had been, but as of 2 days ago, it only workings when I'm on wifi at home. when its on mobile, it doesn't

Link to comment
Share on other sites

Q-Droid

In that case provide the info requested in the second post of this thread.

 

Link to comment
Share on other sites

RyeDog, do you have a domain setup with an entry such as emby.domain.com pointed to your WAN IP?
Next you would need a valid cert for the specific DNS entry your using ie emby.domain.com (or a wildcard cert for your domain)

In Emby Server's network settings you would enter the name being used ie emby.domain.com in External domain:
Enter the path to your cert.pfx file in Custom ssl certificate path:
Make sure the user running Emby Server has read access to the path and file.
Make the same user the owner of the file as well.
Type the exact same secret password used to create the cert.pfx file in the field Certificate password: in network menu.
Set the option Secure connection mode: to Required for all remote connections

If you're not already using port 443 on your network:
Set Public https port number: to 443
Verify Local https port number: has the value 8920 set

Login to your router:
Turn off UPnP
Reset your router
Log back into your router and go to port forwarding.
Take a screen shot of your current settings in case you need them.

Assuming Emby is the only thing you need open remove all entries from port forwarding and save.
Now create one entry for inbound port/WAN on port 443 using TCP (no UDP) redirected to port 8920 port of the IP of your Emby Server. It should look similar to:
image.png

Save or Apply changes, reboot your router, now login and verify the port forwarding is just as you left it.

Go back to Emby Server and scroll to the bottom of the network page, click the save button.

Restart Emby Server using your preferred method.

Now try opening https://emby.domain.com (your URL as shown on dashboard) by clicking on it. If it works you should be good.  If not try it from your phone turning wifi off  using your mobile carrier's network.

Obvious things to check.  Does your domain emby.domain.com have the correct IP of your WAN port?
Does "ping emby.domain.com" show the correct address?

If you need help or just want a new set of eyes to look over your settings, feel free to private message me for help and I can remote in and give you a hand.

Carlo

Link to comment
Share on other sites

turpentine

i had a similar problem one day.

for a sick system reason they were an autorization issue to access the .p12 TLS certificate, i reset the

https emby port stopped working due to file permissions bugs

i advice you to install wireshark in order to capture incoming traffic, to see if you get a tcp syn on that https port, i you are still on ipv4 (with no CGNAT).

 

since i got ipv6 SLAAC, no port forwarding no NAT on home routers anymore, only direct firewall rules

 

 

Edited by turpentine
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
 Share

×
×
  • Create New...