540 Vehicle Server Error

[DarthStar]

This is what Tesla have just replied. I am only logged into the same apps as I’ve been logged into for years….


Hello, remote diagnosis has confirmed that the issue being caused by repeated data requests from a third party. A third party application is spamming your Model 3 for status updates, preventing communication with the Tesla APP.
Even if the third party had the credentials and was then deleted, your Tesla will still be under the control of a third party as the credentials are still stored in their databases.
We can remotely resolve this issue for you by completing the following steps;
1. Change your myTesla password and discontinue use of the apps.
2. The security credentials then need resetting to prevent the vehicle from being woken.
Please provide consent to reset the credentials, this will sign out all accounts.
Once this is complete, sign back into the APP and the connection should then be restored.
Please could you reply to this message once step 1 is complete if you give your consent to reset the credentials.
Kind regards , Tesla Service.

Interesting theory. When I first got this error, I had NO third party apps. Since then, I've started using Stats (and only Stats) and have not had a repeat of the error.

Not saying they're wrong, but I don't think third party apps are the cause in all cases. Certainly not in mine.

 

[Pagemakers]

I’ve had stats installed for years with no issues.

However, I’ve done as Tesla suggest. Let’s see what happens over the next couple of days.

 

[Pagemakers]

Well Tesla’s fix hasn’t fixed anything. Car still unreachable after a few hours with no apps connected.

 

[SidetrackedSue]

Well, it is a worldwide issue today.

And my first thought (as someone who was without a voip phone for a couple of weeks last month) was a DDoS attack for ransomware.

The fact that Elon replied "Checking...." but then didn't update for several hours didn't assure me I was being paranoid.

Finally, previously Tesla has claimed:

A third party application is spamming your Model 3 for status updates, preventing communication with the Tesla APP.

Which adds to my theory since those with the ransomware were building a botnet to spam for status updates to take down the App.

 

[Pagemakers]

Problem is the 2 apps I have installed are very well known and have been on my account for years without an issue. I’m sure my problems weren’t caused by those apps. I have spoke the the app developers and they have responded to me immediately.

 

[DMadd]

Hello, New to TMC with a new to me 2018 MX 100D. I am interested in seeing home charging amounts and costs.
I have been trying to use STATS and today started a 2 week trial of Tessie. Since day one the installation of STATS has been very intermittent with being able to see data past the opening page. I keep getting 503 errors noted as 'the operation has been limited due to an earlier error: request failed with HTTP status code 503. Support for STATS said this is an intermittent error from the Apple side of ICloud for a few users.
I installed Tessie (2 week trial) to see if it was any better. I did get connection with Tessie when I could not get connected to STATS.
BUT.. this evening all three (Tesla original and two 3rd parties) would not connect. I got OEM and Tessie to connect time after a two button reboot. STATS still not showing data.
Was this problem and the 504 related to what you are seeing?
Frustrated with cost of a less than stable app.

Thanks
Danny

 

[Pagemakers]

I do have stats installed but I’ve had it installed for 5+ years with no issue. I did write to the dev and he assured me it’s not his app.

Currently I have no app installed and have done a reset and password change per Tesla’s instructions. I currently can’t connect to my car but I think this is due to the worldwide outage at the moment. However, the 540 server error is not showing currently.

 

[DMadd]

I do have stats installed but I’ve had it installed for 5+ years with no issue. I did write to the dev and he assured me it’s not his app.

Currently I have no app installed and have done a reset and password change per Tesla’s instructions. I currently can’t connect to my car but I think this is due to the worldwide outage at the moment. However, the 540 server error is not showing currently.

@Pagemakers, Thank you. I will TRY to continue to be patient. Hopefully it will sort it out in the next 13 days before I need to make a decision on one or the other.

 

[FLUXCAP1]

I just noticed this today on my Model 3. Will try the two-button reboot. But it sounds like a Tesla server issue...not a vehicle issue.

 

[flyinghawaiian]

I get this error everyday. Tesla told me to change my password but that didn't work.

 

[Tcatz]

The error cleared after a reboot.

Yeah reboot seems to do the magic

 

[flyinghawaiian]

Yeah reboot seems to do the magic

It does, but only for a day, then I get the issue comes back

 

[Jacopa]

Yep I've been getting this all of a sudden too, good news is the car recognizes the phone and the 2button reboot works, for a while.

 

[morsecp]

This has happened to me twice this week. Never happened in the previous 6 weeks of ownership.

 

[Driver08]

I got this error after updating to 2021.44.25.6 and filed a service request. Tesla responded that it is a known issue, and advised to do the two-button reboot. That seems to have fixed it, although I won't be surprised if it happens again given what I'm reading on the forums.

 

[ScoGold]

I have been receiving this error for the last few days 2021 M3 2021.44.30.

I opened a ticket in the app, so let’s see what they push out.

 

[SlimJim]

I have the same issue.
This is a problem as i cannot preheat the car.

 

[OCJeff]

This is happening now for me (just started mid-day).

Is there a "fix" or just wait for it to self-resolve?

Also, I noticed that I can control the car (open/close windows which I did as a test).

 

[whatthe2]

This is happening now for me (just started mid-day).

Is there a "fix" or just wait for it to self-resolve?

Also, I noticed that I can control the car (open/close windows which I did as a test).

Should just go away, but if not do a two button reboot.

 

[OCJeff]

Should just go away, but if not do a two button reboot.

Just to confirm.... 36 hours later and the vehicle was still returning 540 error in-app. When on bluetooth (near the MY), then the app could control it. Too far away and I had no control and no connection.

Two button reset fixed it straightaway and still good 12 hours later.