Tesla-Owner-API down? teslamotors/vehicle-command?

[AnotherDaniel]

Hi all - thank you to the contributors for the work on this project!

One question which I'm not sure is an issue, or something that I just couldn't find any info about: for some time now, my teslamate setup cannot connect to the Tesla APIs anymore (upgraded today, didn't look for a while). I'm getting "Error: :nxdomain" from teslamate, pinging owner-api.teslamotors.com from any of my machines results in 100% packet loss.
This would rhyme with the info from Tesla themselves, that this API is being disabled, and to use teslamotors/vehicle-command as a Rest proxy instead (https://github.com/teslamotors/vehicle-command/tree/main?tab=readme-ov-file#using-the-http-proxy).

Now - what am I missing? Is teslamate 2.2.0 working for everyone, and something's borked in my home network? Or should I be running this proxy, but haven't gotten the memo? etc...

Thanks for any input, Daniel

[brianmay]

It is still working for me.

I think it is normal for owner-api.teslamotors.com to blocking pings.

:nxdomain would suggest that there is a DNS issue inside your docker instance, or whatever you are using.

[AnotherDaniel]

You're right... this sounds like a name resolution issue rather than the endpoint being gone.
Ok thanks for the info that the Tesla server should still work, I'll look into the DNS issue next chance I get!

[AnotherDaniel]

Ok - @brianmay you're correct of course, it was docker DNS issues. Why only recently, and not years ago when I set this up, I don't know. Whatever, teslamate connects again, now!