Why Is Disqus Not Working? | Fix The Real Cause

When Disqus breaks, it rarely feels random. The thread may spin forever, vanish on some posts, show the wrong comments, or refuse to let readers sign in. Those glitches usually come from a short list of causes. Once you know where the break starts, the fix gets a lot simpler.

This article walks through the checks that solve most Disqus problems on blogs, news sites, and custom builds. You’ll see what to test first, what site owners should verify in code, and what readers can try on their own browser before giving up.

Why Is Disqus Not Working? On Your Site Or In Your Browser

The first job is figuring out where the failure lives. Disqus can fail at the site level, the page level, or the visitor level. If you skip that step, you can spend an hour fixing the wrong thing.

Site-level trouble usually shows up on every article. Page-level trouble hits one post or one template. Visitor-level trouble happens only on one browser, one device, or one network. That pattern tells you where to start.

• Site-level signs: no thread anywhere, endless loading on all posts, blank comment box after a theme change.
• Page-level signs: one article shows the wrong thread, missing comments on a single post, duplicate comment threads tied to similar URLs.
• Visitor-level signs: one reader can’t log in, comments load in one browser but not another, posting fails after privacy tools block cookies or scripts.

If you run the site, test one post in a private browser window, then test the same post on mobile. If it fails in both, the issue is probably in your site setup. If it works there but not in your usual browser, the issue is likely local.

What Usually Breaks The Disqus Embed

Wrong Shortname Or Broken Embed Code

Disqus uses your forum shortname to know which comment system belongs to your site. If the shortname is missing, misspelled, or pasted into old code, the thread won’t load at all. The official Universal Embed Code shows the required container and script order, including the disqus_thread element that must appear on the page.

This often happens after a redesign, a plugin swap, or a migration from HTTP to HTTPS. One small template edit can leave the script loading in the wrong spot or not loading on article pages at all.

Bad Page URL Or Identifier

Disqus maps comments to a page URL and, when set, a page identifier. If those values change across versions of the same post, Disqus may split one thread into two or attach comments to the wrong article. That’s why stable configuration matters. Disqus spells this out in its JavaScript configuration variables notes.

A classic mess shows up after permalink edits, category changes, translated pages, or cached pages that print old values. The page still loads, yet the comments look wrong. That points to URL or identifier drift, not a server outage.

Comments Disabled In The CMS

On WordPress and similar systems, Disqus can’t show where comments are turned off at the post level. If your theme or plugin hides the native comment template, or the post has comments closed, Disqus may appear dead when the real issue sits in the CMS settings.

This is one of those fixes that feels too plain to be the answer. Still, it catches a lot of people after bulk edits, imports, or template updates.

Browser Privacy Blocks

Some visitors can read comments but can’t stay logged in, can’t post, or see the box reload again and again. In many cases, strict privacy settings, blocked cookies, ad blockers, DNS filters, or script-blocking extensions are the cause. Disqus says basic posting does not require third-party cookies in every case, yet some browsers need them to keep users signed in across pages. Their cookie documentation lays that out clearly.

If the thread appears in one browser and fails in another, this is where to look first.

Checks That Fix Most Cases In Under Fifteen Minutes

1. Load One Post In A Clean Browser Session

Use a private window. Turn off extensions. Open one article that should have comments. If Disqus loads there, your base embed is probably fine, and your normal browser setup is the thing to fix.

2. View The Page Source

Search for disqus_thread and your shortname. If neither appears, the embed is not being printed on the page. If both appear but the thread stays blank, the script may be blocked or the template may be feeding bad page data.

3. Check The Page URL You Want Disqus To Use

If your article can load with tracking parameters, old category paths, or both HTTP and HTTPS, you can end up with split discussions. Pick one final URL and keep it stable. That alone fixes a surprising number of “missing comments” cases.

4. Confirm Comments Are Open In Your CMS

For WordPress users, check both the site-wide discussion settings and the post itself. A closed post can make Disqus look broken when it’s only following the post’s comment status.

5. Test On Another Network

Some office, school, or filtered home networks block scripts, trackers, or comment platforms. If the thread works on mobile data and fails on Wi-Fi, the network is the clue.

Fixes For Site Owners Who Control The Code

Use Stable Configuration Values

Set the page URL and page identifier in a way that stays fixed even if you edit titles later. The page title can change. The identifier should not. If you run a custom build, make sure cached pages are not printing stale values from another article.

Watch For Theme And SPA Issues

Single-page apps, infinite scroll layouts, and AJAX page loads can break Disqus if the script is loaded once and never reset when content changes. In those setups, you need the thread to reload with the fresh page data each time a new article is shown.

Theme changes can create the same headache. Desktop templates may include the thread while mobile templates leave it out. One layout file can make the desktop version look fine while mobile looks dead.

Check The Browser Console

Console errors can point you straight to the issue: blocked scripts, duplicate function calls, malformed JavaScript, or mixed asset loading. If another script crashes before Disqus runs, the comments can fail even when the embed code itself is fine.

Fixes For Readers Who Just Want The Comments To Load

If you’re not the site owner, your list is shorter. The good news is that the cause is often local, and that means you can fix it yourself.

• Refresh the page in a private window.
• Turn off ad blockers, privacy extensions, and script blockers for that site.
• Clear cached files and cookies for the site.
• Try another browser.
• Switch from Wi-Fi to mobile data, or the other way around.
• Update the browser if it’s old.

If none of that changes anything, the problem is probably on the publisher’s side. At that point, there isn’t much a reader can do beyond reporting the broken page.

When The Problem Is Not Disqus At All

Sometimes the comment system gets blamed for a page that is slow, broken, or half-loaded for other reasons. A bad CDN rule, a script conflict from a consent banner, stale full-page cache, or a plugin error can stop the page before Disqus even gets a chance to render.

That’s why it helps to look at the whole page, not just the comment box. If images are broken, buttons don’t work, or other scripts are failing, the root cause may sit outside Disqus.

What To Do If You Want A Clean, Lasting Fix

Start by separating browser trouble from site trouble. Then verify the shortname, the embed container, the page URL, and the identifier. After that, check whether comments are open in your CMS and whether privacy tools or network filters are blocking scripts. In most cases, one of those checks will expose the break.

That’s the real pattern behind “Disqus not working.” It’s usually not one mystery bug. It’s a small mismatch between how your page loads, how your URLs are defined, and how the browser handles cookies and scripts.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback