is a valid cert req for widgets?

[tomasenskede]

Description

I am new to homepage but it looks awesome... I am struggling with the widgets to get live data into homepage... some works fine some don’t... the once not working are running https without valid cert... is this req. by homepage to get it working?

homepage version

v0.8.11 (4239e8f, Apr 8, 2024)

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! ❤️

---

To address the issue with widgets not working due to running HTTPS without a valid certificate, homepage does not strictly require a valid SSL certificate for widgets to function. However, if the widgets are accessed via HTTPS and the certificate is not valid, this can cause errors due to the browser's security policies or the backend service's refusal to connect to an insecure endpoint.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Ignore SSL Certificate Errors: If you are using curl for testing the API endpoints, you can bypass the certificate check by using the -k or --insecure option. This is not recommended for production but can be useful for testing purposes. For example:

   curl -k https://SERVICEIPORHOST/path/to/api
   

2. Add a Valid SSL Certificate: Consider using a valid SSL certificate for your services. You can obtain a free certificate from providers like Let's Encrypt.

3. Use HTTP Instead of HTTPS: If securing the connection is not a concern (for example, if all services are within a private network), you could configure your services to use HTTP instead of HTTPS.

4. Check for Mixed Content: If your homepage is served over HTTPS, but the widgets are trying to load data from HTTP sources, browsers will block these requests due to mixed content policies. Ensure that all external requests are made over HTTPS.

5. Browser Console: Check the browser error console for any security-related messages or errors that could indicate problems with the SSL certificate.

6. Homepage Configuration: Ensure that the widget URLs in your services.yaml configuration file do not end with a trailing slash or other API path unless otherwise noted, as this can result in an error.

7. Container Networking: Verify that the homepage container can reach the services over the network. You can test this by executing a ping from within the Docker container to the service's IP address or domain.

8. Logs: Check the homepage logs for any error messages that might indicate connection issues or SSL certificate problems.

If you continue to experience issues, you may want to consider reaching out for support using the Homepage AI Bot, GitHub discussions, or the Discord support channel as mentioned in the troubleshooting documentation.

Remember to replace SERVICEIPORHOST and /path/to/api with the actual IP address or hostname and API path of the service you are trying to connect to.

This comment was generated by Glime.

[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.