Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kodi: Suspected SSL/TLS Issue - "Failed to connect" #110975

Closed
jhspyhard opened this issue Feb 19, 2024 · 2 comments
Closed

Kodi: Suspected SSL/TLS Issue - "Failed to connect" #110975

jhspyhard opened this issue Feb 19, 2024 · 2 comments

Comments

@jhspyhard
Copy link

The problem

I am trying to add a Kodi instance to my HomeAssistant (HA) setup, but keep getting a "Failed to Connect" error message.

image

My instance of Kodi is set up for SSL/TLS connections - confirmed working from both the Yatse remote control app, via a browser, and by connecting from the HA machine via openssl s_client -connect media.l33ch.xh:443.

I am able to turn off the Uses an SSL certificate option in the Kodi Integration and successfully connect, once I have disabled SSL in the Kodi.

Kodi's certificate is signed by a private / local-only network Certificate Authority. I had previously added my root certificate to my HA box's Debian ca-certificate store. I am about 95% sure that what is happening is that the Kodi integration connection flow is examining my Kodi certificate using some ca-certificate store other than the root OS's, and is failing the connection when it can't find it.

I turned the logging for homeassistant.components.kodi.config_flow (and globally) up to DEBUG, and managed to get the following line out of HA, but nothing else that was relevant:

2024-02-19 21:23:45.660 DEBUG (MainThread) [homeassistant.components.kodi.config_flow] Connecting to media.l33ch.xh:443 over HTTP

Instructions for adding a custom root certificate to the list that the HA Kodi Integration uses to verify the certificates it encounters would be helpful, to try and rule out this being my issue.

Thanks in advance!

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Kodi

Link to integration documentation on our website

https://www.home-assistant.io/integrations/kodi

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @OnFreund, mind taking a look at this issue as it has been labeled with an integration (kodi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of kodi can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign kodi Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


kodi documentation
kodi source
(message by IssueLinks)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant