Jump to content

Search the Community

Showing results for tags 'port security'.

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

  1. cyphershadow

    TCPWrapper out of no where.

    Afternoon all, I have an unusual issue that just surfaced in the last couple days. Everything on my server was working fine, but all of a sudden this morning the Emby HTTPS port is showing as being tcpwrapped, and is blocking all connection attempts. This is occurring on the internal network, and only for the Emby service. No other services on the underlying QNAP are being affected. No changes to the underlying QNAP TS-451 unit were made, and no changes to the Emby server were made within the last two weeks. The problem persists only on the Emby HTTPS port, and the issue moves to any new HTTPS port that is designated, and persists full reboots of the server and the QNAP. I even rolled the QNAP firmware back to the prior release that was confirmed working, and the issue is persisting. This leads me to believe it may be an issue within the Emby server itself. Were any form of Access Control or tcpwrapping features recently integrated on the back end, and if so is there a way to whitelist? I see in the server logs over the HTTP interface that Dlna, StudioImages, and Port Mapper were updated over the last couple of days, but the problem has remained even after rooming these plugins. So I'm scratching my head here. Any thoughts?
×
×
  • Create New...