8 Problem Types Covered
All Major Browsers
VPN & Cache Fixes
OSCA Contact Included
How Do You Fix Missouri CaseNet When It Is Not Working?
Missouri CaseNet fails due to 8 common causes: active maintenance window (1:00 a.m.–6:00 a.m. CST weekdays and all weekend), disabled JavaScript, an active VPN or proxy, corrupted browser cache, an unsupported browser, a pop-up blocker preventing PDFs, incorrect court selection in search, or a case that is sealed or not in MCAP. Each cause has a specific fix identified in this guide.
Checking Missouri CaseNet status…
8Common failure causes
5 hrsDaily maintenance window
4Major browsers supported
7Case-not-found reasons
4Steps to clear cache
What Is Your Missouri CaseNet Problem? (Select to Jump to the Fix)
Select the problem type below to jump directly to the fix. Missouri CaseNet errors fall into 8 categories — not loading, case not found, browser issues, VPN block, maintenance window, document/PDF errors, login failures, and mobile access problems. Each category has a specific root cause and a targeted resolution.
🚫 CaseNet Not Loading — 5 Causes and Fixes
Most likely cause: CaseNet is within its daily maintenance window or an active VPN is blocking courts.mo.gov.
- Check the maintenance window firstMissouri CaseNet is offline every weekday from 1:00 a.m. to 6:00 a.m. CST and all day Saturday and Sunday. Check the real-time status widget at the top of this page — if CaseNet is currently offline for maintenance, wait until 6:00 a.m. CST Monday–Friday and try again.
- Check the OSCA System Unavailability LogOSCA publishes all scheduled and emergency outages at courts.mo.gov — System Unavailability Log. Review entries for the current date before troubleshooting further.
- Disable any active VPN or proxyCorporate VPNs, school network proxies, and some VPN services block access to courts.mo.gov by routing traffic through IP ranges that OSCA’s infrastructure rejects. Disconnect the VPN completely, then navigate directly to
courts.mo.gov/cnet/welcome.do. - Clear browser cache and cookiesCorrupted cache files prevent the CaseNet interface from loading correctly — symptoms include a blank white page, a partial page with broken layout, or a page that loads endlessly without completing. Use the browser-specific cache clearing steps in the Cache Clearing Guide section below.
- Enable JavaScript and allow cookies from courts.mo.govMissouri CaseNet requires JavaScript to render its interface and requires cookies to maintain session state. Both settings must be enabled. Access browser settings (Settings → Privacy/Security → Site Settings) and confirm courts.mo.gov is not blocked.
🔍 Case Not Found — 7 Causes and Fixes
Most likely cause: Name spelling mismatch or wrong court selected in the dropdown.
| # | Cause | Fix |
|---|---|---|
| 1 | Name entered does not match the clerk’s entry exactly | Try last name only with 2–3 characters — no first name — to return all variations. Enable Include Alias Information. Try alternate spellings (Smith/Smyth, Johnson/Johnston). |
| 2 | Fewer than 2 characters entered in Last Name field | Missouri CaseNet requires a minimum of 2 characters in the Last Name field. Entering 1 character or leaving it blank returns zero results. |
| 3 | Wrong court selected in the dropdown | Deselect any specific court and choose All Courts for a statewide search. A case filed in Jackson County does not appear in a St. Louis County circuit-specific search. |
| 4 | Case is sealed, confidential, or a juvenile record | Sealed cases, cases where the defendant was a minor (not certified as adult), and cases under court-imposed confidentiality orders do not appear in any CaseNet public search — this is by statute, not a search error. |
| 5 | Court does not use MCAP software | Not all Missouri courts use the Missouri Court Automation Program. If the court where the case was filed has not joined MCAP, its records do not appear in CaseNet. Contact the circuit clerk directly for those counties. |
| 6 | CaseNet is within its offline maintenance window | CaseNet returns no results during its offline window (1:00 a.m.–6:00 a.m. CST weekdays; all weekend). A maintenance-window search that returns zero results is normal — not a “case not found” error. |
| 7 | Case predates the court’s MCAP implementation | Very old cases (some pre-1990s, some pre-2000s depending on the county) were not entered into MCAP when courts joined the system. Contact the circuit court clerk and request the paper file or microfilm record. |
💡 Search the Missouri CaseNet Judgment Index Search as a cross-check, if the Litigant Name Search returns no results — judgments are indexed separately and may surface cases that don’t appear in the standard party search.
🌐 Browser Errors — Compatibility Requirements
Most likely cause: Internet Explorer (any version) or a browser with JavaScript disabled, cookies blocked, or outdated TLS support.
| Browser | Compatibility | Known Issues |
|---|---|---|
| Google Chrome (latest) | ✓ Fully supported | None. Chrome is the recommended browser for Missouri CaseNet. |
| Mozilla Firefox (latest) | ✓ Fully supported | None. Firefox ESR (Extended Support Release) also supported. |
| Microsoft Edge (Chromium, v79+) | ✓ Fully supported | None. Edge replaced Internet Explorer as the default Windows browser in 2020. |
| Apple Safari (v14+ on macOS/iOS) | ✓ Supported | Safari below version 14 may display PDF document rendering errors. Update to Safari 14+ to resolve. |
| Internet Explorer 11 | ✗ Not supported | Microsoft ended IE11 support on June 15, 2022. Courts.mo.gov no longer guarantees IE11 compatibility. Pages display broken layout or fail to load. Use Chrome, Firefox, or Edge instead. |
| Internet Explorer 10 or earlier | ✗ Not supported | TLS 1.2 support requires IE11 minimum. IE10 and earlier cannot establish a secure connection to courts.mo.gov. |
| Opera (Chromium-based) | ⚠ Generally works | Opera uses the Chromium engine — CaseNet functions, but Opera is not officially tested by OSCA. Use Chrome or Firefox for guaranteed compatibility. |
| Brave Browser | ⚠ May require settings adjustment | Brave’s aggressive fingerprint protection and script blocking can interfere with CaseNet’s session management. Disable Brave Shields for courts.mo.gov. |
Browser Requirements for Missouri CaseNet — 3 Technical Prerequisites
- JavaScript enabledMissouri CaseNet requires JavaScript to render the search interface, process form submissions, and display case records. Confirm JavaScript is enabled: Chrome → Settings → Privacy and Security → Site Settings → JavaScript → Allow. Firefox → Options → Privacy & Security → confirm JavaScript is not disabled via about:config.
- Cookies allowed from courts.mo.govCaseNet uses session cookies to maintain your search state between pages. Third-party cookie blocking does not affect courts.mo.gov (it is a first-party session cookie), but if courts.mo.gov is explicitly blocked in your browser’s cookie exceptions list, remove that exception.
- TLS 1.2 or higher supportedCourts.mo.gov enforces TLS 1.2 minimum for all connections. All modern browsers (Chrome 30+, Firefox 27+, Safari 7+, Edge all versions) support TLS 1.2. If you receive an “SSL connection error” or “Secure connection failed” message, update your browser — it is running a version that predates TLS 1.2 support.
🔒 VPN / Network Block — Why CaseNet Is Blocked on Your Network
Most likely cause: Corporate VPN, institutional network firewall, or university/library network that restricts government website access.
Missouri CaseNet at courts.mo.gov is blocked on 4 network types that commonly restrict external government sites: corporate VPN tunnels, university and college campus networks, K–12 school district networks, and some public library Wi-Fi networks. The block is applied at the network level by the employer, institution, or ISP — not by OSCA or Missouri CaseNet itself.
| Network Type | Symptom | Fix |
|---|---|---|
| Corporate VPN (work network) | courts.mo.gov times out or returns “This site can’t be reached” only when VPN is connected | Disconnect the VPN and access CaseNet from your standard internet connection. If VPN is required for work access, use a personal device on a home or mobile data connection. |
| Proxy server (IT-managed network) | Browser shows a “Proxy Authentication Required” or “Access Denied” page when navigating to courts.mo.gov | Contact your IT administrator and request that courts.mo.gov be added to the proxy whitelist. OSCA’s infrastructure serves public government records and qualifies for whitelist exceptions in most institutional policies. |
| Consumer VPN service (NordVPN, ExpressVPN, etc.) | CaseNet loads the main page but search results do not return, or the page loops on loading | Disable the VPN for the courts.mo.gov domain, or pause the VPN entirely and access CaseNet directly. Some VPN exit nodes are flagged by courts.mo.gov’s hosting infrastructure for suspicious traffic patterns. |
| Public Wi-Fi (library, coffee shop) | CaseNet loads but displays a captive portal redirect or “Connection Not Private” certificate warning | Complete the public Wi-Fi portal login (accept terms on the captive portal page), then navigate to CaseNet. If a certificate warning appears, confirm the URL is exactly courts.mo.gov — not a misspelled lookalike domain. |
🛠 Missouri CaseNet Maintenance Schedule — When the System Is Offline
Missouri CaseNet is offline on a fixed weekly schedule and during announced emergency maintenance windows.
| Day | Availability | Offline Window |
|---|---|---|
| Monday | ✔ Online | 1:00 a.m.–6:00 a.m. CST (5-hour daily maintenance) |
| Tuesday | ✔ Online | 1:00 a.m.–6:00 a.m. CST |
| Wednesday | ✔ Online | 1:00 a.m.–6:00 a.m. CST |
| Thursday | ✔ Online | 1:00 a.m.–6:00 a.m. CST |
| Friday | ✔ Online | 1:00 a.m.–6:00 a.m. CST |
| Saturday | ✖ Offline | All day — full 24-hour maintenance |
| Sunday | ✖ Offline | All day — full 24-hour maintenance |
OSCA also takes Missouri CaseNet offline on Missouri state holidays, including New Year’s Day, Martin Luther King Jr. Day, Presidents’ Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day. Planned emergency maintenance (system upgrades, security patches) is published in advance at courts.mo.gov — System Unavailability Log.
📄 Court Documents Not Opening — 4 Causes and Fixes
Most likely cause: Document filed before July 1, 2023 (not available online) or a pop-up blocker preventing the PDF viewer from opening.
- Confirm the document was filed after July 1, 2023Missouri CaseNet’s Remote Public Access program launched on July 1, 2023. Only documents filed on or after that date are viewable online. Check the docket entry date — if it is before July 1, 2023, the document does not have an online link regardless of browser or settings. Visit the courthouse’s public access terminal to view the document.
- Disable the pop-up blocker for courts.mo.govCaseNet opens PDF documents in a new browser tab or pop-up window. Pop-up blockers prevent this. Allow pop-ups from courts.mo.gov: Chrome → Settings → Privacy and Security → Site Settings → Pop-ups and Redirects → Add courts.mo.gov as an allowed site. Firefox → Options → Privacy & Security → Block Pop-up Windows → Exceptions → add courts.mo.gov.
- Ensure a PDF viewer is active in the browserCaseNet delivers court documents as PDF files. All modern browsers (Chrome, Firefox, Edge, Safari) include built-in PDF viewers that activate automatically. If the PDF fails to render, open Adobe Acrobat Reader, set it as the default PDF viewer, and retry the document link.
- Check whether the document is sealed or restrictedEven for post-July 2023 documents, some filings are restricted: protective orders, sealed exhibits, minor identifying information, and redacted financial documents. A docket entry with no link for a post-July 2023 filing confirms the document is restricted — it is not a browser error.
🔑 CaseNet Login Not Working — 5 Specific Scenarios
Note: Missouri CaseNet login is required only for eFiling, Track This Case, and Manage My Case — not for any public search function. All 5 search methods work without any login.
| Scenario | Cause | Fix |
|---|---|---|
| Wrong email/password | Credentials entered incorrectly | Click Forgot Password on the login page → enter registered email → follow the reset link. Password is case-sensitive. |
| Account locked | Multiple consecutive failed login attempts trigger a temporary lock | Wait 30 minutes for the automatic lock to expire, then attempt login again. Repeated locks indicate the saved password in your browser is outdated — update it after a successful reset. |
| Registration email not received | New account registration email went to spam, or email provider blocked courts.mo.gov | Check the spam/junk folder first. Whitelist @courts.mo.gov in your email provider. Wait 1 hour — OSCA’s email system may queue during peak registration periods. If still not received after 1 hour, contact OSCA Help Desk. |
| Forgot registered email address | Account was created with an email address no longer in use | Click Forgot Username on the login page and try all email addresses you may have used at registration. If none succeed, contact OSCA Help Desk with your full name and account details. |
| eFiling login fails despite valid My Account | eFiling uses the MoCourts eFiling portal — a separate system from the CaseNet My Account | eFiling registration is separate from a standard CaseNet My Account. Contact the Missouri Courts eFiling Help Desk at (573) 526-0062 for eFiling registration issues. A standard CaseNet account login does not grant eFiling access. |
📱 Mobile Access Issues — 4 Common Problems and Fixes
Missouri CaseNet functions on mobile browsers — no official app exists. OSCA has not optimized courts.mo.gov for mobile viewports, so the desktop layout renders on phones, requiring horizontal scrolling on small screens.
| Issue | Fix |
|---|---|
| Page is cut off on the right side (horizontal overflow) | Enable Desktop Site mode in your mobile browser to trigger the full desktop layout: Chrome mobile → Menu (⋮) → Request Desktop Site. Safari iOS → Address bar → “aA” icon → Request Desktop Website. |
| Touch targets are too small to tap accurately | Pinch to zoom in on the search form fields. Courts.mo.gov does not scale to mobile touch target sizes. A desktop-class tablet (iPad, Android tablet) provides a better experience than a phone screen for CaseNet searches. |
| PDF documents fail to open on mobile | iOS Safari: tap the PDF link → long-press → Open in New Tab. Android Chrome: tap the PDF link → it opens in Chrome’s built-in PDF viewer. If the PDF link produces no response, confirm pop-ups are allowed for courts.mo.gov in mobile browser settings. |
| Login session expires quickly on mobile | Mobile browsers in low-power mode and some iOS power management settings terminate background tabs, ending the CaseNet session. Disable Low Power Mode for the session, or keep the CaseNet tab actively in the foreground while working. |
How Do You Clear Browser Cache to Fix Missouri CaseNet?
Clearing browser cache removes corrupted or outdated page files that prevent Missouri CaseNet from loading correctly. The cache clearing process requires 4 steps in any browser: open Settings, navigate to Privacy or History, select cached files and cookies, and confirm the deletion. After clearing, close all browser tabs and navigate directly to
courts.mo.gov/cnet/welcome.do.Clear Cache in Google Chrome — 4 Steps
- Open Clear Browsing DataPress
Ctrl + Shift + Delete(Windows/Linux) orCmd + Shift + Delete(Mac). This keyboard shortcut opens the Clear Browsing Data dialog directly — no menu navigation required. - Select “All time” as the time rangeChange the Time Range dropdown from “Last hour” to All time — this ensures all cached CaseNet files are removed, not just recent ones.
- Check “Cached images and files” and “Cookies and other site data”Enable both checkboxes. Cached images and files removes stored page assets. Cookies removes session data that may be corrupted from a previous CaseNet session.
- Click “Clear data” and restart ChromeClick the blue Clear data button. Close Chrome entirely (all windows), reopen it, and navigate to
courts.mo.gov/cnet/welcome.do.
Clear Cache in Mozilla Firefox — 4 Steps
- Open Clear Data via keyboard shortcutPress
Ctrl + Shift + Delete(Windows/Linux) orCmd + Shift + Delete(Mac) to open Firefox’s Clear All History dialog. - Set the time range to “Everything”Change the dropdown from “Last Hour” to Everything to clear all cached files regardless of when they were stored.
- Check “Cache” and “Cookies”Enable the Cache checkbox (removes stored page files) and the Cookies and Site Data checkbox (removes session tokens that may be corrupted).
- Click “Clear Now” and restart FirefoxClick Clear Now. Close Firefox completely, reopen it, and navigate directly to courts.mo.gov/cnet/welcome.do.
Clear Cache in Apple Safari (macOS and iOS) — 4 Steps
- macOS: Open Safari → Develop menu → Empty CachesIn Safari on macOS, click the Develop menu in the menu bar → select Empty Caches. If the Develop menu is not visible, enable it: Safari → Preferences → Advanced → check “Show Develop menu in menu bar.”
- macOS: Clear cookies via Preferences → PrivacySafari → Preferences (Cmd+,) → Privacy tab → Manage Website Data → search for “courts.mo.gov” → Remove. Or select Remove All to clear all cookies.
- iOS (iPhone/iPad): Settings → Safari → Clear History and Website DataOpen the iOS Settings app (not Safari) → scroll to Safari → tap Clear History and Website Data → confirm. This clears cache and cookies for all sites.
- Restart Safari and navigate to courts.mo.govClose Safari completely (swipe away from app switcher on iOS), reopen it, and navigate to
courts.mo.gov/cnet/welcome.do.
Clear Cache in Microsoft Edge — 4 Steps
- Open Clear Browsing Data via keyboard shortcutPress
Ctrl + Shift + Deleteto open Edge’s Clear Browsing Data panel. Edge’s shortcut is identical to Chrome — both are Chromium-based browsers. - Set the time range to “All time”Change the Time Range to All time to remove all cached CaseNet assets, not just recent session data.
- Check “Cached images and files” and “Cookies and other site data”Enable both checkboxes to remove stored page assets and session cookies from previous CaseNet visits.
- Click “Clear now” and restart EdgeClick Clear now. Close all Edge windows, reopen Edge, and navigate to courts.mo.gov/cnet/welcome.do.
What Do Missouri CaseNet Error Messages Mean?
Missouri CaseNet displays 6 common error messages: “No Records Found,” “Service Unavailable,” “Session Expired,” “Access Denied,” “Connection Timed Out,” and the OSCA maintenance page. Each message identifies a different root cause — no records found is a search input error, session expired is an inactivity timeout, and service unavailable confirms the system is in its maintenance window.
⚠️ CaseNet Error Message Decoder
Enter an exact error message or error phrase you see in Missouri CaseNet to identify the cause and fix.
Try:
How Do You Contact OSCA When Missouri CaseNet Has a Persistent Error?
Contact the OSCA CaseNet Help Desk at courts.mo.gov for persistent CaseNet errors — the Help Desk operates Monday through Friday, 7:30 a.m. to 5:00 p.m. CST, excluding Missouri state holidays. Before contacting OSCA, confirm the System Unavailability Log shows no active outage and that the troubleshooting steps for your specific error type have been completed.
📞 OSCA CaseNet Help Desk — Contact Information
Help Desk Hours
Monday – Friday
7:30 a.m. – 5:00 p.m. CST Closed Missouri state holidays
7:30 a.m. – 5:00 p.m. CST Closed Missouri state holidays
eFiling Help Desk
(573) 526-0062
eFiling portal issues only — separate from CaseNet My Account
Information to Prepare Before Contacting OSCA Help Desk
Providing 4 pieces of information to the OSCA Help Desk reduces resolution time: the exact error message you received, the date and time of the error (including your time zone), the browser name and version number, and the specific case number or search terms you used when the error occurred. OSCA uses this information to replicate the error in their test environment.
What Are the 6 Best Practices to Prevent Missouri CaseNet Errors?
Missouri CaseNet errors are prevented by 6 practices: always accessing during operating hours (Mon–Fri 6:00 a.m.–1:00 a.m. CST), using a supported browser (Chrome, Firefox, or Edge), disabling VPN before accessing courts.mo.gov, clearing browser cache monthly, allowing pop-ups from courts.mo.gov, and bookmarking the correct URL
courts.mo.gov/cnet/welcome.do rather than typing it manually.| # | Best Practice | Error It Prevents |
|---|---|---|
| 1 | Access only during operating hours — Mon–Fri 6:00 a.m.–1:00 a.m. CST | Prevents “Service Unavailable” errors caused by accessing during the 1:00 a.m.–6:00 a.m. maintenance window or over weekends |
| 2 | Use Chrome, Firefox, or Edge — avoid Internet Explorer entirely | Prevents JavaScript errors, TLS failures, and page rendering errors caused by unsupported browser versions |
| 3 | Disable VPN before navigating to courts.mo.gov | Prevents connection timeouts and access denials caused by VPN IP blocks or proxy restrictions |
| 4 | Clear browser cache monthly or after any CaseNet loading failure | Prevents white-screen, broken-layout, and infinite-loading errors caused by corrupted cached page assets |
| 5 | Allow pop-ups from courts.mo.gov in browser settings | Prevents PDF court documents from failing to open when clicking document links in docket entries |
| 6 | Bookmark the exact URL courts.mo.gov/cnet/welcome.do | Prevents accidental navigation to unofficial or misspelled CaseNet lookalike domains that display errors or phishing pages |
Frequently Asked Questions — Missouri CaseNet Troubleshooting
The 10 most common Missouri CaseNet troubleshooting questions address why search returns no results on weekends, how long maintenance lasts, whether CaseNet works on iPhone, what “session expired” means, why cases disappear from results, whether CaseNet has a mobile app, what causes the spinning loading screen, how to report a bug to OSCA, why Pay By Web fails, and how to confirm CaseNet is actually down versus a local network issue.
Why does Missouri CaseNet return zero results on weekends?
Missouri CaseNet is completely offline every Saturday and Sunday — all day, not just during certain hours. Any search attempted on a Saturday or Sunday returns zero results or a service unavailable message because the MCAP database is not running. This is normal scheduled maintenance, not a system error. The first available search window each week begins Monday at 6:00 a.m. CST. OSCA’s MCAP system conducts full database maintenance, backup, and indexing operations during the 48-hour weekend window.
Why does the Missouri CaseNet page just spin and never load?
An endlessly spinning loading screen on Missouri CaseNet results from 3 causes: (1) an active VPN routing the connection through a blocked IP range — the server receives the request but never completes the response; (2) corrupted session cookies from a previous CaseNet visit that prevent the server from establishing a clean session; or (3) a browser extension (ad blocker, script blocker, or privacy extension) blocking one of CaseNet’s required JavaScript files. Fix in sequence: (1) disable the VPN, (2) clear cache and cookies for courts.mo.gov, (3) open CaseNet in a private/incognito window — this loads with all extensions disabled and confirms whether an extension is the cause.
Does Missouri CaseNet have an official mobile app?
No official Missouri CaseNet mobile app exists as of 2026. The Office of State Courts Administrator (OSCA) has not released an iOS or Android application for CaseNet. Any app in the App Store or Google Play Store claiming to be “Missouri CaseNet” or “MO CaseNet” is a third-party application — not operated by OSCA or the Missouri Judicial Branch. The only official access point is the mobile browser at
courts.mo.gov/casenet. Chrome and Safari on iOS and Android both support all 5 CaseNet search methods and document viewing for post-July 2023 filings.What does “Session Expired” mean on Missouri CaseNet?
Session Expired means your CaseNet session was inactive for longer than the server’s timeout period — typically 15 to 30 minutes without submitting a form or clicking a search. Missouri CaseNet uses server-side session management: when your session expires, the server discards the session token and any in-progress search state. Fix: close the browser tab, open a new tab, navigate to
courts.mo.gov/cnet/welcome.do, and start the search from the beginning. If session expiration repeatedly interrupts multi-step searches (such as reviewing multiple cases), open each case in a new tab to keep the main session active.How do you confirm Missouri CaseNet is actually down versus a local problem?
Distinguish between a CaseNet system outage and a local network problem using 3 verification steps: (1) Check the OSCA System Unavailability Log — if OSCA posted an outage notification for the current time, the system is confirmed down; (2) Test from a different network — attempt access from a mobile data connection (4G/5G) rather than Wi-Fi. If courts.mo.gov loads on mobile data but not on Wi-Fi, the problem is your local network or ISP, not CaseNet; (3) Try from a different browser — if courts.mo.gov loads in Chrome but not in Firefox, a browser-specific cache or extension issue is the cause, not a system outage.
Why does a case appear in Missouri CaseNet one day and disappear the next?
A case that was visible and then disappeared from Missouri CaseNet results has 2 likely explanations: (1) Expungement was granted — if a court granted an expungement order under RSMo §610.140, OSCA removes the case from public CaseNet access within approximately 30 days of the order. The EXPU docket code appears briefly before removal. (2) The case was sealed by court order — a judge sealed the case record, restricting it from public access under Missouri Supreme Court Rule 109.05. A sealed case is not deleted — it is hidden from public access while remaining accessible to parties and their counsel. For either situation, search the Missouri CaseNet Judgment Index and Litigant Name Search for cross-confirmation before concluding the case was removed.
Why does Missouri CaseNet work on one computer but not another?
Missouri CaseNet functioning on one computer but failing on another points to 3 device-specific causes: (1) Browser version difference — the working computer runs Chrome or Firefox; the failing computer runs Internet Explorer 11 or an outdated browser that lacks TLS 1.2 support or modern JavaScript execution; (2) Network difference — the working computer connects through a home network; the failing computer connects through a corporate VPN or institutional proxy that blocks courts.mo.gov; (3) Browser extension conflict — a script blocker, ad blocker, or privacy extension installed on the failing computer blocks one of CaseNet’s required JavaScript files. Test in private/incognito mode on the failing computer — if CaseNet loads in incognito mode, a browser extension is causing the conflict. Disable extensions one at a time to identify which one.
Why does Missouri CaseNet Pay By Web not work?
Missouri CaseNet Pay By Web payment failures result from 4 causes: (1) the court where the case was filed does not participate in the Pay By Web program — not all 114 Missouri courts are enrolled, and the Pay By Web link only appears on case pages for participating courts; (2) the payment amount exceeds the court’s online payment limit — some Missouri courts cap online payments at specific dollar thresholds; (3) the credit or debit card issuer declined the transaction — contact your bank to confirm no international or government-site blocks are active on the card; (4) the payment session timed out — Pay By Web has its own session timeout, separate from CaseNet’s search session. If the Pay By Web link does not appear on your case page, the court does not participate. Contact the circuit court clerk directly for alternative payment methods (mail, in-person, phone).
How do you report a Missouri CaseNet bug or technical error to OSCA?
Report Missouri CaseNet technical errors to OSCA through the courts.mo.gov contact form. Include 4 pieces of information in the report: (1) the exact error message or behavior you observed (screenshot if possible), (2) the date and time of the error in CST, (3) the browser name and version number (open browser → Help → About to find the version), and (4) the specific URL you were on when the error occurred. For errors affecting a specific case record, include the case number. OSCA’s technical team reviews reports and posts resolution status in the System Unavailability Log for system-wide issues.
Why does Missouri CaseNet show an “Access Denied” error?
“Access Denied” on Missouri CaseNet appears in 3 specific situations: (1) VPN or proxy block — the most common cause. Courts.mo.gov actively blocks traffic from VPN exit nodes and certain proxy server IP ranges. Disable the VPN and retry. (2) Browser sending unusual request headers — security browsers (Tor Browser, hardened Firefox configurations, Brave with maximum shields) send request headers that courts.mo.gov’s security infrastructure classifies as suspicious, triggering an access denial at the server level. Use standard Chrome or Firefox without privacy hardening for CaseNet. (3) Attempting to access a restricted case or document — sealed cases, confidential records, and restricted documents return an “Access Denied” or “You do not have permission” message. This is not a technical error — the denial is intentional and correct.