Web server working but not accessible

Hi…so this is a weird one, and I suspect the solution is obvious and I'm missing something. After the last update, my Security Spy web server stopped responding at its URL. I use the web server for local access on Apple TV, and it stopped responding without any changes to the network configuration.

However, the URLs from the URL generator are working fine, and my Scrypted instance gets its feed just fine and shares it out via HKSV.

Are these now mutually exclusive, or have I managed to misconfigure something? Preferences shill show sharing via https checked. Thanks!

Comments

  • It's difficult to debug this without specifics, but it's possible that the network address of your Mac changed, breaking the connection to the Apple TV. I would recommend deleting the server instance from the Apple TV and adding it again. Since the URLs from the URL Generator work, it must be that SecuritySpy's web server is up and running, so I hope it will be a simple case of adding the server to the Apple TV app again that will resolve this issue. Also, make sure that you have the the option to "Advertise this web server via Bonjour" turned on in SecuritySpy under Preferences > Web, as this is how the Apple TV app finds your SecuritySpy server.

    If you continue to have problems, please email us and include a debug file (SecuritySpy menu > Debug > Create Debug File On Desktop) and we will check your settings and advise you further.

  • pixelknave
    edited October 2022

    Hi Ben…thanks. I dug into this a little bit more, and it looks like it was a problem with the MacOS Firewall on the Mini running SecuritySpy. Even though SecuritySpy was allowed via "Firewall Options", I could reproduce the problem by toggling the Firewall on (didn't work) and off (worked). I tried removing and re-adding SecuritySpy to the allow list manually, but no dice.

    Coincidentally, the Mini was a version behind on Monterey 12.5…I upgraded to Monterey 12.6 and now everything is behaving as expected.

  • Hi @pixelknave great to hear you found the solution - that's a weird one indeed, we've never come across such problems with the macOS firewall. Sounds like it could be a glitch in macOS 12.5 specifically.