-
Notifications
You must be signed in to change notification settings - Fork 54
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
HTTP Error 403: Forbidden url #27
Comments
I saw the same thing starting yesterday. |
Can you post the output of:
|
Guess what, it has started working again. I've posted output however I'm happy to close this. Might have been an issue with Tesla API rather than teslajson?? root@masterbot:/config# python --version |
I'm glad it's working. Note that I'm no longer supporting Python 2.7. If it works, that's great but I'm not doing any 2.7 fixes going forward. |
My +1 was on Python 3.8.2. For a period yesterday, nothing worked. It also appears to be working again for me. |
Hi, I have this same issue. I never got it to work. Could you help me ? Please Thank you requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://auth.tesla.com/oauth2/v3/authorize?client_id=ownerapi&code_challenge=M2VmZTU1YjYzM2M3NGEyZmEzNDZlODZmYjU0YmJlOThiYWEzNTFiZjMzZTIyZWQ5MDU5N2JhNmIzNjU1ZWU5YQ%3D%3D&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&response_type=code&scope=openid+email+offline_access&state=1a1eq684sx7bfxzp9s0larxr |
I am also seeing the same error:
Is teslajson dead for good or is anyone planning on fixing this? |
Hi,
This was working and I have just started to get 403 errors. Is this happening to anybody else?
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://auth.tesla.com/oauth2/v3/authorize?code_challenge=NDk3YmI5MzZhOWRkNTBiNDA2MDlkYjdkZWI4ZGE1NDY2ODlhMTVmZDczZWVjZjUwYjg4Y2Y0NzVlOTVmYzJiOA%3D%3D&client_id=ownerapi&state=lmim84twliip2m0dm46zl1u7&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&response_type=code&code_challenge_method=S256&scope=openid+email+offline_access
The text was updated successfully, but these errors were encountered: