Jump to content

Search the Community

Showing results for tags 'gluetun'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • 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
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. Hey, I'm back again, was trying out Emby in August and ran out of time. I am now been running Emby since October 6 and having good success with on disk TV shows, Movies, and Live TV via m3u and XMLTvlisting and will buy a lifetime pass shortly, but am having trouble introducing a HDHomeRun - figured that was easier than using TVHeadend and my USB tuners. Environ: Raspberry 4B/8. Debian 64 bit. All up to date, Docker/docker-compose. I tried adding a working HDHomerun with a reserved IP to Emby. The auto-detect didn't work, but I wasn't surprised as Emby is not on the lan subnet, but behind docker and gluetun. But when I tried providing the IP address it just errored on trying to add. I figure it is the gluetun network stack. Gluetun knows what is local to the LAN and what should go out the VPN, but needs to be told of ports being used by dependant containers. I listed 8096 and 8920 for Emby, and that works fine.. Occasionally a Firestick Emby app gets confused and can't see the server after a Firestick restart, but a retry fixes that. I think I read that Emby is using udp to communicate with HDHomeRuns. I believe I would need to list the UDP port numbers in gluetun's configuration and rely on gluetun to deliver incoming dup back to the Emby container. I tried adding ports: - 65001:65001/udp to gluetun, but still no joy. Who can help a guy out? Docker Compose environ. Running Emby using gluetun's network providing me with a VPN tunnel through Nord. docker-compose.yml version: '2.0' services: // other containers snipped // qbittorrent, radarr, sonarr, jackett, apcupsd gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=nordvpn - VPN_TYPE=openvpn # or wireguard - OPENVPN_USER=<<secret>> - OPENVPN_PASSWORD=<<secret>> - SERVER_COUNTRIES=Canada ports: - 8096:8096 - 8920:8920 emby: #image: emby/embyserver:beta image: emby/embyserver_arm64v8 container_name: emby #network_mode: host network_mode: "service:gluetun" environment: - PUID=1000 - PGID=1000 - TZ=America/Toronto volumes: - /mnt/emby:/config - /mnt/television:/data/tvshows - /mnt/movies:/data/movies # - /opt/vc/lib:/opt/vc/lib #ports: # - 8096:8096 # - 8920:8920 restart: unless-stopped
×
×
  • Create New...