Wrong color status of siteMonitor/ping

[dukobpa3]

Description

I have two services (marked on picture)
First one have response more than second.
Second one event not accessible (http status undefined NaN ms)
But both of them have green mark.
Not so important with text view but with statusStyle: dot green color hides real situation.

First one (with long ping) shows red even with 500ms if I'm using http, but green even with 1,500ms https

homepage version

0.8.10

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

..

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

It seems like you are experiencing an issue with the status indicators for your services not accurately reflecting their actual status when using the statusStyle: dot configuration. This could be a bug or a misconfiguration in the way the status is being determined and displayed.

To help you further, I would need to know the exact configuration you are using for these services in your services.yaml file. Specifically, how you have set up the ping or siteMonitor properties for these services, as well as the statusStyle setting.

In the meantime, you can try the following steps to troubleshoot the issue:

1. Ensure that your services.yaml configuration is correct and that the ping or siteMonitor properties are set up properly for each service.
2. Check the documentation for any updates or changes in the statusStyle configuration that might affect how statuses are displayed.
3. Review the release notes for version 0.8.10 to see if there are any known issues or changes related to service status indicators.
4. If you are comfortable with it, you can also check the browser's developer console for any errors or warnings that might provide more insight into the issue.

If after these steps the issue persists, please provide the relevant sections of your services.yaml configuration, and any additional information from your troubleshooting that could help identify the problem.

This comment was generated by Glime.

[dukobpa3]

I think configuration works well, the issue is just with wrong color codes for different statuses.

• HTTP status NaN definitely not accessible so it should be red.
• I'm not sure about long pings, because site works but it is slow. But in other hand in case I'll make siteMonitor with http://.... definition instead of https://... same request times marks as red.

[shamoon]

Perhaps this has something to do with the status codes the server is responding with, it would be helpful to have an actual URL to test, can you provide that?

[spadazz]

The first, third and fourth button are using :

• different href: to call an api
• THE SAME siteMonitor: to check if the host is active or not.
  After this, if it's still not clear, I give up.

[shamoon]

Oh, now I get what youre doing. Can you post the actual config? Wondering if thats the issue.

Theres not really a reason it should be different as long as the homepage API is returning the same result. So theres still a miscommunication in the other direction, which is that you havent posted the homepage API results for anything other than the Nas one. For example, if you've set things up correctly e.g. 'Wake' will call siteMonitor?group=Power&service=Wake (not Nas), thats what I'd be curious to see if its different.

For example:

- Testing:
     - Example 1:
          href: http://localhost?dosomething
          siteMonitor: https://404doesntexist.org
     - Example 2:
          href: http://localhost?dosomethingelse
          siteMonitor: https://404doesntexist.org
     - Example 3:
          href: http://localhost?dosomethingelse2
          siteMonitor: https://404doesntexist.org
     - Example 4:
          href: http://localhost
          siteMonitor: https://google.com

yields:

And you can see the distinct network calls:

[spadazz]

Thank you, I'll get back to you as soon as possible..I think tomorrow.
I just add that the first href: is calling the NAS webui
The third and fourth href: are calling a go api that executes commands via ssh on the host (Nas).
Clicking the button the api works as expected.
It's just the status reported by siteMonitor that do not work.

[spadazz]

So, this is a sample config of the service Nas that we saw earlier :

    - Nas:
        icon: mdi-nas
        href: https://nas.<domain>
        description: Nas
        siteMonitor: https://nas.<domain>
    - Wake:
        icon: cloudflare-pages
        href: http://192.168.178.220:8089/wolweb/wake/NAS
        description: Nas
        siteMonitor: http://192.168.178.220:8089/wolweb
    - Reboot:
        icon: mdi-restart-#f4a520
        href: http://192.168.178.220:9000/api/host/..something..
        siteMonitor: http://192.168.178.10:8080
        description: Nas
    - Poweroff:
        icon: mdi-power-plug-off-#f4a520
        href: http://192.168.178.220:9000/api/host/..something..
        siteMonitor: http://192.168.178.10:8080
        description: Nas

the siteMonitor in https//nas. and http://192.168.178.10 are equivalent, the first is just proxied to get ssl certificate.

Disabling all these sitemonitors and the re-enabling the one at a time, works up to 3 sitemonitors, showing a red status for a powered off host.
From 4+ all the statuses are always green.

Since I have 3 equal sitemonitors per-service, and there are now 3 services in the group...it's too much.
Notice that in the other 2 services there are equivalent "sub-groups" that are also called Wake, Reboot, Poweroff
I tried to keep the titles clean for "easy readability", but maybe this is a naming problem for the the sitemonitor.

I validated the entire yaml and it seems fine.

[shamoon]

A "service" is each item in that list, Nas, Wake, Reboot, Poweroff. Each are 1 service, so you have 4 service blocks and 3 different site monitors.

Again, you have only ever posted the results for siteMonitor: https://nas.<domain>, not for siteMonitor: http://192.168.178.220:8089/wolweb or siteMonitor: http://192.168.178.10:8080. Names shouldn't matter here.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.