Constant "Reconnecting..."

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I try to start of continue a chat I get “Reconnecting…” a couple of times and then it fails.

A couple of day ago it was working no problem. I tryed a VPN on/off, my wifi, cafe wifi, mobile hospot.. nothing..
I reinstalled, relaunched, delete all local files, did network diangostic, in the new UI, in the old UI
Cursor Status pages says its all ok

what to do?

When I click the Request error ID i got:

Request ID: 729aaeba-c569-42fa-abd3-dab0f5c94e89
[internal] Invalid time zone specified: Etc/Unknown
mIe: [internal] Invalid time zone specified: Etc/Unknown
at mg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24345)
at dg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at wg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at nCh.run (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async lQi.runAgentLoop (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41749:12418)
at async mim.streamFromAgentBackend (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:12344)
at async mim.getAgentStreamResponse (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async hCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Xa (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4244)

Steps to Reproduce

Open Cursor
Try yo send a message on chat
“Reconnecting…”

Operating System

Linux

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.12.69

For AI issues: add Request ID with privacy disabled

Request ID: 729aaeba-c569-42fa-abd3-dab0f5c94e89
[internal] Invalid time zone specified: Etc/Unknown
mIe: [internal] Invalid time zone specified: Etc/Unknown
at mg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24345)
at dg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at wg_ (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at nCh.run (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async lQi.runAgentLoop (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41749:12418)
at async mim.streamFromAgentBackend (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:12344)
at async mim.getAgentStreamResponse (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async hCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Xa (vscode-file://vscode-app/home/cnk/.cache/appimage-run/7e9892c4de777c609be7fa5617e1ecaf0e23972a261fd80eabd1230ccd9362a0/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4244)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this is a known issue. When the OS reports the timezone as Etc/Unknown, which is common with some Linux setups and AppImage, Cursor can fail to parse it. You can see that in the trace too: Invalid time zone specified: Etc/Unknown. It’s already tracked, but there’s no ETA for a fix yet.

Workaround: set the system timezone explicitly:

sudo timedatectl set-timezone America/Argentina/Buenos_Aires
timedatectl   # make sure Time zone is set correctly

Then restart Cursor.

If timedatectl isn’t available on your distro, you can launch the binary with an environment variable:

TZ=America/Argentina/Buenos_Aires appimage-run /path/to/Cursor.AppImage

Let me know if it helped. If you still see Reconnecting… after changing the timezone, send a new Request ID and I’ll take a look.

7 
TZ="America/Argentina/Buenos_Aires" appimage-run ./Cursor-3.2.16-x86_64.AppImage

this did the trick! thanks

10

Hey @Ceneka

Update: the server-side fix is deployed. The Invalid time zone specified: Etc/Unknown error in Chat or Agent should no longer happen. We fixed a backend crash when the OS reports an invalid time zone.

You no longer need the workaround of manually setting your system timezone, and you don’t need to restart or update Cursor.

If you’re still seeing the error, please start a new thread and include your Request ID and Cursor version.