Qwen Not Working? Check Status and Fix Common Errors

If Qwen is not working, first determine whether the failure affects everyone or only your browser, app, account, network, conversation, model, or feature. At the time of this check, Qwen’s main web pages were reachable and independent monitors did not show a broad outage, so a local or feature-specific problem is more likely—but that snapshot cannot rule out a new, regional, account-specific, or partial incident.

Status snapshot — October 13, 2026 at 12:16 UTC: Qwen’s official site and chat page returned pages during this review. Is-down.ai reported the web endpoint operational from its US monitoring location with no reports in the previous hour, while StatusGator also labeled Qwen up despite isolated recent user reports. Alibaba Cloud Health Status showed no active cloud incident. These signals are useful, but none proves that every Qwen feature, model, region, or account is healthy.

Before signing out, clearing site data, or reinstalling the app: copy any unsaved prompt or visible response, download generated files you need, save important conversation URLs, and confirm which account and sign-in method you used. Destructive troubleshooting can sign you out and may remove unsynced or guest-session state.

Is Qwen down right now?

There was no clear evidence of a widespread Qwen web outage at the verification time above. However, Qwen does not appear to provide a public, component-by-component status dashboard for its consumer chat service. Independent monitors can confirm that a public endpoint responds from their location, but they cannot see whether your account, a particular model, image generation, file analysis, web search, voice, or another feature is failing.

Use four signals together instead of trusting one status page:

Open the official service: try qwen.ai and chat.qwen.ai. A working landing page does not prove that generation is healthy, so send one short, non-sensitive test prompt in a new conversation.
Check more than one independent monitor: look for a simultaneous increase in failures or reports. One complaint is not proof of an outage.
Test a second route: use another network or device. If Qwen works there, the original browser, device, DNS route, firewall, proxy, or network is the likely problem layer.
Identify the product: Qwen Chat, the mobile app, Alibaba Cloud API access, Qwen Code, local Qwen models, and third-party services do not share one health state.

If the official site fails from multiple devices and networks while independent reports rise at the same time, wait for the service to recover rather than repeatedly deleting browser or app data. If Qwen works elsewhere, continue with the local checks below.

Diagnose the problem in two minutes

Protect your work. Copy the prompt, response, error text, and conversation URL before changing the session.
Start a new chat. Send a short plain-text prompt such as “Reply with the word test.” If this works, the problem is probably limited to the original conversation, its context, an attachment, or a selected feature.
Test ordinary chat separately from the failing feature. If text chat works but image generation, web search, voice, or file upload does not, treat it as a partial feature issue—not a complete Qwen outage.
Open a private window. If Qwen works there, suspect stored site data, a session problem, or an extension. Some browsers still allow selected extensions in private mode, so check that setting.
Try another current browser. If only one browser fails, focus on its privacy protections, content blockers, cookie rules, or cached site data.
Try another device or network. A successful test isolates the problem to the original device, network, VPN, proxy, firewall, or DNS path.
Read the exact message. A displayed usage limit, access restriction, permission request, or unsupported-feature message needs a different response from a blank page, timeout, or server error.

Symptom	Likely problem layer	Safest quick test	Next action
Qwen will not open on any device or network	Possible service or regional routing incident	Check the official pages and two independent monitors	Wait and report the incident if multiple signals agree
Qwen works in a private window	Stored site data, session, or extension	Retest with extensions disabled	Remove the narrow conflict or clear Qwen-only site data
Only one conversation fails	Conversation context, attachment, or transient generation failure	Send a short prompt in a new chat	Continue in the new chat and preserve the original URL
Text chat works, but one feature fails	Feature, permission, model, entitlement, or partial incident	Test a different feature or model if available	Check the displayed limit, update the app, or report the feature
The web version works, but the app does not	App version, local storage, permissions, or mobile network	Update the official app and test another network	Review permissions; reinstall only as a final step
Qwen Chat works, but an API request fails	API credentials, endpoint, model, region, quota, or cloud incident	Check the HTTP response, request ID, and cloud status	Use the API documentation or cloud support path
A locally run Qwen model fails	Local runtime, model files, hardware, or configuration	Read the local runtime logs	Troubleshoot the runtime rather than Qwen Chat

How to fix Qwen not working, in the safest order

Retry once, then stop repeated submissions. Copy your prompt first. One retry can clear a transient failure, but repeatedly pressing Send can create duplicate requests without identifying the cause.
Use a new conversation. If the new chat works, continue there. A very long thread, attachment, tool state, or one failed turn may be affecting only the original conversation.
Run a controlled plain-text test. Remove attachments, web search, image tools, and other optional features. A successful plain-text response shows that the core chat is available and narrows the failure to the removed element.
Confirm the official URL or app. Use qwen.ai or begin from Qwen’s official download page. Do not diagnose a third-party Qwen client as though it were the first-party service.
Reload the page or fully close and reopen the app. This resets the current interface process without deleting account or site data.
Test a private window. A successful result points toward the normal browser profile rather than a global outage.
Try another updated browser. If it works, return to the original browser and test privacy shields, extensions, cookie settings, and site data one at a time.
Temporarily disable one relevant blocker. Test one ad blocker, script blocker, privacy protection, or DNS filter at a time, reload Qwen, then re-enable it. Do not permanently turn off browser security.
Change the network path. Temporarily disconnect a VPN or proxy and compare Wi-Fi with mobile data or another trusted network. Do not use a VPN to evade geographic or account restrictions.
Update the browser, operating system, or official app. An official Qwen app response on Google Play specifically advises updating when supported media or voice features are missing.
Check permissions. Voice needs microphone access; camera or photo workflows need the relevant device permission; downloads and file selection can be blocked by browser or operating-system controls.
Sign out and back in only after saving your work. This can replace an expired session, but it also changes the state you are trying to diagnose.
Clear only Qwen’s site data. Use the browser’s site settings for qwen.ai instead of erasing all browsing data. Expect to be signed out, and do not assume guest or unsynced state will survive.
Reinstall the mobile app last. First confirm the correct account, save anything not synchronized, and verify that the web version works. Reinstallation is unnecessary when the same failure also occurs on the web and other devices.

Fix specific Qwen errors and symptoms

Qwen will not load, shows a blank page, or returns a gateway error

Open the official Qwen home page and chat page separately.
Check whether the same error occurs in a private window and another browser.
Compare a second network. If mobile data works but office or school Wi-Fi does not, the network path or filtering policy is the more likely cause.
Temporarily disconnect a VPN, proxy, or filtering DNS service, then retest.
If the failure appears on multiple devices and networks and independent reports rise, stop local changes and wait for Qwen to recover.

A gateway or server message does not automatically identify the underlying cause. Record the exact code, time, timezone, and URL instead of describing it only as “not working.”

Qwen says “The current content is empty, please regenerate”

This message is a symptom, not a reliable diagnosis. A documented DuckDuckGo Android browser report reproduced it on qwen.ai; the reporter could use another browser, and a DuckDuckGo contributor linked the breakage to that browser’s protections. That does not prove every occurrence has the same cause, but it makes a browser-compatibility test a high-priority step.

Copy the prompt and open a new Qwen conversation.
Send a short plain-text test without an attachment or optional tool.
Try a private window and a different updated browser.
If the second browser works, return to the first and temporarily test one privacy shield, script blocker, or extension at a time.
If the error appears across browsers, devices, and networks, check current outage signals and report the exact message to Qwen.

Qwen shows an internal error or cannot send the message

First determine whether the failure belongs to the prompt, the conversation, or the service. Save the prompt, create a new chat, and send a short text-only request. If that succeeds, add the original attachment or feature back separately. If every short request fails, compare another browser, network, and current status signals.

Capture any request ID, trace ID, or error code displayed by the interface. Do not publish session cookies, complete request headers, authentication tokens, or private document contents.

Qwen is stuck generating or unusually slow

Copy the prompt before stopping or leaving the page.
Test a short prompt in a new conversation.
Try another currently available model if the interface offers a model selector.
Split a long request into smaller steps and test attachments separately.
Compare another network to rule out route latency or filtering.
If all models and short prompts stall on multiple devices, treat it as a possible service incident rather than a prompt problem.

Qwen login is not working or keeps redirecting

Confirm that you are on an official Qwen domain.
Use the same sign-in method originally linked to the account. Email, Google, Apple, phone, or another method may lead to different account records.
Allow required cookies, redirects, and sign-in pop-ups for the test.
Try a private window or another browser to isolate a damaged session or protection conflict.
Set the device date and time automatically if authentication pages report an expired or invalid session.
If a verification option is unavailable in your region or the product displays an access restriction, use the official support route. Do not try to bypass the restriction.

Only image generation, video, web search, files, or voice is failing

If ordinary text chat works, Qwen as a whole is not completely down. Diagnose the individual feature:

Files or document analysis: read the type or size message shown by Qwen, then test a smaller non-sensitive file. Do not assume a fixed limit unless the current interface or official documentation states it.
Image or video generation: start a new chat, verify that the feature is still visible for your account, and update the official app. A missing option may reflect version, account, plan, rollout, region, or policy—not necessarily an outage.
Web search: confirm that the search option is enabled when the interface provides one, then compare a plain response without search. Save the query and report the feature if only search fails repeatedly.
Voice: verify microphone permission at both the operating-system and browser or app level, then test the microphone in another trusted application.
Conversation history: confirm the account and sign-in method, avoid clearing site data, and try any saved direct conversation URL. Missing history and failed generation are separate symptoms.

For PDF-specific preparation and upload checks, use our Qwen PDF upload and verification guide.

Browser privacy protection and extension conflicts

A browser conflict is especially likely when Qwen works in another browser or private window. The safest approach is a controlled test rather than permanently weakening protection:

Open Qwen in a private window with extensions disabled where possible.
If it works, return to the normal window and disable one relevant extension or privacy protection.
Reload Qwen and repeat the same short test prompt.
Re-enable the protection after the test.
If one setting is responsible, use the narrowest site-specific exception available or report the broken site to the browser vendor.

Do not disable antivirus software, firewall protection, or organization-wide security controls merely to access Qwen. On a managed work or school device, ask the administrator whether the domain, scripts, cookies, or streaming connection is blocked.

What to do when the Qwen mobile app is not working

Start from Qwen’s official download page so you do not troubleshoot an unrelated app with a similar name. If the official web version works but the app does not:

Force-close and reopen the app without deleting its data.
Install the latest version from the official store listing.
Compare Wi-Fi and mobile data.
Review microphone, camera, photo, file, and notification permissions only for the feature you are using.
Confirm the correct account and sign-in method.
Use the in-app help route before reinstalling if you can still reach Settings.
Reinstall only after preserving unsynced work and confirming that the account can be accessed elsewhere.

The current Google Play listing for Qwen – Alibaba AI Assistant directs users to the app’s Settings > Help Centre and lists [email protected] for issues and feature suggestions.

Account, usage-limit, plan, and regional problems

Do not infer a quota or regional restriction from a generic error. Use the wording displayed by Qwen and distinguish these cases:

Technical failure: the page, request, or feature errors without a specific entitlement message.
Usage limit: Qwen explicitly states that a limit has been reached. Follow the displayed reset or upgrade information rather than an unofficial number.
Plan or account access: the feature is visible but marked unavailable for the current account or plan.
Gradual rollout: another account or device has a feature that is not yet present on yours.
Regional availability: the official app store, product page, or interface says the service or feature is unavailable in the current region.
Policy restriction: the request is refused or the feature is limited for content or safety reasons. This is not the same as a server outage.

Limits, plans, supported regions, and feature availability can change. Verify them in the current first-party interface or documentation and do not rely on an old forum post.

Qwen Chat, API, Qwen Code, local models, and third-party apps need different fixes

Qwen Chat or the official app: use the browser, app, account, feature, and status checks in this guide.
Qwen API: the Qwen API Platform and Alibaba Cloud developer services have their own credentials, endpoints, model access, quotas, and health signals. Check the HTTP status, error body, request ID, account region, base URL, and model identifier. Never share the API key.
Alibaba Cloud services: use Alibaba Cloud Health Status for cloud incidents, but do not treat it as a component dashboard for the consumer Qwen chat app.
Qwen Code: use the official Qwen Code page, documentation, logs, and repository issue tracker. A Qwen Code authentication failure does not prove that Qwen Chat is down.
Local Qwen models: a qwen.ai outage does not stop a model already running locally. Check the local runtime, model files, available memory, hardware support, prompt template, and logs.
Third-party Qwen providers: check that provider’s status and account. The provider can fail while Qwen’s own web service remains available.

For client setup and login-route checks, use our Qwen Code setup and authentication guide.

For developer credentials and endpoint checks, see our Qwen API guide.

When and how to report a Qwen problem

Report the problem when it is reproducible after a clean-browser test, affects more than one device or network, repeatedly affects one feature, prevents account access, or displays an error code that ordinary troubleshooting does not resolve.

Include:

The exact error message.
The date, time, and timezone.
The official URL or app version.
The operating system and browser version.
The account sign-in method, without credentials.
The affected model, conversation type, or feature.
Whether another browser, private window, device, or network worked.
Short reproduction steps.
A request ID, trace ID, or error code if shown.
A screenshot with names, email addresses, documents, payment details, and other private information removed.

Never send a password, one-time code, session cookie, authentication token, API key, full request headers, private document, or billing information. For the current official Android app, Qwen lists Settings > Help Centre and [email protected] as feedback routes.

Safe temporary workarounds

Save the prompt locally and retry after current incident signals clear.
Continue in a new Qwen conversation if only one thread is broken.
Use another available Qwen model if only one model fails.
Switch between the official web and app experiences when one remains functional.
Use another assistant only for non-sensitive work and recheck its privacy terms before uploading files.
For technically capable users, a suitable open-weight Qwen model can run locally, but local setup and hardware troubleshooting are separate from Qwen Chat.

Frequently asked questions

Is Qwen down right now?

No broad Qwen web outage was visible at the October 13, 2026, 12:16 UTC check. The official pages responded, independent monitors classified the service as operational, and Alibaba Cloud showed no active cloud incident. This is a point-in-time result, not a guarantee for every location, account, model, or feature.

What does “The current content is empty, please regenerate” mean?

The message does not identify one confirmed cause. It can accompany a failed generation or browser compatibility problem. Copy the prompt, try a new chat, then compare a private window and another browser before clearing data.

Why does Qwen work in a private window but not normally?

The normal browser profile likely contains conflicting site data, a session issue, or an extension or privacy rule that is absent from the private test. Disable one relevant protection at a time or clear only Qwen’s site data after saving your work.

Will clearing Qwen site data delete my chats?

Clearing site data will normally sign you out, but the effect on guest, local, unsynced, or account-synced state should not be assumed. Save important prompts, outputs, files, and conversation URLs, and confirm the account before clearing anything.

Why is one Qwen feature broken while chat still works?

The feature may use a different model, permission, tool, entitlement, rollout, or service path. Test plain chat, a new conversation, and another available feature. Report it as a feature-specific failure rather than a complete Qwen outage.

Is Qwen Chat status the same as Qwen API status?

No. Consumer chat, the official app, API services, Qwen Code, local runtimes, and third-party providers can fail independently. Check the status and logs for the product you are actually using.

How should I report a Qwen bug?

Provide the exact error, timestamp and timezone, device, operating system, browser or app version, affected feature, reproduction steps, and the results of another-browser and another-network tests. Remove private information and never include credentials or API keys.

Sources checked

Qwen official website and Qwen Chat for first-party reachability.
Qwen official download page for the current app route.
Qwen – Alibaba AI Assistant on Google Play for current app features, update guidance, and support routes.
Alibaba Cloud Health Status for cloud-service incidents.
DuckDuckGo Android issue #6106 for a documented browser-protection compatibility case involving qwen.ai.
Is-down.ai and StatusGator as independent, non-official outage signals.

Independent monitors and community reports were used only as diagnostic signals. They do not replace official confirmation of an outage, limit, policy, feature availability, or root cause.