Guild Wars 2 Wiki:Reporting wiki bugs

Please report all bugs found on Guild Wars 2 Wiki here. This page is NOT for reporting game bugs, those should be reported at the official forums.

---

Resolved issues

---

• 2007-2010
• 2011-2012
• 2012-2013
• 2013-2014
• 2014-2015
• 2015-2016
• 2016-2017
• 2017-2018
• 2018-2019
• 2020
• 2021
• 2022
• 2023-2024
• 2025

This page is used to report bugs with the wiki, this does NOT cover in-game issues.

• If you are experiencing an in-game bug or issue that requires technical support, check the Guild Wars 2 official forums.
• If you are experiencing difficulties getting past a specific part of the game, please use the "Search" box on the left to find the specific quest, mission, or region that you are finding difficult. You can review any tips on that page, and discuss it on corresponding talk page if more help is desired.
• If you have a problem with contents of a wiki page, use the associated talk page.

Please review existing bug reports before creating a new one, these will be listed below. If you add a bug not related to the wiki (such as a bug in the game itself), the report may be removed with no actions taken.

When reporting a new bug, be sure to provide a description of the problem, your wiki username, any error message received, and any additional comments that may help someone reproduce and troubleshoot the suspected bug.

Key: = Solved, = Mitigated, = Unsolved, = Not a bug/Unconfirmed

Semantic query: Printout skips data

See /archive 12#Semantic query: Printout skips data for full description.

Long term issue. Awaits https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/5036 which didn't make it into the release of SMW 4.0.0.

Mitigated by edits such as this one. -Chieftain Alex 12:47, 11 September 2022 (UTC)

Still happening as reported on Template talk:Trait list#Traits not displaying some elite specs correctly. -Chieftain Alex 17:35, 4 April 2023 (UTC)

This fix has also been excluded from SMW 5.0.0. -Chieftain Alex 16:55, 14 March 2026 (UTC)

Empty or incomplete SMW queries

See /archive 13#Empty or incomplete SMW queries for full description.

Basically requires additional purge activities to rebuild pages after wiki database updates. -Chieftain Alex 22:27, 14 February 2025 (UTC)

"|+order=" not sorting as expected (SMW Records)

See "|+order=" not sorting as expected (SMW Records)

Bugs related to sorting of the record SMW data type. -Chieftain Alex 22:27, 14 February 2025 (UTC)

Reference previews

Reference previews only appear when logged out, but not while logged in. And, not sure if related, but in case it helps: Attempting to turn of the media viewer using the gear shown when viewing a file while logged in doesn't actually turn of the media viewer (nor change the acompaning setting for it the preference settings (Which is where the gear found in Page previews goes to (Special:Preferences#mw-prefsection-rendering) while logged in, while providing options to toggle Page previews and Reference previews individually instead while logged out.) accordingly). Nightsky (talk) 14:48, 3 May 2023 (UTC)

Checked, still broken as of MW 1.39.6 -Chieftain Alex 17:20, 13 April 2024 (UTC)

Still broken as of today. ~Sime 15:13, 6 February 2026 (UTC)

HTTP errors (various)

403 errors

These errors turned out to be due to server firewall rules vs a spam campaign targeting the varnish servers. -Chieftain Alex 22:17, 14 February 2025 (UTC)

Just got this error again after my edited on User:Tery3065/sandbox5 (using SMW to pull the objects images using Has appearance property), so my IP got blocked? After resetting my network, it works. --𝙏ᴇʀʏ 17:25, 17 February 2025 (UTC)

Actually, your IP address accidentally got caught in with a few others I'd seen sending malicious requests to the wikis earlier today. I saw your post earlier and removed your IP from the blocklist but forgot to respond here. Justin Lloyd (talk) 23:06, 17 February 2025 (UTC)

Recently uploaded images not loading

Same issue as #403 errors above. -Chieftain Alex 22:17, 14 February 2025 (UTC)

Pagename with semicolon causing 403

Trying to access pages containing semicolon (e.g. Achievement Eligibility: In Tatters; Not Shattered ) results in a 403 error. The same page is accessible via long URL ( https://wiki.gw2.org.cn/index.php?title=Achievement_Eligibility%3A_In_Tatters%3B_Not_Shattered ). --BryghtShadow (talk) 16:13, 9 May 2025 (UTC)

Turned out to be a misconfigured firewall rule. -Chieftain Alex 22:34, 19 July 2025 (UTC)

504 gateway errors

These errors are being investigated by ArenaNet, the cause is currently unknown. -Chieftain Alex 22:17, 14 February 2025 (UTC)

Appears to be caused by an "empty" SMW query (0 results) with 7 sortkeys, on Template:Trait list, which is effectively called on every single trait/skill page on the wiki. For the moment this has been edited to remove some sortkeys (anything fewer than 7 is fine apparently). I will leave this at unresolved red status until we've had time to review. -Chieftain Alex 00:00, 15 February 2025 (UTC)

The Shadowstep (mechanic) was still inacessible this morning, so looked further.

Ended up editing Template:Skill list (checked for type/effect being equal to "+", i.e. all results) and Template:Related skills list (removed couple of marginally unnecessary types, this change may not be required due to the amendment to skill list, which is called by this template).

My guess as to the root cause is that our SMW properties have finally gotten big enough that its an issue to make certain queries, particularly greedy ones with "+" or where the results are being sorted many times over. -Chieftain Alex 12:45, 15 February 2025 (UTC)

Marking as resolved, not seen in a while now. -Chieftain Alex 11:56, 16 March 2025 (UTC)

Have been getting 504 Gateway Time-out when trying to load Guaranteed_Wardrobe_Unlock/Weapon_Skins for the past couple of days. - Gumbolia (talk) 20:35, 20 September 2025 (UTC)

This page has probably grown too large and is failing to load as a result, needs to be split up into smaller pages. --ItVictor (talk) 00:10, 21 September 2025 (UTC)

That page is still crazy big and its amazing it works at all. -Chieftain Alex 17:26, 14 March 2026 (UTC)

Now seems to be fixed for Condition and Boon pages. Originally: I'm getting 504 errors on every page about Conditions (Condition overview page and also more specific pages like Burning, Slow, etc.) and also all of the specific boon pages (Regen, Quickness, etc.). Happens on both PC and mobile. --Tilden (talk) 16:08, 25 September 2025 (UTC)

Was fixed on same day by Medyro reducing the query depth with this new parameter. -Chieftain Alex 17:26, 14 March 2026 (UTC)

I've been seeing 504 errors when trying to load Release/Features for the last couple of weeks. Chugs for a long time and then times out. --Blackjackkent 04:30, 3 October 2025 (UTC)

I've chopped that page from 25 to 10 results and fixed up the way the further results link is handled, such that it no longer throws 403 errors. -Chieftain Alex 17:26, 14 March 2026 (UTC)

403 Forbidden

Whehter using /wiki ingame, clicking on a link, or trying to write here, I constantly get this error. After 10-20 seconds the page finally loads, but this is beyond annoying--91.14.39.155 19:57, 30 October 2025 (UTC)

Being investigated on ArenaNet's side, thanks for the report. -Chieftain Alex 20:30, 30 October 2025 (UTC)

More and more pages show Error 203

→ moved from Talk:Main Page/editcopy

I was linking an item via "/wiki Polyluminescent Undulating Refractor (Black)" and got this error, circumventing it by going to the main page for the refractors and selecting the black version. (had this error a few times over the last 2-3 weeks already but had other stuff to do to care much) After this, I tried to find a way to post it somewhere to inform people who are registered (I contributed a lot over the years but still don't feel like registering) so they can take a look into the problem and hopefully solve it but got the same error on some discussion pages. Sadly this page here looks like it's some kind of step child that only gets attention once every few months. I hope I am wrong with that assessment though :P Thanks in advance for your time.

Weirdest part that I just found out by doublechecking the item link I added here: Now it works by rightclick here as well as a wiki link from the game itself. Is this because of some cache that remembers I went there already? (176.6.56.22 15:13, 2 November 2025 (UTC))

This page and discussion are for changes to the Main page. What you want is to report the bug to Guild Wars 2 Wiki:Reporting wiki bugs. ~Sime 15:24, 2 November 2025 (UTC)

What links here: 403 Forbidden

Apparently this bug presents on any Wiki page (Tools, What links here), for example, right here. If it is an intended limitation for unlogged users, it would be better to clearly inform about this. Otherwise, please fix. --185.115.4.151 14:31, 14 March 2026 (UTC)

Certain special pages are frequently being subjected to crazy volumes of traffic (basically DDOS by AI web crawlers) which trip the firewall rule + lockout anon users from Special:WhatLinksHere + Special:RelatedChanges. We could hide the links from the user interface when logged out, but that probably isn't the right answer... I'll have a chat with the other admins + the anet team and see what functions currently get 403'd during a DDOS event. -Chieftain Alex 16:32, 14 March 2026 (UTC)

Thank you for explanation! I am not very good in network security, but if such block is a way to prevent the malicious attempts to get access to as many Wiki pages as possible, I can wait as long as need. But if there are another ways to stop such spam, please take them into account as well. Maybe like Cloudflare does or something else. Anyway, blocking the bots to preserve the main Wiki pages and their availability to users is a priority. --185.70.52.196 18:27, 14 March 2026 (UTC)

Chatlinks generating with wrong or different codes

Been reported a few times in recent weeks for various pages, collating these in one place

• Master Diver - discord report 2026-04-24: ""Valslake Waypoint" was changing to the "Slough of Despond Waypoint" on click to copy. several other were exhibiting the same behavior"
• Radiance of the Sun God - 2026-05-03 - discord report "this page is behaving weirdly, at first it displays the correct waypoint link for the waypoints but once you click on it, it copies a different waypoint, for example the "ireko tradecamp waypoint" links actually link to the crucible of eternity waypoint [&BEIFAAA=] when you click on it rather than the correct waypoint [&BAoAAAA=]" ... Ireko Tradecamp Waypoint showing [&BAoAAAA=] but then showing [&BEIFAAA=] when clicked on ... "same waypoint but different waypoints once you click on them"
• Talk:World_boss#Feedback_2026/05/11 - 2026-05-11 - "Muridian Waypoint link issue on World Boss page. Shows correct one [&BEcAAAA=] but when clicked to copy shows wrong one [&BPcAAAA=] (E becomes P) Solved: Refreshing browser's pinned tab helps"

-Chieftain Alex 16:33, 11 May 2026 (UTC)

This should now be fixed. The issue was occurring noticeably only on pages with enough chatlinks - this gave me an idea that it was a race condition; which turned out to be correct. Due to the number of invocations of the same small widget code being called, there was variable leakage (var) from one instance to another. I didn't really think this was possible, but now I see that it was. The widget has been updated to block scope "const"/"let" so should be resistant to this error now.

Thinking about extent of condition, this could affect any widgets used more than once on a page (more likely to see on lightweight ones imo) - I can't actually think of many. -Chieftain Alex 17:54, 11 May 2026 (UTC)