Why You're Seeing Error Pages on the Arkansas DOC Website (and What to Do)

Seeing an error page when you’re trying to find prison information is frustrating - especially when you’re in the middle of planning a visit, sending mail, or trying to understand programs. If an Arkansas DOC page is showing only the word “nginx,” it generally means the website isn’t serving the real page content right now. Below, you’ll see examples of pages where this was observed and a set of low-risk steps you can use to get what you need while the official page isn’t loading normally.

When checking Arkansas DOC webpages, some pages did not load their normal content and instead displayed only a single token: “nginx.” This behavior was observed on the Pine Bluff Unit facility page (https://doc.arkansas.gov/facilities/pine-bluff-unit), on an Inmate Programs page labeled “page 4” (https://doc.arkansas.gov/correction/inmates/inmate-programs-and-services/inmate-programs-page-4/), and on the Chief Deputy Director page (https://doc.arkansas.gov/correction/about-us/chief-deputy-director/). In each case, the page content shown was simply “nginx,” rather than the facility, program, or staff information you’d expect to see.

“Nginx” (pronounced like “engine-ex”) is the name of a common web server - basically, the software that helps a website deliver pages to your browser. When you see “nginx” by itself, it usually means you’re getting a bare server response instead of the real webpage. That can happen for a few different technical reasons, but the key takeaway for you is simple: the site isn’t delivering the content you’re looking for right now, even though the web address itself may still open.

The practical problem is that you can’t use those pages the way you normally would. If a facility page loads as “nginx,” you can’t read the facility details that families often rely on for planning and confirmation - like where to look for official updates or what information the DOC is currently posting for that location. If a programs-and-services page is doing the same thing, it can also block you from reading about inmate programs that might matter for questions about classes, eligibility, or what a loved one may have access to while incarcerated. In other words, even if only a handful of pages are affected, it can still interrupt the specific “I need this answer right now” tasks people are trying to complete.

1. Refresh once, then try again later - Sometimes this clears quickly. If not, step away and retry in 15–60 minutes.
2. Try a different browser or a private/incognito window - This helps rule out a bad cached copy, extensions, or a stuck session.
3. Switch networks if you can - If you’re on Wi‑Fi, try cellular data (or the other way around). It’s a simple way to see if the problem is local to one network.
4. Look for an archived copy of the page - A search engine’s cached result or the Internet Archive’s Wayback Machine may have a recent snapshot that includes the missing text.
5. Write down exactly what you need from the page - Make a short list (for example: visitation details, mailing rules, program description) so you don’t lose time once the site is back.
6. Document what you’re seeing - Save the exact URL, the date/time you checked, and a screenshot showing the “nginx” page. This makes it much easier to report and follow up.

Reporting

• ✓ The exact URL(s) that show only “nginx”
• ✓ A screenshot that clearly shows the “nginx” page
• ✓ The date and time you checked (include your time zone if you can)
• ✓ What device you used (phone or computer) and which browser (Chrome/Safari/Edge/Firefox)
• ✓ Whether it happens on more than one network (Wi‑Fi vs. cellular)
• ✓ What you already tried (refresh, private window, different browser)
• ✓ A short note on what information you were trying to access (facility details, inmate programs, staff page)
• ✓ If you already have an official Arkansas DOC contact method you trust, send the report there rather than posting personal details publicly

If you’re seeing “nginx,” plan on checking back periodically instead of repeatedly hammering the page - quick retries spaced out over the day are usually enough. Keep your screenshot and notes until you’ve confirmed the page is loading normally again, especially if your plans depend on something you were trying to verify. Once the site is back, re-check any details you pulled from an archived copy so you’re working from the current official information. There isn’t reliable public info here about how long a fix will take, so your best move is careful documentation and patient rechecks.