Jump to content

Search the Community

Showing results for tags 'forwarding'.



More search options

  • 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 2 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 my tp link router . In Forwarding - i added a virtual server as follows : Service Port - 8096 Internal Port - 8096 IP Address - "Added my In-Home LAN access IP here" (192.xx.xx.x) Protocol - TCP ( options available - TCP ,UDP and All ) Common Service Port - "left blank" ( options available - DNS, FTP, GOPHER, HTTP, NNTP, POP3, PPTP, SMTP, SOCK, TELNET ) 4) I did checked if port 8096 is opened according to https://canyouseeme.org It outputs the below error : Error: I could not see your service on XXX.XX.XX.XX on port (8096) Reason: Connection timed out The IP address showing in canyouseeme.org is also the very same ip showing alongside in wan access in emby dashboard which again is same with my actual external ip ( I don't think issue is with IP mismatch in any way ) PS / This is my first time using any media server at all so i haven't tried WAN access on any different media server ,to be able to tell if it works with some different service . In my laptop ,i am connected to the internet through my home wifi . I haven't up any proxy , vpn or firewall in my machine locally or at router level . In fact just of curiosity - being connected to the very same wifi network in my android device. I tried emby server for android app and started emby server from there but wan access is still not working OS - Arch Linux ( x86_64) Emby Server v4.4.3.0
  2. I just changed the lan port from 8096 to 80 without giving it much tought, found out it does not work on freebsd? any way to change it in a file in order to access the web interface again? Update: when into "/var/db/emby-server/config" and edited "system.xml" and changed the port back to 8096
×
×
  • Create New...