Last modified: 2012-06-27 20:48:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39990, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37990 - Cannot forward error
Cannot forward error
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
Other other
: Unprioritized blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-27 17:17 UTC by Wttgrdnr3
Modified: 2012-06-27 20:48 UTC (History)
1 user (show)

See Also:
Web browser: Apple Safari
Mobile Platform: iOS
Assignee Huggle Beta Tester: ---


Attachments

Description Wttgrdnr3 2012-06-27 17:17:13 UTC
WIKIMEDIA FOUNDATION
Error
Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon. Please try again in a few minutes.

You may be able to get further information in the #wikipedia channel on the Freenode IRC network.

The Wikimedia Foundation is a non-profit organisation which hosts some of the most popular sites on the Internet, including Wikipedia. It has a constant need to purchase new hardware. If you would like to help, please donate.

If you report this error to the Wikimedia System Administrators, please include the details below.
Request: GET http://en.wikipedia.org/, from 10.64.0.133 via cp1014.eqiad.wmnet (squid/2.7.STABLE9) to ()
Error: ERR_CANNOT_FORWARD, errno [No Error] at Wed, 27 Jun 2012 17:06:11 GMT
Comment 1 Dereckson 2012-06-27 20:48:08 UTC
Good evening,

Thank you for your bug report.

You received this message as we had a network issue involving the different servers needed to deliver you page content.

We apologize for the incident, and can assure you we're continually monitoring and taking care of our network.

The situation now works again.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links