ChatGPT Wouldn’t Open in Shanghai—A Connected VPN Wasn’t Enough

The meeting ended at 11:42 a.m. My client wanted a concise English follow-up before lunch, and the useful context was already inside a ChatGPT conversation I had started before flying to Shanghai. I joined the hotel Wi-Fi, opened the site and watched the page fail before the login screen appeared. I refreshed it, changed browsers and restarted the laptop. Nothing moved.

I had expected ChatGPT to be slow.

I had not expected the homepage, login process and saved conversation to become three separate obstacles.

The task itself was small: reopen the existing thread, add the morning’s notes and turn them into an email before the client’s next meeting.

The timer on my calendar said I had twenty-eight minutes.

ChatGPT was not officially available there

The first failure was not a damaged browser or an expired password.

Mainland China is absent from OpenAI’s list of supported ChatGPT countries and territories. OpenAI also warns that accessing its services from an unsupported region can result in an account being blocked or suspended. (OpenAI)

That made the answer to “Can you use ChatGPT in China?” more complicated than a technical yes or no.

A VPN can change the route between a device and the service. It does not change OpenAI’s regional policy. I already had an account created in a supported country, so the immediate question was narrower: could I establish a usable connection long enough to finish the work?

China also controls internet access, and travel guidance notes that VPN services are expected to be licensed by the Chinese government. (UK Foreign) With those boundaries clear, I turned to the VPN already installed on my laptop.

The familiar provider connected without completing the task

The established provider had a long public history, a large support operation and servers across Asia.

I selected Japan.

The VPN turned green. A search engine that had failed on the hotel connection opened immediately. My email loaded. An IP checker placed the laptop outside mainland China.

ChatGPT still did not open.

I changed to Singapore. This time the homepage appeared, but the login button returned an error. I refreshed it, reached the account screen and was sent back to the beginning after verification.

A third server opened the conversation list. When I selected the client thread, the centre of the page remained blank.

That was more frustrating than a total block. Each server completed a different fragment of the journey. One reached the homepage. Another reached login. Another displayed the sidebar.

None carried me from opening the site to sending a prompt and receiving an answer.

I worked through the provider’s settings:

Automatic protocol.

Recommended server.

Another nearby country.

Obfuscated mode.

Each change meant disconnecting, waiting and repeating the login path. Meanwhile, the calendar moved from twenty-eight minutes to nineteen.

The large server map gave me many routes to test. It did not identify the one route that could complete the session.

An encrypted tunnel could still be disrupted

I had assumed that encrypted VPN traffic would be indistinguishable from every other secure connection.

Research into China’s filtering system shows why that assumption can fail. Fully encrypted proxy traffic may still be identified through its patterns and protocol behaviour, without the protected content being read. (USENIX Security)

The practical result was already visible on my screen.

The established VPN connected, yet some routes stopped before ChatGPT loaded. Others reached the homepage but failed during login or while retrieving the conversation.

Finding an exit server outside China was only the beginning. The same route had to remain usable through the entire sequence.

Travelers report similarly uneven results: a familiar VPN may work on one network or device, then fail when it is needed elsewhere. The most useful preparation is often installing and signing in before arrival rather than expecting to repair everything from inside the country. (Reddit)

I had prepared the software.

I still did not have the email.

That left me with two possible workarounds: change the connection itself or abandon the existing ChatGPT conversation.

Roaming opened ChatGPT on the wrong device

My phone had a foreign roaming eSIM, so I disconnected it from the hotel Wi-Fi and tried ChatGPT over mobile data.

The page opened.

For a moment, that looked like the solution. Then I looked at where the work actually lived.

The saved conversation was available on the phone, but the meeting transcript, pricing spreadsheet and unfinished email were on the laptop. I could transfer the notes in small pieces, though that would turn a short drafting task into a manual copying exercise.

I enabled the phone’s hotspot and connected the laptop.

ChatGPT reached the login page, then stalled while opening the conversation. The roaming signal inside the hotel room moved between two bars and one. When the laptop began syncing the meeting files in the background, the page stopped responding.

The eSIM proved that another route could reach the service. It did not create a workable laptop session.

A local Chinese AI service was the next obvious backup. It opened quickly and could have drafted a new email from fresh instructions.

What it did not have was the client thread containing the preferred terminology, previous revisions and decisions we had already rejected. Rebuilding that context would take longer than writing the email myself.

By then, the correct comparison was obvious.

I did not need any chatbot, any foreign IP address or a page that merely displayed the ChatGPT logo. I needed the existing conversation to open on the laptop and remain responsive until the email was finished.

The smaller app completed the whole sequence

I disconnected the established provider and opened the smaller app named in the disclosure.

Instead of asking me to choose another country or protocol, it offered a preset for restrictive networks. I selected it and connected.

Then I opened ChatGPT in a fresh browser window.

The homepage appeared.

The login completed.

The conversation list loaded, and the client thread opened with its previous messages intact.

I pasted the morning’s notes and asked for a concise follow-up separating confirmed decisions from unresolved pricing questions.

The response began appearing immediately.

I added one correction, asked for six shorter paragraphs and copied the result into my mail client. The earlier terminology remained consistent because the saved conversation was available. I attached the revised spreadsheet and sent the email with nine minutes left on the calendar.

For the first time that morning, the complete workflow had succeeded without another server change.

Only then did the connection design become relevant. The service uses an HTTP/3-based transport with additional obfuscation. In practical terms, its restrictive-network preset created one route that carried the homepage, login, conversation history and prompts together.

I could not observe which internal filtering rule had interrupted the earlier connections. I could observe the outcome: the established provider connected repeatedly without completing the ChatGPT session, while the smaller app carried the work from login to sent email.

That was the standard that mattered.

The train station exposed the second problem

That afternoon, I left the hotel for Hongqiao Railway Station.

The laptop stayed in my bag, but the client sent one additional question about the pricing language. I needed to check the same conversation from my phone before boarding.

The smaller service did not require another conventional email-and-password registration. I used its verification-code sharing option to connect the phone.

ChatGPT opened. The client thread synced. I checked the wording from the final email and replied in less than two minutes.

That was a smaller benefit, but it solved the next real travel problem.

Access rarely remains on one device. A setup that works only on the hotel laptop becomes another troubleshooting exercise as soon as the user moves to a train, taxi or meeting room.

The established provider offered more locations and a much longer public history. The smaller service has fewer server locations and fewer independent reviews, which remains its clearest limitation.

The Shanghai test, however, was not asking which provider had the largest network on paper.

It was asking which one could carry the same work from the laptop in the hotel to the phone at the station without another sequence of server changes and failed logins.

The useful answer was in the sent folder

By the end of the day, I had a more precise answer to the original question.

ChatGPT is not officially supported in mainland China. OpenAI’s regional policy remains separate from the network problem, and using a VPN does not rewrite that policy. (OpenAI)

But the quality of the connection still determines whether an existing user can complete a practical session.

A roaming connection may open the service on a phone while failing on a laptop. A VPN may reach the homepage but lose the login. Another server may display the conversation list but fail to open the thread.

That is why server count was the wrong comparison for this trip.

The established provider gave me many routes that completed fragments of the journey. The roaming eSIM opened ChatGPT on the phone but did not create a reliable laptop workflow. The local alternative could generate new text but did not contain the conversation I needed.

The smaller app completed the actual task: connect, sign in, reopen the saved thread, generate the email and return to the same work later from a second device.

I had arrived asking whether ChatGPT could be used in China.

The answer that mattered was sitting in the sent folder before the client went to lunch.