-
Notifications
You must be signed in to change notification settings - Fork 84
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
(missing_token) Missing access token parameter. #128
Comments
This error means that oauthlib doesn't get an access token back from the Tesla server. The body is actually HTML with an access denied error instead of a JSON response. |
yep, I see that. But do you know why it is happening? it seems TLS is old
on server? localhost is working well. Strange
Tim Dorssers ***@***.***> schrieb am So. 21. Mai 2023 um
11:43:
… This error means that oauthlib doesn't get an access token back from the
Tesla server. The body is actually HTML with an access denied error instead
of a JSON response.
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPA4M5URDTIRP2T6A7VUH3XHHPT7ANCNFSM6AAAAAAYJF3NUI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi. I have the same issue. Everything worked fine until today I set up a new virtual environment, in which I installed teslapy with all necessary dependencies. |
I deployed on different servers (debian, ubuntu..) and still no luck. I have TeslaPy==2.7.0 both in my localhost and on server. localhost works fine, but server doesn't. what are we missing here? |
I tried different versions for TeslaPy and also for the dependent packages, no change. |
what we are doing is a pure "man in the middle attack"? :D but then localhost is still working. I suspect, the scope is the issue, maybe? instead of offline_access maybe online_access .. but just a guess |
Lucky for you. Here nothing is working, neither server nor localhost. |
damn it. time for tesla sso auth for third parties. |
I think I may have found a solution that works for me: using the following (older) package versions I can log in again without the "Missing token error" certifi = "2022.9.24" With one or more of these packages the newer (current) versions seem to cause the trouble. |
Aaah thanks man. I will try out tomorrow morning. |
This saved my day. |
Hey @fbphysik thank you so much for the tip ! had the same problem, but it was solved only by downgrading charset-nromalize and requests to the aforementioned versions, I did not have to touch the others if that's important : I"m working in an up-to-date dockerised Domoticz where I had :
If I had a guess that would be to blame a recent requests update (thank you so much for teslapy btw :) ) |
I believe the combination of urllib3 2.0 and Python <3.10 is causing issues. Either upgrade Python to 3.10+ or downgrade urllib3 to 1.26.x. Please let me now if this works for you. |
I'm sorry it will be difficult for me to do more testing, though in my dockerized environment it works properly with python 3.9 and urlib 2.0.4 Python 3.9.2 (default, Feb 28 2021, 17:03:44) Hope that'll help a bit |
hey Tim, thanks for this great library!!!
I am getting this issue below. It works well in my localhost, but on server (Debian) it is failing with this error:
(missing_token) Missing access token parameter.
The text was updated successfully, but these errors were encountered: