Timeout when connecting to Tesla servers ... but only on one server. SSL issue in TeslaMate?

[segdy]

I have been running TeslaMate for nearly a year on a European server and works flawlessly. Now I wanted to move to a US server and I used backup/restore exactly as in the manual (Note: it's a US car in the US). Successfully moved thanks to #4488

After it I saw it didn't work any more I realized I am getting time out when connecting to server. Log is full of these messages:

teslamate-1  | 2025-01-12 10:10:28.772 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744540377860457 -> error: :timeout (5185.911 ms)
teslamate-1  | 2025-01-12 10:10:28.773 car_id=1 [error] Error / :timeout

In contrast, on the European server, everything else identical, it works:

teslamate-1 | 2025-01-12 10:03:14.272 car_id=1 [info] Start / :asleep
teslamate-1 | 2025-01-12 10:07:27.324 car_id=1 [info] Start / :online
teslamate-1 | 2025-01-12 10:07:27.552 car_id=1 [info] Connecting ...
teslamate-1 | 2025-01-12 10:08:09.026 [info] Update available: 1.28.3 -> 1.32.0

In Europe, I can test the API just with wget successfully:

# wget https://owner-api.teslamotors.com/ -O-
--2025-01-12 10:10:34-- https://owner-api.teslamotors.com/
Auflösen des Hostnamens [owner-api.teslamotors.com](http://owner-api.teslamotors.com/) ([owner-api.teslamotors.com](http://owner-api.teslamotors.com/))… 52.211.84.165
Verbindungsaufbau zu [owner-api.teslamotors.com](http://owner-api.teslamotors.com/) ([owner-api.teslamotors.com](http://owner-api.teslamotors.com/))|52.211.84.165|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 404 Not Found
2025-01-12 10:10:35 FEHLER 404: Not Found.

However, in the US, it's stuck at "Connecting..." forever:

# wget https://owner-api.teslamotors.com/ -O-
--2025-01-12 10:14:04--  https://owner-api.teslamotors.com/
Resolving [owner-api.teslamotors.com](http://owner-api.teslamotors.com/) ([owner-api.teslamotors.com](http://owner-api.teslamotors.com/))... 52.11.254.23
Connecting to [owner-api.teslamotors.com](http://owner-api.teslamotors.com/) ([owner-api.teslamotors.com](http://owner-api.teslamotors.com/))|52.11.254.23|:443... connected.

Eventually, after long time, I am getting:

Unable to establish SSL connection.

Note, the IP address is different (I assume it's anycast). I manually tried to add 52.211.84.165 to /etc/hosts but it's the same. So the issue is not the server/Tesla side.

Any advice?

[cwanja]

What US service / provider / host are you trying to connect from?

[segdy]

It’s not an IP level issue, see above. Connection establishes but something gets wrong during the SSL handshake.

I can successfully telnet there to port 443

[ngardiner]

Check the date/time on your server, if it is really out of whack (forward or backward, talking years here) it may be rejecting the server's cert due to being invalid.

[brianmay]

To me it looks like Tesla is blocking you.

[segdy]

No. After long time I found the issue: Tesla is discarding/blocking/ignoring ICMP need fragmentation packets.

I have a WireGuard tunnel (MTU 1420) in between. In order for larger response packets from Tesla server to reach me, they need to be fragmented (Note: They have DF bit set).

sinxe they are ignoring ICMP messages from my edge router, their packets are always too large for the intermediate wg tunnel and being discarded