Jump to content

Search the Community

Showing results for tags 'vpn tunnel'.

  • 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 3 results

  1. Buongiorno a tutti! Ho un problema con il mio serer emby. Ho attuamente due connettività (casa e casa vacanze) accoppiate tra loro con due Fritz Box (accoppiamento lan tramite vpn) La situazione è la seguente, lan 1 (connettività principale)192.168.1.x lan 2 192.168.2.x con il server emby posizionato su 192.168.1.xx Se dall'esterno mi collego in vpn alla connettività principale (dove si trova fisiamnete la macchina su cui è installato emby) riseco ad aprire senza problemi l'app (in quanto il disositivo connesso in vpn risulta avere un insirizzo 192.168.1.x se però provo a spostarmi nella connettività accoppiata alla lan principale l'app non siesce a connettersi, da browser invece anche sotto la connettività secondaria (192.168.2.x) mi basta digitare l'ip del server emby (192.168.1.x) e riesco a visualizzatre tutto tranquillamente. Sapete per caso quale può essere il problema? Grazie a tutti i nanticipo.
  2. Since I installed Wireguard on my raspberry pi4, where I have emby server runnin, I got the logs flooded with: 2021-09-15 00:01:03.504 Error App: Error sending socket message from to *** Error Report *** Version: Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb Operating system: Linux version 5.10.60-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #144 Framework: .NET Core 3.1.13 OS/Process: arm/arm Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/lib/emby Application path: /opt/emby-server/system System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (0xFFFFFFFF): Bad value for ai_flags at Rssdp.SsdpCommunicationsServer.SendFromSocket(Tuple`3 socketTuple, Memory`1 messageData, IPEndPoint destination, CancellationToken cancellationToken) Source: System.Private.CoreLib TargetSite: Void Throw() 2021-09-15 00:01:03.712 Error App: Error sending socket message from to *** Error Report *** Version: Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb Emby seems to be working fine so maybe it is not a real problem but I would like to hear if any suggestion on how to avoid this. Thanks
  3. VincentVanGozer

    DLNA via Server across IP subnets

    Hi all! Apologies if this has been answered, which means my search skills suck... I'm wondering if I can use the play-to feature to specify a DLNA device on another IP subnet? Basically, I've got my emby server (latest version for windows) on a subnet. I have a VPN tunnel set up to my sister's house, with everything on a subnet there. Is there a way in the web GUI or config files to manually add an option to play-to a DLNA device at a fixed IP address in that other subnet? The intended end result is that she can http log into the mediabrowser server with her login, select the play-to device of her TV, and have it stream that way. MBserver ( <-> Gateway <-> <-> DLNA device Thanks for any tips, tricks, advice, and knowledge!
  • Create New...