Announcement

Collapse
No announcement yet.

HS3 Https Server stops responding (http is ok)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HS3 Https Server stops responding (http is ok)

    Hi,
    Running HS3 3.0.0.548 for a while now. I have got the ssl server enabled on the Labs setup pageusing port 443 and when I start up HS3 it all works fine, both locally and from outside my LAN.

    However, after some variable amount of time (from a few hours to a few days), the https server stops responding and I can't access the HS3 GUI using https/port 443. When this happens I can still access the GUI using http/port 80.

    There's nothing I can find in the logs - is there any way to diagnose this and is it a known issue (given that it's a labs feature)?

    Thanks,

    Jon.


    #2
    You could try turning on Homeseer's debug for web/email activity.

    From an immediate script command:

    &hs.DebugMode = 512

    Set it back to 0 when finished.

    You will find the log file in a new folder called \Debug Logs

    Any reason why you cannot use a VPN?
    Jon

    Comment


      #3
      Hi Jon,

      Thanks for the tip, but I've not been able to catch anything ueful in the logs. It's almost as if something upstream blocks traffic, but for the fact that a restart of HS brings the HTTPS server back.

      I am guessing now that all attention will be on HS4, so I don't expect there's much mileage in raising it with HST. I don't think I am quite ready to take on the migration to HS4 at home yet, so I think I'll look at a weekly or nightly restart for now.

      I don't use a VPN just because I'm not perhaps as bothered as I should be about security into HS3 (pretty much everything else is blocked), but thought if the option was there I should use it and it doesn't feel quite right to have to run a VPN just to access a web site at home...

      Cheers,

      Jon.




      Comment


        #4
        I have this exact issue in HS3. I never could figure it out and just worked around it, mostly, by scheduling a nightly reboot. Now that I have migrated to HS4 I was hopeful the issue would be resolved, but no luck.

        Was a solution for this ever identified?

        Thanks,
        Drew

        Comment

        Working...
        X