Jump to content

Search the Community

Showing results for tags 'ddns'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 6 results

  1. After viewing the other thread for setting Emby server via IIS with auto renewed SSL Cert, I've decided to share my personal approach (no IIS) for non-advanced users: I kept the default Windows Installation of Emby. I setup a local scheduled job to back up the configuration files for Emby Server, so if I need to reinstall Emby one day, all configuration files are available from separate machine. I chose not to use IIS as I don't want to have the hard dependency between Emby Server with the Windows machine. I run the Emby server as it is, so the port 8096 and 8920 remain the same as its default setting. I do use the Port Forwarding feature on my router to expose the Emby server port 8920 (HTTPS) and/or 8096 (HTTP) to public. To be a bit more secured, you may choose to expose only the HTTPS port 8920 to public. You might want to ensure the firewall does not block these ports. I registered a free account on noip.com, as it offers me free DDNS hostname + a free SSL Certificate. I applied this free SSL Cert, downloaded the certificate file to the windows machine, and configured directly on my Emby server configuration page to use the corresponding SSL cert file with password. From the public to access my home Emby Server, the url will just be my free DDNS url + the port I chose to expose. It is a valid public URL with valid SSL Certificate. With such configuration pattern, the only risk is within the Windows Machine. If it is for any reason broken, all I have to do is: Install Emby Server for Windows, restore the configuration files from backup, copy SSL cert to the Emby server hosting machine Configure Router port forwarding from the Windows Machine IP, make sure the Windows machine firewall does not block the ports you want to expose Pros vs Cons: It has less dependency on the Windows Machine itself, and swapping to a new Windows machine would be easy as well. No configuration required for IIS and its required components. Emby comes with its web layer hosting, so for personal users it is a bit of overkill to setup another IIS layer. noip.com offers free tier users the DDNS service with a free SSL Certificate, so why not take the advantage of that. Of course, we might not get the "SSL auto renewal" part, but for an Emby home user/personal user, how much value we are saving by setting up the SSL auto renewal? You need to have certain knowledge of how to apply for the SSL cert on noip.com website. https://www.noip.com/support/knowledgebase/configure-trustcor-standard-dv-ssl/
  2. I wanted to share a PowerShell script with everyone. This can be ran as a scheduled task on a Windows box, and will update your DNS entry in Cloudflare via API. This is much better then paying for a DDNS service, and you can use your own domain. Make sure you have already purchased a domain and have your domain's DNS setup in Cloudflare. Step 1: Create a path on your hard drive for this script. For this example I'm going to use C:\Scripts. Copy the script to this path and open it with your favorite editor. I use Notepad++. Step 2: Create you Cloudflare API token https://developers.cloudflare.com/api/tokens/create To create an API for your script login to your Cloudflare account at https://dash.cloudflare.com/login. Then go to User Profile/API Tokens https://dash.cloudflare.com/profile/api-tokens. From the API Token dashboard select 'Create Token' You will want to use the 'Edit zone DNS' template or select 'Create Custom Token' Here you will want to allow Zone Read access and Zone DNS Edit rights. It will then take you to a summary page, select 'Create Token' You will now have the generated API Secret. Copy API Token into the script Copy your Zone ID Go back to the main home page of your Cloudflare dashboard and select your domain Scroll down and towards the bottom right you will find the API section. You want to copy the Zone ID Add which record you want to change. I typically update my main domain I have for emby and then all my other records are CNAME that point back to the same IP. Note: Make sure you are proxying your traffic to mask your actual IP. Step 3: Create a task in task scheduler Open task scheduler on windows. I typically create an Automation folder to keep my tasks separate from Windows and Applications. Once you have your Automation folder, select that folder and 'Create Task'. Name the task anything you like. I chose to name mine 'Cloudflare DNS Update'. Also change the user to run as 'System'. Go to the next tab and create a new 'Trigger'. I choose to run mine hourly. You now want to create an 'Action'. You want to 'Start a program'. The program is 'powershell.exe'. For the argument you want '-File "C:\Scripts\updateCloudflareDNS.ps1" That is it, the task will now execute the script to check your external IP and update your DNS record for you. Issues and updates will be logged wherever this script is. So for this example it would be in C:\Scripts\updateCloudflareDNS.log. updateCloudflareDNS.ps1
  3. sometimes i can access the ddns,but sometimes i can't.(The same setting) I turned off upnp, but turned on port forwarding.(Tried local http and network http port forwarding) I tested that the port prompt is closed,But the same settings qb and tr can be used normally How can i solve the problem? I did not use ssl certificate,And The ddns I use is DYNU Maybe this is related to multiple dialing?
  4. Ok this is going to be a long post. In this thread I will show you 2 different ways in which I setup a HTTPS connection to my emby server. Both ways require a certificate which again I will show you how i got mine using Lets Encrypt on Windows. I will break the posts up into Sections. Part.1 - Setting up a DDNS (Dynamic DNS host) Only require if you ISP IP is dynamic i.e. changes. Part.1.A - Setting Up DDNS using your own Domain Name Part.2 - Getting a Domain Name (Optional but looks fancier) Part.3 - Getting a SSL Cert from Lets Encrypt the easy way. Part 3a - Using LE.exe to get Certificates (recommended) Part.4 - Setting up HTTPS by changing default port to 443 Part.5 - Setting up HTTPS using reverse proxy
  5. Since about three days ago I have not been able to connect to my remote access. I have been remotely accessing my content through a DDNS from DuckDNS but it has stopped working. Has anything changed on Emby's side that I may now need to reconfigure. I've contacted DuckDNS and they say everything is fine on their side so I'm checking with other users to see if this problem is unique or a known issue.
  6. dchaosblade

    Remote Access issue

    So, earlier this week I went through and set up my mediabrowser server to be accessible from outside of my LAN. I opened up the appropriate port, registered a host name with www.noip.com, and everything seemed to work fine. I was able to connect to my server remotely from my phone, and from my computer at work. My brother was also able to connect without issue. My parents however, are having a problem... If in their web browser, they type in http://[ip]:8096/mediabrowser then everything works fine. Problem is that the IP I have is dynamic, thus the use of the noip hostname. If they use the hostname provided via noip though they get connection error (website could not be found). Attempting to ping the server ended in failure as well (unable to resolve host name). The issue occurs in both Safari and Chrome, on two different macs (running OSX) and an Android phone. It appears to me that the issue has something to do not with their computer or my server, but rather their router or something (it's blocking the connection due to noip's ddns redirect). Has anyone had this issue before and/or know how to solve it? I looked into their router configuration and didn't see any settings that looked like they might prevent the connection but it's the only thing that makes sense to me. If necessary, they can connect using the IP Address, but it's likely to cause issues eventually when the IP gets renewed (I'm not sure how long the lease time is for an IP from Comcast, which is the ISP for both me and my parents).
  • Create New...