Jump to content

Cannot connect to Emby Server Remotely


iiiJoe
Go to solution Solved by iiiJoe,

Recommended Posts

@iiiJoe You can delete your attachments. Click your username in the top right and in the menu choose "My Attachments". You can delete them from there any you wish to remove.

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, speechles said:

@iiiJoe You can delete your attachments. Click your username in the top right and in the menu choose "My Attachments". You can delete them from there any you wish to remove.

Ty!!

Link to comment
Share on other sites

10 hours ago, iiiJoe said:

Tried this but getting a similiar result. IMG_1301.thumb.png.7f8d4e61d9f74978b238f4b890c5e332.png

Right I wanted you to provide the server log after doing this:

Quote

Can you temporarily enable debug logging in the logs section, repeat the process with the iOS app, and then try again? Thanks.

Can you please do that? thanks.

Link to comment
Share on other sites

  • 3 weeks later...

Sorry it took so long to get back. I’m now able to log into one of my servers remotely (Desktop-A7L07T6) but I cannot log into the other one (HP). When I choose HP it just redirects me to Desktop. Curiously, HP is showing LAN access while Desktop is showing WAN. Both servers are running on the same home network  

IMG_1496.jpeg

Edited by iiiJoe
Link to comment
Share on other sites

sross44

When you access the nework page of the desktop, what does it show? Block out a small portion of the WAN on that, but if you could share a screenshot of the rest of the page that may help us all in diagnosing why it's showing a different IP address. I'm going to assume it's a different port issue being on the same network as the other server, but I could be wrong on that. 

For example, I have Emby at 8096 and I have a second instance spun up on a different port. Just food for thought since it looks like you're accessing those servers remotely on cellular. 

Link to comment
Share on other sites

2 hours ago, Luke said:

Try doing a new connection by manually entering the server address and see if that helps.

I think part of the issue is that both of my servers have the same WAN address

Link to comment
Share on other sites

3 hours ago, sross44 said:

When you access the nework page of the desktop, what does it show? Block out a small portion of the WAN on that, but if you could share a screenshot of the rest of the page that may help us all in diagnosing why it's showing a different IP address. I'm going to assume it's a different port issue being on the same network as the other server, but I could be wrong on that. 

For example, I have Emby at 8096 and I have a second instance spun up on a different port. Just food for thought since it looks like you're accessing those servers remotely on cellular. 

Yes, both servers are using the same port and WAN address

Link to comment
Share on other sites

seanbuff
2 minutes ago, iiiJoe said:

Yes, both servers are using the same port and WAN address

And that is why you are seeing what you're seeing. If you want both instances to be independent, then you will need to assign them both different ports, and adjust your port forwarding rules accordingly.

Is your intention to run two separate Emby Servers?

Link to comment
Share on other sites

14 minutes ago, seanbuff said:

And that is why you are seeing what you're seeing. If you want both instances to be independent, then you will need to assign them both different ports, and adjust your port forwarding rules accordingly.

Is your intention to run two separate Emby Servers?

I actually have 3 separate servers. So I would like to have access to all 3, if possible. Port forwarding rules would be adjusted on the router, yes?

Link to comment
Share on other sites

seanbuff
13 minutes ago, iiiJoe said:

Port forwarding rules would be adjusted on the router, yes?

Yes, because you'll presumably only have one WAN IP, each server will require a different port so that you can differentiate between them externally.

e.g.

http://<externalIP>:8096 - Server 1
http://<externalIP>:8097 - Server 2
http://<externalIP>:8098 - Server 3

Link to comment
Share on other sites

seanbuff

Alternatively, you can choose to use a reverse proxy (eg. nginx, caddy, etc) to front all your services in a more efficient and secure way.

Plenty of threads here in the community for doing that.

Link to comment
Share on other sites

sross44

Make sure you set each instance of Emby to the right port too. On the network page change the local http port and https (if you have it setup) to whatever you want. Like @seanbuffserver 2 can be 8097 etc. 

Out of curiosity, why do you want 3 servers running? I understand 2, with a beta and a regular server.... but what could you want with 3? You can set user permissions for different foler access on one server etc. 

Link to comment
Share on other sites

1 hour ago, sross44 said:

Make sure you set each instance of Emby to the right port too. On the network page change the local http port and https (if you have it setup) to whatever you want. Like @seanbuffserver 2 can be 8097 etc. 

Out of curiosity, why do you want 3 servers running? I understand 2, with a beta and a regular server.... but what could you want with 3? You can set user permissions for different foler access on one server etc. 

Thank you for the info! I may come back for advice since I've never gotten into changing ports. I use different providers so I like to test which hardware/software and providers are the most reliable.

Link to comment
Share on other sites

sross44
1 hour ago, iiiJoe said:

Thank you for the info! I may come back for advice since I've never gotten into changing ports. I use different providers so I like to test which hardware/software and providers are the most reliable.

It's not that difficult to do and pretty straight forward. If you like to test all of that, knowing how to port forward would definitely help out. 

Link to comment
Share on other sites

  • Solution

Thank you everyone for your help! I got all three of my servers to connect remotely through different ports. I left one server with its original port then changed the other two servers to different ports, set two new port forwarding rules on my router and I’m good to go. Thank you again ☺️

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