Jump to content

Search the Community

Showing results for tags 'remote-port-forwarding'.

More search options

  • 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
    • 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 1 result

  1. Hey Emby community. I have diagnosed a problem with my Emby environment, however I can't come up with a swift and elegant solution to it. First, some background: I'm running Emby in a home server which comes with 2 limitations 1. My IP is dynamic 2. I CANNOT open any ports. This is NOT possible with my ISP (I highlighted this in bold to indicate that this really isn't a solution to my problem, I'm looking for a different solution) To mitigate these problems I have a VPS running in the cloud (with a public IP) for a few euros per month, which handles all incoming traffing through remote port forwarding. This is done using SSH tunnels (background on that here if you're interested: https://www.ssh.com/ssh/tunneling/example.) This actually works really well and is quick enough to stream full HD content, the issue however comes when you start chromecasting content. If you use a chromecast, the IP address is passed along to the chromecast, which is a non-accessible IP. Example: My home IP is The Emby VM has IP: assigned to it. The chromecast will now be passed the IP:, which it can't connect to, because the ports on it can't be opened. This also shows in my logs (using a local chromecast): 2019-01-07 16:22:51.255 Info HttpServer: HTTP GET http://192.168.xxx.xxx:8096/emby/Videos/74ba4614749a59664393502333685647/stream.mp4?Static=true&mediaSourceId=74ba4614749a59664393502333685647&deviceId=U0hJRUxE&Tag=4791f2f25d6e3fdbd691f3be6954d613. Host=192.168.xxx.xxx:8096, Connection=keep-alive, Origin=https://mediabrowser.github.io, Accept-Encoding=identity;q=1, *;q=0, User-Agent=Mozilla/5.0 (Linux; Android 8.0; Build/OPR6.170623.010) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.47 Safari/537.36 CrKey/1.36.140076, Range=bytes=0-, chrome-proxy=frfr, Accept=*/*, Accept-Language=en-US, CAST-DEVICE-CAPABILITIES={"bluetooth_supported":true,"display_supported":true,"hi_res_audio_supported":false,"remote_control_input_supported":false,"touch_input_supported":false} Because of this, the chromecast will simply play nothing (and it won't give out any error either for some reason). The solution I want is for me to be able to select either a domain name or another IP address to pass when chromecasting. For example. http://publicdomain.ext:8096 would work. would work How can I achieve this? Thanks in advance.
  • Create New...