Search the Community

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?