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

API: non-existing domain (auth.tesla.com and owner-api.teslamotors.com) #3896

Closed
1 task done
aklira opened this issue May 19, 2024 · 7 comments
Closed
1 task done
Labels
area:tesla api Related to the Tesla API closed:invalid This doesn't seem right

Comments

@aklira
Copy link

aklira commented May 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Error fetching car data

Expected Behavior

No response

Steps To Reproduce

No response

Relevant log output

2024-05-19 08:49:06.025 [error] POST https://auth.tesla.com/oauth2/v3/token -> error: "non-existing domain" (5124.268 ms)
2024-05-19 08:49:06.039 [warning] Token refresh failed: %TeslaApi.Error{
  reason: :token_refresh,
  message: "non-existing domain",
  env: nil
}

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.28.5

@JakobLichterfeld JakobLichterfeld added the area:tesla api Related to the Tesla API label May 20, 2024
@JakobLichterfeld JakobLichterfeld changed the title Error fetching car data Owner API: non-existing domain May 20, 2024
@JakobLichterfeld
Copy link
Collaborator

same for https://owner-api.teslamotors.com/

@JakobLichterfeld JakobLichterfeld added the note:needs investigation The issue must be investigated first label May 20, 2024
@JakobLichterfeld JakobLichterfeld changed the title Owner API: non-existing domain API: non-existing domain (auth.tesla.com and owner-api.teslamotors.com) May 20, 2024
@JakobLichterfeld JakobLichterfeld added the note:help wanted Extra attention is needed label May 20, 2024
@KrzysztofHajdamowicz
Copy link

$ dig auth.tesla.com

; <<>> DiG 9.10.6 <<>> auth.tesla.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36932
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;auth.tesla.com.			IN	A

;; ANSWER SECTION:
auth.tesla.com.		16224	IN	CNAME	auth.tesla.com.edgekey.net.
auth.tesla.com.edgekey.net. 18945 IN	CNAME	e1792.dscx.akamaiedge.net.
e1792.dscx.akamaiedge.net. 20	IN	A	23.74.172.56

;; Query time: 50 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon May 20 14:38:43 CEST 2024
;; MSG SIZE  rcvd: 135
$ dig auth.tesla.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> auth.tesla.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47695
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;auth.tesla.com.			IN	A

;; ANSWER SECTION:
auth.tesla.com.		16941	IN	CNAME	auth.tesla.com.edgekey.net.
auth.tesla.com.edgekey.net. 17069 IN	CNAME	e1792.dscx.akamaiedge.net.
e1792.dscx.akamaiedge.net. 20	IN	A	23.74.172.56

;; Query time: 54 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon May 20 14:38:54 CEST 2024
;; MSG SIZE  rcvd: 135

Works in EU

@JakobLichterfeld
Copy link
Collaborator

Works in EU

The webserver itself, yes, the API endpoints seem down.

@JakobLichterfeld
Copy link
Collaborator

JakobLichterfeld commented May 20, 2024

Token generation with tesla_auth is possible, but TeslaMate complain tokens not valid, logs show

-> error: "non-existing domain"

Which indicates API Enpoint for my vehicle is down.

@aklira
Copy link
Author

aklira commented May 20, 2024

I've made a test to query the tesla auth api with the following query from the same host I am running teslamate:
curl -sX POST -H "Content-Type: application/json" https://auth.tesla.com/oauth2/v3/token -d @auth.json -w "%{http_code}\n"

And it works fine, I am getting the correct response content with http code 200

@JakobLichterfeld
Copy link
Collaborator

For me a flush dns and reboot solved the issue

@aklira
Copy link
Author

aklira commented May 20, 2024

Same thing here for me, a reboot fixed the problem. Issue can ben closed.

@aklira aklira closed this as completed May 20, 2024
@JakobLichterfeld JakobLichterfeld added closed:invalid This doesn't seem right and removed note:help wanted Extra attention is needed note:needs investigation The issue must be investigated first labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:tesla api Related to the Tesla API closed:invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants