Bug in X DMs (X Chat) showing "Unable to communicate with server" Causes of the error and how to fix it when an error occurs even after entering the passcode
When attempting to open XChat (formerly DMs), some users have suddenly been prompted to enter a passcode, and even after entering the correct passcode, they see [Unable to communicate with server. Please check your network connection and try again.] and are unable to proceed. This issue has been occurring since around April 14.
It is occurring in both the mobile app and the web client, and appears to be a temporary issue.
Table of Contents
Details of the issue
With this issue, when trying to open XChat, users are prompted to enter or newly set a passcode (PIN), and even after entering the correct passcode, the error message [Unable to communicate with server. Please check your network connection and try again.] appears, preventing them from proceeding.
This issue has been occurring in both the mobile app and the web client since around April 14.
XChat is X's new chat service, and traditional DMs have been integrated into XChat.
XChat includes features such as encryption, disappearing messages, and file transfer, and overall offers stronger security and privacy than DMs.
In XChat, messages are encrypted so that not even X itself can view them, and only the user can read them.
However, because encryption has been implemented in XChat, users are now required to set a 4-digit passcode.
With this issue, even if users enter the passcode they should have already set, an error occurs and they are unable to open XChat.
Messages in XChat are not encrypted directly with the 4-digit passcode that was set. Instead, the system uses the 4-digit passcode to protect a dedicated secret key (a key used to restore encrypted messages) stored on the server.
Given that it is occurring in both the app and the web client, this issue is likely a problem on X's server side.
XChat also experienced a different issue in early April.
It is better not to reset the passcode casually
The 4-digit passcode for XChat is used to store and restore the secret key required to decrypt conversation history.
If you have already set an XChat passcode and have a device on which the passcode has already been entered, you can reset the passcode from the chat settings.
However, if you have already set a passcode but do not have any device that has already entered the passcode and can access XChat, resetting the passcode will result in the loss of encrypted conversation history.
Even in that case, older unencrypted messages will still remain visible, but encrypted messages will no longer be accessible.
Even if you do have a device on which the passcode has already been entered, it is better to avoid resetting it while this issue is currently occurring.
If you forget the passcode, in the worst case you may be unable to restore your conversation history, so casually resetting the passcode is not recommended.
How to fix it
It is recommended that you wait a few days and then try entering the correct passcode again.
As mentioned above, casually resetting the passcode is not recommended, and if you enter the wrong passcode too many times, you may also lose access to encrypted messages.
It is unclear whether a case in which you entered the correct passcode but still received an error is counted as a failed passcode attempt, but if it is counted, repeatedly trying could make it impossible to restore encrypted messages permanently.
If you have not yet set up an XChat passcode, wait a few days and then try setting the passcode using the method introduced in the article below.
Please note that you cannot use DMs (XChat) unless a passcode has been set.
Conclusion
Since around April 14, there has been an issue in which even if users enter the correct passcode in XChat, [Unable to communicate with server. Please check your network connection and try again.] is displayed and they are unable to proceed.
It is occurring in both the mobile app and the web client, and appears to be a temporary issue.
It is recommended that you do not reset the passcode or keep forcing attempts, and instead wait a few days before trying again.
Share this article
Follow us for updates
Adding us to your preferred sources on Google makes it easier to find our articles on Google. Also, be sure to follow us on X and our RSS feed.
-1.png&w=1080&q=75)
I've been using JavaScript more than my native language since birth. I am nowhere and everywhere on the internet.
I build web apps and browser extensions in TypeScript as a web frontend programmer. I released Shadowban Scanner, a tool that detects shadowbans on X, and Restore Link Card, a tool that brings back link cards. Media outlets in Japan and abroad covered both tools. For iGEM 2023, I built the Wiki for Team Japan-United and helped the team win the Grand Prize. On my blog, I cover news about X and social media, test and troubleshoot bugs, and share frontend development insights.
