Last modified: 2006-04-27 17:05:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5688 - Untraceable block on meta
Untraceable block on meta
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-22 19:27 UTC by Nick Boalch
Modified: 2006-04-27 17:05 UTC (History)
0 users

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


Attachments

Description Nick Boalch 2006-04-22 19:27:06 UTC
The IP address 129.234.4.76 (pepys.dur.ac.uk, one of the proxy servers of the
University of Durham) is blocked from editing on meta, with the reason
'Auto-added for persistent vandalism; possible open proxy', and has been blocked
for at least 6 months.

The blocking admin is listed simply as '[[User:|]]' and the address does not
appear in the IP blocklist (see
<URL:http://meta.wikimedia.org/wiki/Special:Ipblocklist?action=search&limit=50&ip=129.234>).

(Filed here rather than in MediaWiki because it relates specifically to meta;
sorry if it should have gone under MediaWiki as a software issue.)
Comment 1 Nick Boalch 2006-04-22 19:28:24 UTC
Screenshot of block message: http://bylands.dur.ac.uk/~ngb/random/meta-block.png
Comment 2 Brion Vibber 2006-04-22 19:57:32 UTC
That was me with a manual mass-block.
Comment 3 Nick Boalch 2006-04-26 18:42:57 UTC
Thanks, but the problem still exists as of 2006-04-26 19:40 BST.
Comment 4 Brion Vibber 2006-04-27 17:05:08 UTC
I told you who and how. Your trace is done.

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


Navigation
Links