TeslaMate 4.0.0 still receives 403 on /products and /vehicles after upgrade --> solve with v4.0.1

[Xsantos]

Hi,

I'm still affected after upgrading to TeslaMate 4.0.0.

Setup

TeslaMate 4.0.0
Docker
Raspberry Pi 5
aarch64
PostgreSQL 16
Image pulled on 2026-06-14
Running image: sha256:1c4f03e1c8a8e43269ac24c78a2f4a4a021637bbedf600d4b951ec1223889a4e

What I did

Upgraded from 3.x to 4.0.0
Pulled latest image
Restarted containers
Generated a new refresh token using Auth for Tesla
Logged in again

Current behavior
Token refresh works:

POST https://auth.tesla.com/oauth2/v3/token -> 200
Refreshed api tokens

But every vehicle request still fails:

GET https://owner-api.teslamotors.com/api/1/products -> 403
GET https://owner-api.teslamotors.com/api/1/vehicles/ -> 403

TeslaApi.Error / %{
"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api"
}

TeslaMate detects my vehicle (Model 3 SR+), but the status remains "unavailable".

The Tesla mobile app works normally and can access the vehicle without any issues.

Is anyone else still seeing 403 errors on /products and /vehicles with TeslaMate 4.0.0 after the TLS v1.3 fix?

[dr-busch]

Exactly the same here, running on RPi5 (Ubuntu) through docker. Only difference is I'm on PostGreSQL 17, but otherwise identical setup. Mine did seem to work for a while after upgrading to 4.0, but then back to the same issues. Refreshing API tokens is fine, but all the requests are 403 errors, same as you've listed. Is this an issue with the RPi version of the stack running HTTP/1.1 instead of HTTP/2?

[Xsantos]

Interesting. I'm seeing the same issue on a Raspberry Pi 4 (aarch64) running Docker.

My setup:

TeslaMate 4.0.0
Raspberry Pi 4 (64-bit / aarch64)
PostgreSQL 16
Latest Docker image pulled on June 14
Tesla app works normally
Refresh token works (POST /oauth2/v3/token -> 200)

However TeslaMate still gets:

GET https://owner-api.teslamotors.com/api/1/products -> 403
GET https://owner-api.teslamotors.com/api/1/vehicles/ -> 403

with:

forbidden, see https://developer.tesla.com/docs/fleet-api

I upgraded to 4.0.0 and generated a new refresh token, but the issue remains. So it does not seem to be limited to Raspberry Pi 5.

[Xsantos]

Correction: I'm running a Raspberry Pi 4 (aarch64), not a Raspberry Pi 5 as stated in the original post.

[giraygokirmak]

I have full blown dell r210ii xeon server with teslamate 4.0 docker stack i got the same problem. Renewed auth and refresh keys, dropped and composed stack both wont help

[azertsenemadommeg]

I try to get around that how relevant is the information that you run it on a DELL server.

[feartheclown]

See: #5399 (comment)

There's an issue w/ 4.0. Pull Request 5406 seems to have resolved it but have to update yaml to pull it until it is put in the main. #5406

Edit: issue now resolved with release 4.0.1 so no need to install PR #5406

[wertasd]

As @feartheclown has mentioned I have updated my docker-compose.yml file with "image: ghcr.io/teslamate-org/teslamate:pr-5406" and now is OK. Thank you

[feartheclown]

Looks like they just released 4.0.1 about an hour ago. I just pulled it and it is working. If you installed PR #5406 just revert back the yaml line to image: teslamate/teslamate:latest then follow normal update instructions.

[mondychan]

v4.0.1 fixed it for me!

[jpizquierdo]

Fixed for me!! Previously in version 2.X.X, it seems to affect all of us! Thanks for the quick fix guys

[Xsantos]

v4.0.1 fixed it for me too. Thank You!