"This site can't be reached" error message after successfull installation

[marcbaier]

I sucessfully followed all the installation steps. I can see four running containers in my local synology NAS docker. However, when I enter the IP address of the NAS: 192.168.xx.xx:4000 I am not getting any content but only "this site an't be reached".

What wold be the next steps to check what is going wrong ? Access to my Synology works fine via 192.168.xx.xx:5000

Do I need to check if the port 4000 is open ?
Thanks so much for your help !

[pazzotranquillo]

I got exactly the same issue after updating to version 1.25.2.

Any help would be really appreciated!

Thanks

[scottcline]

Seems as if Tesla deprecated all v2 tokens, and only v3 tokens are valid. According to this article, TM needs to be updated to support v3 tokens.

https://electrek.co/2022/01/13/hacker-tesla-resetting-third-party-app-access/

[refrain]

Mine isn't working on the latest version either, and I upgraded from 1.25.0. Use version 1.25.0 instead of 'latest' (1.25.2):

docker-compose.yml

services:
  teslamate:
    image: teslamate/teslamate:1.25.0

[pazzotranquillo]

Downgrading to 1.25.0 also worked for me. Thanks for the suggestion.

[herbit]

If you are running Debian 10 (Buster), the issue is probably this one: #2302
See the suggested solution with the Buster back port in the thread.