Very odd behavior. I noticed in the log after using HS Mobile events like:
May-14 8:01:56 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:30 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:15 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:14 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:02 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:57 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:52 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:47 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:42 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:37 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:17 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:12 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:07 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:02 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:57 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:54 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:44 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:37 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:12 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:07 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:04 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:55 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:51 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:46 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:29 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:24 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:19 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:13 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:08 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:30 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:27 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:05 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:00 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:55 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:50 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:49 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:49 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
xx.xxx.xx.xx is my publice WAN address.
Happens every time I log in. Seems like these events are taxing the server and it is generally slow e.g. log page refreshes and generally cannot login through MyHS due to timeouts. I was successful once. Since myHS is not working I connect direct with DNSname_port which connects to the Zee server on a subnet.
HS Mobile connects every time and very quickly. Trying to connect with same DNSname_port usually results in a timeout. Smartphone and PC/Chrome Browser are on the same LAN.
So...any ideas?
Thanks.
Further update:
When first logging into HS Mobile three login events are logged. If I do nothing with the app, the Log file is quiet.
However, each time I activate a widget (On/Off, click on it to view,...etc) more login entries are created.
HS support says this is not normal and they have not heard of this issue previsouly.
May-14 8:01:56 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:30 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:15 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:14 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:01:02 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:57 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:52 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:47 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:42 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:37 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:32 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:17 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:12 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:07 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 8:00:02 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:57 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:54 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:44 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:37 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:12 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:07 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:59:04 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:55 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:51 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:46 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:29 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:24 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:19 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:13 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:58:08 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:30 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:27 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:05 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:57:00 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:55 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:50 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:49 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
May-14 7:56:49 AM Web Server Web Server authorized login successful from: xx.xxx.xx.xx User: r***a@comcast.net
xx.xxx.xx.xx is my publice WAN address.
Happens every time I log in. Seems like these events are taxing the server and it is generally slow e.g. log page refreshes and generally cannot login through MyHS due to timeouts. I was successful once. Since myHS is not working I connect direct with DNSname_port which connects to the Zee server on a subnet.
HS Mobile connects every time and very quickly. Trying to connect with same DNSname_port usually results in a timeout. Smartphone and PC/Chrome Browser are on the same LAN.
So...any ideas?
Thanks.
Further update:
When first logging into HS Mobile three login events are logged. If I do nothing with the app, the Log file is quiet.
However, each time I activate a widget (On/Off, click on it to view,...etc) more login entries are created.
HS support says this is not normal and they have not heard of this issue previsouly.
Comment