Jump to content

Search the Community

Showing results for tags 'WAN'.

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

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 11 results

  1. As the title implies , the Remote (WAN) access doesnt work for me .After some searches , i found this article and followed everything mentioned in there - https://support.emby.media/support/solutions/articles/44001849007-connectivity . 1) Firstly the In-Home ( LAN ) access is working fine , no issues there 2) I made sure that the ip address showing up in WAN access is indeed the correct one . wget -qO- ifconfig.me/ip This when ran inside terminal does returns the same ip mentioned in WAN Access so thats fine as far as i can tell. 3) Lastly i did setup port forwarding on m
  2. I have had my server running perfectly for about 3 months now, able to connect anywhere in the world and from any device via my domain name emby.XXXX.com on port 8096. However, today I went to connect remotely and was met with Connection Failure messages from all devices. I checked my network settings and the Dashboard shows that everything is still looking correct on the server side. What I've tried: Removing my custom domain, and connecting directly to my public IP address Changing the port # Checking to make sure the po
  3. Asaki

    WAN inaccessible

    Bonjour, je rencontre un problème suite à l'installation de emby server sur mon Raspberry Pi 4 (4GB). Emby est inaccessible en dehors du réseau local (inaccessible en WAN, je ne peu donc pas y accéder depuis un appareil non connecter sur le réseaux local). J'ai installé cette version de emby server : Ubuntu Armv7 (armhf) - BETA Download emby-server-deb_4.5.0.6_armhf.deb dpkg -i emby-server-deb_4.5.0.6_armhf.deb Open a web browser to http://localhost:8096 Puis cette version pensant que c'était surement dû à la beta : Ubuntu Armv7 (armhf) Download emby-server-deb_4.4.2.0_armhf
  4. ShadowKindjal

    Emby WAN URL

    I seem to be having issues accessing my server from the internet in certain situations. Currently, my SSL connections is handled by a reverse proxy, apache. This URL is (for example) https://emby.server.com/ but the URL listed on my dashboard is listed as https://emby.server.com:8920/. When connecting to my server with the reverse proxy URL I never have any issues establishing a connection but the URL posted in the dashboard seems to go down randomly. This is an issue because users connecting to my server with emby connect accounts are usually trying to access the server via dashboard URL. My
  5. Hi, i just created my server today, got emby installed and it just wont work when putting the ip address in my browser (Mobile) while connected to mobile data. Internal works fine. I have tried unblocking ports on my Asus Router and TalkTalk modem +the ports on the server 2012 firewall but still no connections (I also tried with a friend and he couldn't get in either. Is there something i am missing?
  6. Hi, I've set up my Emby-server with "HTTPS using reverse proxy" using the "Setting up SSL for Emby (WIP)" guide. My question is: How can I switch between my LAN IP-address 192.168.1.20:8096 if I'm at home and my https: // emby.domainname.com:443 address if I'm on the road (using the Android-app)? Manually adding the other address for the same server doesn't seem to work? Thanks!
  7. There is wrong local network address in the Dashboard, the local address is the the same as the public ip-address. I've attached a screenshot. I would like to have an option to explicitly specify network interfaces to whom Emby should bind. As well as ability to completely disable binding to unnecessary interfaces.
  8. studio-jurdan

    https, wan and....

    hello, i'm sory but i realy can't acces to emby server outside my home, the wiki and help are not up to date so they are talking about option i can't find in this distro (the last) why HTTS first? it make ssl alert to all the browsers that is no cool for my guest ??? why another port for internet that the one for intranet? if i try to connect with emby account, sometime i can see my server inb the "list" BUT it ca'nt connect. i had open the wan port in windows seven firewall AND in my router firewall i also made a DMZ zone for the server internal IP on my router i also tryed w
  9. I'm on version 3.0.5557.20000 and am having a problem streaming movies through EMBY connect. When i try to stream a movie i get an error: As soon as that error pops up this is outputted to the log file: 2015-04-04 13:15:44.9904 Error - NotFoundHttpHandler: 10.26.9.3:8096 Request not found: /Items/9183b1456a4fd9dc78eb45b1f1049a4f/PlaybackInfo?UserId=e4fafe12771947c5e7923375b97685f4&StartTimeTicks=0 I'm able to stream from within the LAN and from WAN using my WAN IP, It just doesn't seem to work through EMBY connect. Any ideas? server-63563702400.txt
  10. jxd132

    Chromecast over WAN

    Hi everyone, I'm setting up MB to be accessible over the WAN, and it works well for everything except Chromecast. Everything functions on the LAN, both from Android clients and casting to Chromecast. In MB Server, I use UPnP to open the ports, and the router shows 8096 and 8945 forwarded properly. The Android client connects and plays video from remote locations, so this seems to confirm the ports are open. But, when I am remote and try casting to a Chromecast, the video does not play. The app triggers the Chromecast to start the receiver app, which shows the MB logo on the TV. Hitti
  11. Port forwarding; an overview This is an overview not an in depth discussion of IPv4 networking The basic’s IP addresses have to be unique on a network if they are duplicated then data may not be delivered to its intended recipient. You could think of this like a postman delivering mail on your street, if there are two houses numbered 12 then which does he deliver mail addressed for number 12 too, probably the first number 12 they get to. Needing a unique IP address causes a problem. Due to the way IPv4 works there are simply not enough of these addresses available for every one
×
×
  • Create New...