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
https not working after 1.4.0 update #53
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful. |
If it helps i am also getting the error below for https requests after migrating to 1.4.0 Secure Connection Failed |
Confirmed: LOG: https://www.pastiebin.com/5e19a23f26b49 |
Same here; thought I did something wrong. Is there any way to roll back to the last version? |
here too 2020-01-16 12:58:56 - WARNING :: MainThread : The pyOpenSSL module is missing. Install this module to enable HTTPS. HTTPS will be disabled. |
Same issue on trying to open Tautulli running via Hassio on an RPi 4 |
At least once a day I go to my hass.io page hoping to see that update icon on Tautulli... and then the sadness grips me... : ( (Just kidding and being dramatic. But it would be nice to see this bug fixed soon!) |
Is more information needed? Is there something we need to provide on our end to move closer to closing this issue? Just wondering and volunteering if there is anything I can do. |
Unless you can upgrade the app to Python 3.0, at this time nope Edit - maybe it should have been sad face 😢 |
Paul, can you clarify? What changed between this and the last version? Tautulli? openSSL? I'm naive in the ways of Docker containers and add ons. |
From the investigation I did, I believe it is likely this: Which looks like it is a Python 3 version of the library, the 2 library is no longer available for Alpine 3.11. Considering Python 2 is no longer supported these issues would likely only increase. I could be wrong (its a likely possibility 😉 ), but I do think supporting Python 2 apps should really be a no go at this point in time. |
Thanks, that really helped me to understand it better. Looking at Tautulli's repo it looks like a PR was put in for Py3 support but closed without comment so I guess Tautulli, at least as an Add On for HA is dead. Bummer. |
Could maybe build this addon on this instead: Yes its a fork and it will probably not be migrated but still, its python3 atleast and would solve alot. How do you guys manage today? Not that its not working properly..
|
Since I can still access Tautulli locally without SSL, I built a bunch of sensors using the REST api and calling it locally with http. REST doesn't care if it's SSL or not so it works.
My resources look like this:
Then I used templates to build sensors out the attributes I was interested in and made cards for them using Thomas Loven's template-entity-row and styled them using card-mod. Yeah, it was the long way round, but I learned a lot in the process and I like the way the cards look so in the meantime this is working well for me. |
Fixed in dev. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Problem/Motivation
After latest upgrade to 1.4.0, https connection stopped to work. Http is working ok, bit since I'm accessing my hassio using https, I lost access to tautulli via iframe panel
Expected behavior
Access via https should work as previously configured
Actual behavior
I'm getting error in the browser:
ERR_SSL_PROTOCOL_ERROR
Also error in add-on log:
2020-01-09 22:45:24 - WARNING :: MainThread : The pyOpenSSL module is missing. Install this module to enable HTTPS. HTTPS will be disabled.
Also, inside add-on in Settings section, https is not checked. After turning it on and restarting it is still unchecked.
Steps to reproduce
Try to access add-on via https
My config didn't change:
"username": "my username",
"password": "my password",
"ssl": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"log_level": "info"
}
The text was updated successfully, but these errors were encountered: