1

I have been unable to view any article pages, user pages including my own, user talk pages including my own, and user logout… using Windows 10 Home in Chrome Browser. I switched to MS Edge as an anon user and it acted normal until I logged in.

Each error message is slightly different here are two examples:

Example 1: https://www.wikihow.com/Conduct-a-Workshop
MediaWiki internal error.

Original exception: [a40b892d853013abf06a1da8] 2020-02-27 15:14:41: Fatal exception of type “MWException”

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

Example 2:  https://www.wikihow.com/Prioritize-Your-Debts

MediaWiki internal error.

Original exception: [167ee958375e3c1048152d54] 2020-02-27 15:02:43: Fatal exception of type “MWException”

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

2

Hi @Zack , I’m so sorry to hear this! I’m not able to replicate these errors, but I’m going to check in with a dev to see if we can figure out what’s happening with your account. 

Would it be possible to clear the cache and cookies on your browser? This should log you out, so you could try logging in again and see if it continues. 

3

I am at the office and logged in on a coworker’s machine. Same results as soon as I log in. Windows 10 Pro / Chrome and MS Edge. Different machines, different network, same errors. I also cleared the cache & cookies on Chrome and logged in again. Same.

4

Seems this problem is back. I reported one a while back( forums.wikihow.com/discussion/28947/bug-receiving-error-patrolling-using-traditional-rc-not-rcp-tool#latest ), then just the other day, someone else reported a new sighting of the same issue ( forums.wikihow.com/discussion/29383/internal-error-v-2#latest ) now this! Seems that this is a deeper issue. 

5

Hi @Byankno1 , thanks for your note but it appears these are separate issues. There was a link that was causing some issues in Zack’s account, which have now been remedied.