Tesla drivers no longer have access to their cars by server error • The Register



Some Tesla drivers who were in the mood for a ride on Saturday were unable to do so after an update to the cars companion app produced server errors.

Tesla do not use conventional keys. Instead, they require the presence of a key fob, key card, or authenticated mobile phone app that connects to EVs via Bluetooth. It’s apparently easier and / or more convenient than a wrench, or something. Heck, everything is better with Bluetooth, isn’t it?

Drivers who use the app to start their cars have reported that they cannot activate their cars with their apps.

Tesla Founder and CEO Elon Musk personally responded to the above tweet, with the following information:

Measures like, perhaps, allowing people to open their cars with keys? Just a suggestion.

Tesla appears to have made no further public statements about the incident. The company placed its support forums behind a record wall earlier in 2021 and owning a MuskMobile is a requirement for entry. Your correspondent is therefore not in a position to explore the official missives. Tesla’s Twitter account is silent on this, and the electric car business doesn’t care about Facebook. The exact nature of the failure is therefore difficult to guess.

Which leaves us trying to guess what a combination of server error 500 and “increased network verbosity” might mean.

A clue tells us that the Tesla app was updated on November 18 to version 4.3.0 on iOS and 4.2.3-742 on Android.

Downdetector.com fault tracking site checked in outages on Saturdays – a few days after removing app updates – and The register Cannot find any reports of Brick MuskMobiles immediately after upgrading the app. It looks like the app is off the hook as a source of network verbosity.

Error 500, defined by the World Wide Web Consortium as an internal server error, produces the error message “The server encountered an unexpected condition that prevented it from fulfilling the request.” “

So could Musk’s Tweet suggest that something related to Tesla’s app user authentication has been changed to be more detailed and effectively DDOSed Tesla’s own infrastructure? We can only speculate.

Whatever the cause, it was quickly corrected. The Downdetector report says the outages ended after about four hours, leaving drivers behind electrified wheels and the rest of us wondering if CEOs responding to tweets is the new best practice for tech support. ®





Source link

Previous Watch robotic waiters bring food to diners, clear tables: the job crisis
Next Sify Technologies: Embrace Hybrid Cloud with VMC on AWS