Jump to content

Search the Community

Showing results for tags 'centos 8'.

  • 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


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1 result

  1. So, I've taken the plunge. After years of running Emby on Windows, I've decided to create a Linux VM to be a dedicated Emby server. I chose and successfully installed CentOS 8 on my newly minted ESXi host, and got Emby installed using the instructions on the install page https://emby.media/linux-server.html with limited difficulties. A few maddening hours later fighting with Samba and Windows 10 TLS incompatibilities and after finally getting my remote SMB shares mapped to a local mount point with the appropriate permissions in place, I created my first media library. Success! Amazing! Everything working perfectly. Until I switched from my VM to my main PC's browser. Nothing. Nada. Zip. Zilch. The big zero. Situation is this. I've got default Emby port settings, and using FireFox inside the VM, I can connect to Emby server using IP:8096 or localhost:8096. The correct IP address and port shows up on the Emby Dashboard under "In-Home (LAN) access", but none of my other machines (on the same class c subnet, btw) can see the new CentOS Emby server. Using a port scanner, I do not see 8096 as an open port on that machine. The same scanner does see port 8096 open on my Windows Emby server. Now, I know that port is open, at least on the loopback adapter, because Emby is working just fine using a browser on the Emby Server machine, just can't get to it externally. After multiple attempts at changing settings on the Network page and restarting Emby Server with no luck, I started looking at networking. At one reference, I found the command "netstat -na | grep <port>" to find out of there was anything listening on a port, so I tried, and got this: tcp6 0 0 :::8096 :::* LISTEN tcp6 0 0 ::1:41350 ::1:8096 ESTABLISHED tcp6 0 0 ::1:8096 ::1:41350 ESTABLISHED Now, I'm more of an old-school networking guy, but I *think* this means that Emby has set itself up in the OS to listen to IPv6 ports only? maybe? As I said above, the Emby Dashboard shows the correct IP address and port for internal...the correct IPv4 address. I tried using the IPv6 address in my main machine's browser to verify, but was unable to get that to work. Pinging by IPv6 works, so At this point, I'm at an impasse. Not sure how to proceed from here, so any help/pointers/RTFM would be greatly appreciated.
  • Create New...