This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9549 - "External Checker not available" error
Summary: "External Checker not available" error
Status: RESOLVED FIXED
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: http://validator.w3.org/check?uri=htt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-18 05:19 UTC by Justin Scott
Modified: 2015-08-23 07:07 UTC (History)
2 users (show)

See Also:


Attachments

Description Justin Scott 2010-04-18 05:19:29 UTC
Since last night, when trying to validate a few different HTML5 pages, I always get the following error at the bottom:

External Checker not available
Checking the Document Type of this document requires the help of an external tool which was either not enabled in this validator, or is currently unavailable. Check in the validator's system configuration that HTML5 Validator is enabled and functional.

The error encountered was: 500 Can't connect to localhost:8888 (connect: Connection refused)

Example URL with the error: http://validator.w3.org/check?uri=http%3A%2F%2Fblog.fligtar.com
Comment 1 Michael[tm] Smith 2010-06-14 08:39:26 UTC
The HTML5 backend on the validator occasionally gets taken down and needs to be restarted. It could be that it was down when you tried. If you try again and find that you're having the same problem, please re-open this bug.
Comment 2 Paul d'Aoust 2011-07-28 17:44:12 UTC
The HTML5 validator seems to be down again; would you folks be willing to restart it?

Thanks!
Paul
Comment 3 Michael[tm] Smith 2011-10-26 07:07:03 UTC
(In reply to comment #2)
> The HTML5 validator seems to be down again; would you folks be willing to
> restart it?

We seem to not be having this problem as much as we did in the past. If/when you do find that it's down again, feel free to e-mail me directly to let me know -- mike@w3.org