Certificate error on update check
Hello!
I just updated to version v1.20.0 (from 0.15), and now I'm getting a certificate issue basically on every page load, when doing the update check it seems:
It complains about:
This certificate it must be getting through my HAProxy, which is my loadbalancer, and ssl-offloader in front of my kubernetes cluster. Especially because the domain named in the error, is not the domain homarr is being hosted on. But why is it using this certificate to connect to api.github.com? Did I miss some configuration somewhere?
My setup is like:
Internet > HAProxy > Kubernetes nginx ingress controller > pod
Does anyone have an idea? I haven't really found a similar issue yet.
Solution:Jump to solution
Nvm I found the issue, because I added a domain to my router (opnsense), it propagated that domain, as search domain towards all my machines/vms and so to my pods as well, so it was trying to connect to api.github.com.mydomain.com :catfacepalm:
8 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
It seems like your Pod does not trust github.com, which is weird, because it should be on the general trust list
Yeah indeed, but it's also strange that it's using the certificate from the other domain I own, but not the one that homarr is hosted on.
It is behind a reverse proxy outside of kubernetes, is there a setting I'm missing?
No, Homarr has no settings for certificates. We only have a possibility to upload trusted certificates which are added to the generally trusted ones
Hmm alright, strange then that it behaves like this. Maybe some proxy settings missing?
Solution
Nvm I found the issue, because I added a domain to my router (opnsense), it propagated that domain, as search domain towards all my machines/vms and so to my pods as well, so it was trying to connect to api.github.com.mydomain.com :catfacepalm:
@Meierschlumpf thanks for thinking along anyway!
Bruh, xD
Great that you were able to find the issue 😄