Jump to content

Search the Community

Showing results for tags 'tcp'.



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

  1. wbiggart

    m3u Channels not playing

    Hello, I have setup an m3u tuner for live tv, but I am unable to play any of the channels. I have attached the ffmpeg logs which show the error. When I attempt to run the ffmpeg command by hand without the "rtsp_transport tcp" flag, it runs just fine. Is there any way to make it so that emby doesn't try and force tcp? Thanks in advance. ffmpeg-log.rtf
  2. I'm unable to connect to the server from other computers on my LAN, only on the local machine (e.g. 127.0.0.1:8096). Some things I've tried: Added rules to Windows Firewall Disabled Windows Firewall (turned it off within Windows Firewall; separately disabled the service) Used other ports There is no other firewall software on the server that I'm aware of. For my sanity, I installed Emby on a Windows 10 machine and it worked flawlessly the first time. Is there anything else I could be missing? Netstat results below: Proto Local Foreign State PID TCP 0.0.0.0:8096 0.0.0.0:0 LISTENING 11944 (Emby) TCP [::]:8096 [::]:0 LISTENING 11944 When I'm connected on the local machine, I also get: TCP [::1]:8096 [::1]:51528 ESTABLISHED 11944 TCP [::1]:51528 [::1]:8096 ESTABLISHED 9304 (Chrome)
  3. Hi Everyone, First off, apologies if this is a bit brash, the forum just lost my last full post about this :/ Anyhow, I've running the beta (3.0.5233.40306), everything has been running smooth until last few weeks when it's saying a port is in use when starting MB server. Funny thing is, if I don't close the error dialog and leave it open, everything works fine (web and accessing via MB classic), so I'm not sure what port isn't working. MB server is a fairly vanilla install with ServerWMC and a couple of other plugins I've been using for ages (Trailers, Trakt, etc.). I've killed every process/service I can (except for VMWare workstation and SVN server services), and it still claims a port is in use. The web GUI says it's using ports 8096 and 8945, both of which are free when I launch it. The only real werid thing I've noticed is that one MB process/service is running when I've closed everything and I can't kill it: MediaBrowser.ServerApplication.exe:9996 UDP Morpheus:ssdp *:* TCPView can't find the process, and I can't terminate the connection (I request the process and connection to close and nothing happens). I've done a reinstall and multiple restarts with no luck. I've attached the MB server log and my TCP View log with everything (VMWare and SVN aside) closed. Anyone have any ideas? log.txt unhandled_4d577e32-3e86-4cb8-8581-fd6ae79d1f77.zip Edit: Forgot to put version number in
×
×
  • Create New...