Jump to content

Emby Blog

  • entries
    568
  • comments
    4968
  • views
    3485781

Contributors to this blog

  • Luke 353
  • ebr 70
  • Carlo 31
  • sross44 16
  • 7illusions 15
  • ScottIsAFool 12
  • Abobader 11
  • radeon 8
  • xnappo 8
  • darwindeeds 7
  • Redshirt 6
  • Cheesegeezer 5
  • leedavies 3
  • Aphid 3
  • bigjohn 3
  • snazy2000 3
  • softworkz 3
  • techywarrior 3
  • Soultaker 2
  • chef 2
  • gcw07 2
  • marcelveldt 1
  • hurricanehrndz 1

How to guide: Emby connect, remote access and basic port forwarding


EMBY HOW TO BLOGS

We will be releasing a variety of how to blogs over the next few weeks during the holidays. A lot of people will be home and have some time to "tinker" with their home servers and these little entries will be a great starting point to working more closely with your server. For more in depth knowledge that these blogs do not cover, or any questions that may pop up, please reach out to any of the staff members on the forums in the appropriate channels and we will be glad to assist you. 

What Is Emby Connect?

Emby Connect is a cloud-based service that simplifies remote access by linking your Emby account to your home server. Instead of manually entering your server's IP address, Emby Connect lets you log in using your Emby account and automatically connects you to your server. This allows for a easy interface to share with your family members who may not even know what an IP address is!

It is important to note, though, that Emby Connect is entirely optional.  It is not required for remote access as  you can always use the address of your server and the local credentials you setup.


Setting Up Emby Connect

Here’s how to configure Emby Connect for seamless remote access:

1. Link Your Emby Server to Your Account

  • Log in to your Emby Server: Open your browser and navigate to the Emby Server dashboard (e.g., http://localhost:8096).
  • Go to the Users section: On the sidebar, select Users.
  • Link to Emby Connect: Find your user account and click the More button (three dots). Then, choose Connect to Emby Connect.
  • Sign in to Emby Connect: Enter your Emby Connect account credentials. If you don’t have an account, create one at emby.media/connect.

2. Enable Remote Access

  • Navigate to Settings: From the sidebar, select Settings > Network.
  • Verify Remote Access: Ensure the box labeled Allow remote connections to this Emby Server is checked.
  • Test your connection: Use a device outside your home network to log into your Emby account via the Emby app or web interface. Your library should appear automatically if configured correctly.

Tip: Emby Connect still requires port forwarding or UPnP, as discussed next.


Setting Up Manual Port Forwarding

If Emby Connect doesn’t meet your needs or you prefer direct control, you can manually configure port forwarding on your home router. This ensures your server is accessible from outside your local network.

What Is Port Forwarding?

Port forwarding allows specific incoming traffic (ie, requests to your Emby Server) to bypass your router’s firewall and reach your server directly. It’s a secure and efficient way to enable remote connections.


How to Set Up Port Forwarding

Step 1: Access Your Router Settings

  • Find your router’s IP address. Commonly, it’s 192.168.1.1 or 192.168.0.1. You can confirm this by typing ipconfig (Windows) or ifconfig (macOS/Linux) into the command line.
  • Open a web browser and enter the IP address to log into your router.
  • Log in using your router’s username and password (check the router’s manual or sticker if you’re unsure).

Step 2: Set Up Port Forwarding

  • Locate the Port Forwarding section: It may be under labels like NAT, Virtual Server, or Advanced Settings.
  • Create a new rule:

    Service Name: Enter a descriptive name like "Emby Server."

    Internal IP Address: Enter the local IP address of your Emby Server (find this in Emby > Settings > Network > LAN IP).

    Internal Port: Use 8096 for HTTP or 8920 for HTTPS (if you have SSL configured).

    External Port: Match this to the internal port (8096 or 8920).

    Protocol: Choose TCP or TCP/UDP.

  • Save the rule: Apply the changes and restart your router if necessary.

Step 3: Test Remote Access

  • Open a browser and enter your external IP address and port (e.g., http://<Your_External_IP>:8096).
  • If configured correctly, you’ll see your Emby login page.

Best Practices for Security

While remote access is convenient, it’s important to secure your Emby Server:

  • Use a strong password for your Emby account.
  • Enable HTTPS: Configure an SSL certificate to encrypt your traffic (via Let's Encrypt or another provider). There are a lot of posts on the forums on how to set this up and a lot of different options in which to do so. 
  • Restrict access: Use the IP whitelist/blacklist feature in Emby’s Network settings to limit who can connect.

Common Issues and Troubleshooting

  • Can’t access the server remotely?

    Verify the external IP address matches your public IP (use whatismyip.com).

    Check for typos in your port forwarding rule.

    Confirm your firewall isn’t blocking the connection.

  • Dynamic IP issues?

    If your ISP frequently changes your public IP, consider setting up Dynamic DNS (DDNS) to link a domain name (e.g., emby.myserver.net) to your IP.


Conclusion

Setting up remote connections in Emby is straightforward with options like Emby Connect and manual port forwarding. Whether you prefer the simplicity of Emby Connect or the control of direct address access, you can enjoy your media library wherever you go.

Happy streaming!

  • Like 6

13 Comments


Recommended Comments

bobaldis

Posted

Hi,

Great idea these how to guides and strangely enough the 1st one on Emby Connect is relevant to me as I'm not sure what I'm doing wrong but it never seems to work as it should for me or my users.

Basically I Login to Emby connect get presented with Add Server or Login into Emby Connect (screenshot attached), which just takes me back to the previous login page.image.thumb.png.13d92b9166145bb1acf409cc4e1862b9.png

I've followed the guide and all settings appear as they should be and I can get remote access to my server if I use my external URL, but just do not understand why Emby Connect is not working.

Any guidance appreciated.

Luke

Posted

@bobaldisit sounds like you did not link the user on your server with Emby Connect by following this guide:

Emby Connect

  • Like 1
bobaldis

Posted

5 hours ago, Luke said:

@bobaldisit sounds like you did not link the user on your server with Emby Connect by following this guide:

Emby Connect

Weirdly all my users were, but my account wasn't, I've enabled (but I'm sure it was before) and will test again tomorrow, but I still don't believe it behaves as it should and will try and document my experience to see if perhaps there is something up with my settings.

In the meantime, one thing that seems strange is that even though I've logged into Emby Connect, I still see the "Sign in with Emby Connect" button, which if pressed takes me back to the login page, surely if I'm logged in already this shouldn't be presented to me?
image.png.70eb5466ff45e28bcd37143ac2c0c84e.png

bobaldis

Posted

22 hours ago, bobaldis said:

Weirdly all my users were, but my account wasn't, I've enabled (but I'm sure it was before) and will test again tomorrow, but I still don't believe it behaves as it should and will try and document my experience to see if perhaps there is something up with my settings.

In the meantime, one thing that seems strange is that even though I've logged into Emby Connect, I still see the "Sign in with Emby Connect" button, which if pressed takes me back to the login page, surely if I'm logged in already this shouldn't be presented to me?
image.png.70eb5466ff45e28bcd37143ac2c0c84e.png

So this is the process and my experience:
1) Start sign in image.thumb.png.d4b4725837dd67c2d99e068a9c28c028.png

2) Sign inimage.thumb.png.bd06d078b54f0d3dca80ae271ad7291e.png

3) Signed in options

I believe I've successfully signed in to Emby Connect as presented with "Last used" Server, but as per my previous question, if logged in why is there still a "Sign in with Emby Connect" button?image.thumb.png.82bc2e57f2f75a17a3ec4dc537384272.png

4) Try to login by pressing the "Last used" buttonimage.thumb.png.25f62c10e3a8f28e9361ff7122267973.png

5) Sign in successfully by clicking on either of the links (when at home, or just the WAN link when remote) so server available on the configured URLSimage.thumb.png.c571e9c1e09477719a9d728b430edbbe.png

I'm currently on Version 4.9.0.34 beta running on Synology NAS , but this has been my experience with Emby Connect as far back as I can remember and so hasn't ever felt right?

Any suggestions welcome?

AncyAndal

Posted

This is actually the best guide ive seen for port forwarding its really easy to follow. However is hasnt helped me, for the last 4 days ive been struggling only to find out my ISP was using CGNAT. Once i found that out they gave me a dynamic IP, and i started setting up a DDNS with no-ip. I am still in limbo as to what i should be doing i feel like i played around with to many things and something is blocking my port forwarding preventing my friends and family from accessing the server. Any advice?  here is a summary of things ive been trying and looking at. 
 

Network and Hardware Setup

  • Router: D-Link  (configured with port forwarding).
  • Server: Unraid server hosting Docker containers, including:

     

    • binhex-emby: Emby media server (port 8096).
    • binhex-jackett: Jackett (ive only just have it there i havent configed it yet not running)
    • binhex-qbittorrentvpn: qBittorrent with VPN support.
    • firefox: Docker container running Firefox for browser-based access.
    • GluetunVPN: VPN container for secure connections. (not running yet was looking at it)
    • NoIp: No-IP Dynamic Update Client (DDNS updates,).
    • DDNS Provider: No-IP, .
  • IP Configuration: Dynamic IP (192.168.X.X) reserved via router DHCP.

Steps Taken to Resolve Issues

  • ENABLED DHCP Server:

    Set rule for DHCP on the server.

  • Port Forwarding and DDNS:

    Port 8096 mapped to the Emby server at 192.168.X.X.

    Verified No-IP Docker updates the correct public IP.

  • Local and Remote Access:

    Emby is accessible locally over the LAN.

    Remote access fails.

    Port-checking tools (e.g., CanYouSeeMe) report "Connection timed out" for port 8096.

Unresolved Issues

  • Remote Access to Emby: Connection fails despite correct setup.
  • Port Accessibility: External port checks indicate port 8096 is not open.

    Anything at all I would be greatful, I am even happy to start again from the begining but I wouldnt even know where to start or how to resest things back to default. Thank you for your time and even if you dont help thats okay hopefully my little post here can people trouble shoot somethings they might not of thought of like ISP CGNAT
     

 

sross44

Posted

On 12/28/2024 at 11:27 PM, AncyAndal said:

This is actually the best guide ive seen for port forwarding its really easy to follow. However is hasnt helped me, for the last 4 days ive been struggling only to find out my ISP was using CGNAT. Once i found that out they gave me a dynamic IP, and i started setting up a DDNS with no-ip. I am still in limbo as to what i should be doing i feel like i played around with to many things and something is blocking my port forwarding preventing my friends and family from accessing the server. Any advice?  here is a summary of things ive been trying and looking at. 
 

Network and Hardware Setup

  • Router: D-Link  (configured with port forwarding).
  • Server: Unraid server hosting Docker containers, including:

     

    • binhex-emby: Emby media server (port 8096).
    • binhex-jackett: Jackett (ive only just have it there i havent configed it yet not running)
    • binhex-qbittorrentvpn: qBittorrent with VPN support.
    • firefox: Docker container running Firefox for browser-based access.
    • GluetunVPN: VPN container for secure connections. (not running yet was looking at it)
    • NoIp: No-IP Dynamic Update Client (DDNS updates,).
    • DDNS Provider: No-IP, .
  • IP Configuration: Dynamic IP (192.168.X.X) reserved via router DHCP.

Steps Taken to Resolve Issues

  • ENABLED DHCP Server:

    Set rule for DHCP on the server.

  • Port Forwarding and DDNS:

    Port 8096 mapped to the Emby server at 192.168.X.X.

    Verified No-IP Docker updates the correct public IP.

  • Local and Remote Access:

    Emby is accessible locally over the LAN.

    Remote access fails.

    Port-checking tools (e.g., CanYouSeeMe) report "Connection timed out" for port 8096.

Unresolved Issues

  • Remote Access to Emby: Connection fails despite correct setup.
  • Port Accessibility: External port checks indicate port 8096 is not open.

    Anything at all I would be greatful, I am even happy to start again from the begining but I wouldnt even know where to start or how to resest things back to default. Thank you for your time and even if you dont help thats okay hopefully my little post here can people trouble shoot somethings they might not of thought of like ISP CGNAT
     

 

Sorry I didn't see this. Did you make any progress? Have you tried setting up something like Nginix Proxy Manager for a reverse proxy? I find a lot of times that's an easy route to take and you don't have to open up a lot of ports either. 

AncyAndal

Posted

@sross44I kinda have, I ended up just getting a domain and set up a clareflare tunnel. I'll be moving again next year and when i do ill either keep paying for it or making sure i get a server friendly ISP

bobaldis

Posted

On 25/12/2024 at 17:42, Luke said:

@bobaldisit sounds like you did not link the user on your server with Emby Connect by following this guide:

Emby Connect

Hi Luke,

Did you see my follow up posts?

Luke

Posted

On 12/26/2024 at 6:25 PM, bobaldis said:

So this is the process and my experience:
1) Start sign in image.thumb.png.d4b4725837dd67c2d99e068a9c28c028.png

2) Sign inimage.thumb.png.bd06d078b54f0d3dca80ae271ad7291e.png

3) Signed in options

I believe I've successfully signed in to Emby Connect as presented with "Last used" Server, but as per my previous question, if logged in why is there still a "Sign in with Emby Connect" button?image.thumb.png.82bc2e57f2f75a17a3ec4dc537384272.png

4) Try to login by pressing the "Last used" buttonimage.thumb.png.25f62c10e3a8f28e9361ff7122267973.png

5) Sign in successfully by clicking on either of the links (when at home, or just the WAN link when remote) so server available on the configured URLSimage.thumb.png.c571e9c1e09477719a9d728b430edbbe.png

I'm currently on Version 4.9.0.34 beta running on Synology NAS , but this has been my experience with Emby Connect as far back as I can remember and so hasn't ever felt right?

Any suggestions welcome?

Hi, the suggestions are given to you in the form of those four bullet points.  Your "fix" is to choose one of them. Which of them are you going to do?

bobaldis

Posted (edited)

On 03/01/2025 at 23:17, Luke said:

Hi, the suggestions are given to you in the form of those four bullet points.  Your "fix" is to choose one of them. Which of them are you going to do?

Hi @Luke,

Apologies, but I do not understand your response, I've provided my full login experience using Emby Connect with comments, it would be good if you could confirm whether my assumptions in the comments are correct or am I missing something?


If you are referring to the the 4 bullet points in my screenshot, as they work OK when I click on them, why does Emby Connect fail to connect stating "Unable to Reach Server" surely it uses these same URLs, this happens every time not just occasionally?

I'm not complaining or anything only trying to work out why it doesn't work for me or my users, perhaps I have something misconfigured, but as far as I can tell it is as per the guide?

Thanks Bob

Edited by bobaldis
seanbuff

Posted

24 minutes ago, bobaldis said:

why does Emby Connect fail to connect stating "Unable to Reach Server" surely it uses these same URLs, this happens every time not just occasionally?

Hi Bob, so the assumption is that your browser is forcing you to a https login, and you have not setup TLS for your server so it is failing. Is this correct? 

If there is no HTTPS configured on your server, you could try disabling your browser from redirecting you using the steps outlined here: https://emby.media/community/index.php?/topic/123079-unable-to-connect-via-emby-connect/#comment-1296417

 

 

  • Thanks 1
bobaldis

Posted

55 minutes ago, seanbuff said:

Hi Bob, so the assumption is that your browser is forcing you to a https login, and you have not setup TLS for your server so it is failing. Is this correct? 

If there is no HTTPS configured on your server, you could try disabling your browser from redirecting you using the steps outlined here: https://emby.media/community/index.php?/topic/123079-unable-to-connect-via-emby-connect/#comment-1296417

 

 

Thanks, just off to bed but will try this in the morning.

bobaldis

Posted

14 hours ago, bobaldis said:

Thanks, just off to bed but will try this in the morning.

Perfect, now works as described and as I always thought it should, I allowed "Insecure Content" on "https://emby.media/", so this now opens "http://app.emby.media/#!/home" as below without any intervention.

Thanks @seanbuff:)

image.thumb.png.44f3bd0c7a9d031a87f176e2b1b7ddf5.png

@LukePerhaps a link on this page to a brief guide on the HTTPS fix as I didn't really understand the issue until reading the other thread ?

image.thumb.png.25f62c10e3a8f28e9361ff7122267973.png

  • Like 1
  • Thanks 1

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...