Online Status Issue

[vmsman]

Awesome work on this new project and thanks for all your hard work. I have observed that the online "status" indicator in the lower right of an app icon does not always correctly indicate the status of a self hosted application. If the service is hosted through a reverse proxy behind NginX Proxy Manager (NPM), lab-dash is monitoring the status of NPM rather than the status of the hosted service. In addition, it seems to be necessary to refresh the lab-dash web page to see any change in the online/offline status or the clock widget.

[AnthonyGress]

Hmm I will have to look into this more. I may have to tweak the health check to resolve the IP from the services Alias before checking the status.

As far as the clock not refreshing, I'm not sure what that would be. I haven't heard of anyone else having that issue so there might be something in your specific setup causing that issue but I'm not sure what that would be. The clock basically just updates the time every 1 minute. I will take a deeper look tonight and see what could be causing that.

[vmsman]

After a closer look, I can report that the clock does update on a 2 minute interval on my Brave Browser. Services hosted behind NPM momentarily have a gray status icon and then they return to green. Services not using NPM correctly show read & green, but only after a refresh of the browser tab.

[AnthonyGress]

The current interval for health checks is once every 15 minutes, can you see if they update after 15 minutes?

I think I have an idea of why the NPM services are not displaying correctly so I will get an issue created for that.

[geekmoto13]

I think this might be related to issue #15

[vmsman]

@AnthonyGress The clock seems to update on an interval which I thought was 2 minutes. After watching the behavior for an hour, I am not sure. It seems that switching tabs in the browser and switching back after a minute or so triggers an update. Interesting.

[AnthonyGress]

@AnthonyGress The clock seems to update on an interval which I thought was 2 minutes. After watching the behavior for an hour, I am not sure. It seems that switching tabs in the browser and switching back after a minute or so triggers an update. Interesting.

That might be related to a power saving feature in the browser where it hibernates inactive tabs

[AnthonyGress]

This should be fixed in v1.1.5 @vmsman

Let me know if you are still experiencing this issue