Closed oscarpp1984 closed 1 month ago
Thanks for reporting.
1.24.1
You are using an outdated version of TeslaMate and do encounter a DNS issue on your host. Please update TeslaMate and restart your host for correct DNS resolving for all Docker containers.
Thanks for reporting.
1.24.1
You are using an outdated version of TeslaMate and do encounter a DNS issue on your host. Please update TeslaMate and restart your host for correct DNS resolving for all Docker containers.
Hello, THX for relpying. I am using the latest version 1.30.1, the version of Postgres 15. And I have tried many app applied for the token(mac, Windows), but still encounter the login problem.
If you have DNS issues you can try as many tokens as you wish, none will succeed
Where ever you are hosting TeslaMate is blocking the call to Tesla servers in China. This is not a TeslaMate issue.
Where ever you are hosting TeslaMate is blocking the call to Tesla servers in China. This is not a TeslaMate issue.
Problem solved. The token is generate from server which out of China. So can't login from a Chinese IP. Set a proxy to owner-api.vn.cloud.tesla.cn. The token can access successful.
Is there an existing issue for this?
What happened?
When restore the database after reinstall the teslamate, can't login teslamate via token. The teslamate webpage shows "Invalid token",but I can sure the token is correct. Is there some login restrictions in China? The teslamate log shows connection refused.
Expected Behavior
No response
Steps To Reproduce
1.Restore the database 2.Login Teslamate via Token
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.24.1