Jump to content

Emby suddenly stopped working.


Go to solution Solved by Apotropaic,

Recommended Posts

Zenith Media
Posted

It's an eero Max 7, they refer to it as a modem/router. Along with it, I have a deco mesh system. 

Zenith Media
Posted

Okay, actively trying the process now. 

Posted
7 minutes ago, Zenith Media said:

Along with it, I have a deco mesh system.

Why?  The Eero is also a mesh system.

Zenith Media
Posted

I already had the deco system when I upgraded the internet to ont, it came with eero. We have a lot of devices. It works. I tried the steps. On the deco, I made it an Access Point and enabled Smart DHCP. On the eero interface, I port forwarded the deco with 32700-32700, previously I had 8096-8096. As of now, it does not work remotely, still.

sa2000
Posted (edited)
1 hour ago, Zenith Media said:

On the deco, I made it an Access Point and enabled Smart DHCP. On the eero interface, I port forwarded the deco with 32700-32700, previously I had 8096-8096

the 32700 to 32700 in the support article example was for the case when they were both routers and on the 2nd router you forward 32700 to 8096

You said you made the deco access point - so the network and DHCP is now served by the eero, If you want to use 32700 as the public port, on the eero you forward 32700 to 8096 for the the emby server local IP address - because the deco is now just an extension to the existing eero network

Does the eero port forward allow you to have a different public port from the local port i.e. 32700 to 8096 or does it only allow the same port number? if it has to be the same, then you should go back to forwarding 8096 to 8096 on the eero to the local IP of the emby server - assuming you are keeping the deco operating as an Access Point

 

 

Edited by sa2000
Zenith Media
Posted

Okay, I adjusted the port forwarding through the eero, 8096-32700. 

sa2000
Posted (edited)
18 minutes ago, Zenith Media said:

the eero, 8096-32700. 

So the Emby Server has a local IP address provided by the eero. 

It is DHCP Reserved or static

You have a manual port forward in the eero for Public/WAN/External Port 32700 to forward to Private/LAN/Local tcp port 8096

In Emby Server Settings - Network, you have Public http port number set to 32700 

The default Local Http port number is kept as default as 8096

Update: and you have disabled "Enable automatic port mapping" ?

correct?

Edited by sa2000
Zenith Media
Posted

Reserved.

In the eero app, under IP Reservation, Port Forwarding 8096-32700 (Enabled).

In Emby Server Network settings, no, the public http port number by default is showing 8096 in the first row and on the second row it is showing the Public https port number 8920. Do I change both of these to 32700?

For the local inside of emby Network settings, the first row Local http port number, 8096. The second row Local https port number, 8920

sa2000
Posted (edited)
16 minutes ago, Zenith Media said:
16 minutes ago, Zenith Media said:

Port Forwarding 8096-32700

 

I am concerned this might be a port range 8096 to 32700

Do you have a screen in the eero app like the one below?s

 

If you do, then 

it needs to be:

Name: Emby

Port or Port Range: 32700

Use a different port or port range for the internal port: enabled

Internal Port or Port Range: 8096

Protocol: TCP ticked

and saved

Then in Emby Server Network Settings you keep

Local http port as 8096 and you set

Public Http port as 32700 and you have

"Enable automatic port mapping" unticked

and Save

I am assuming you have "Secure Connections Mode" as "Disabled"

If your eero app screen is different, let me have a screenshot

 

 

eero.png

Edited by sa2000
Zenith Media
Posted

I adjusted it to this...

eero.jpg

sa2000
Posted

that is good. you don't need to have udp for this - so sufficient for TCP to be ticked

Lets check the server network settings - for ports and automatic mapping and secure connections

 

sa2000
Posted

great - only one thing to change:  

Public http port number - change from 8096 to 32700 and save

 

sa2000
Posted

If you can get me a screenshot of the eero app with tcp only ticked and not with udp, i will use it as an example in the documentation

Zenith Media
Posted

Okay. So the second Public row, keep it 8920?

sa2000
Posted
1 minute ago, Zenith Media said:

Public row, keep it 8920?

That is for https / secure connections and it is disabled - so no need to touch it

Zenith Media
Posted

eero 2.jpg

  • Thanks 1
sa2000
Posted

Once you change the http port in network settings, on the emby server settings dashboard, you should see your local IP address with port 8096 and your public ip address with port 32700

Running on http port 8096

Home (LAN) access: http://LOCAL-IP-ADDRESS:8096

Remote (WAN) access: http://PUBLIC-IP-ADDRESS:32700

 

Zenith Media
Posted

Correct.

It is still not connecting remotely. 

Not sure how much you have read prior. My pc is hard wired to a deco satellite. The main deco is connected to my eero in a different room. I adjusted the settings within deco as recommended yesterday. 

sa2000
Posted
2 minutes ago, Zenith Media said:

Not sure how much you have read prior. My pc is hard wired to a deco satellite. The main deco is connected to my eero in a different room.

What is the local IP address of the emby server?

Is it within the IP LAN subnet on the eero? Does the eeor app have a ping tool where you can ping that IP to see it gets through 

Does the eero need rebooting after setting up a port forward ?

 

 

Zenith Media
Posted

Yes to the first two.

Question, for the deco(s) connected to the eero and my pc, should port forward them?

sa2000
Posted
7 minutes ago, Zenith Media said:

Question, for the deco(s) connected to the eero and my pc, should port forward them?

The decos should now be acting in passive mode as "Access Point" and all the network management for IP addresses should be by the eero.

On the Deco app, when you click on Advanced settings, does it show operation mode as "Access Point" ?

You could click on Reboot Deco in Settings / System - if the mode is correctly set to Access Point

You could show them individually and reboot - starting with the main deco and then once that is operational, the satellite decos rebooted

 

 

Zenith Media
Posted

Yes, the deco in the app is showing as Access Point still.

 

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
×
×
  • Create New...