punchsuckr
Senior Member
Something is hanging up https or keeping it too busy to respond. I use curl for the check, and the (28) is the curl return code which is a timeout. Just speculating, but do you have a lot of syslog activity going on (do you have packet logging on for example)?
As long as it doesn't repeat one right after one another, it means its breaking whatever it is free by restarting https.
Nope the syslog is at its default level, nothing changed. If i have ssl disabled then i don't get any errors (your fix is working well on the beta and I dont have to add the router ip to the specified IP addr list).
Update: Yep 24 hours and no errors with ssl disabled.
Last edited: