View Full Version : WIKI
Flowe
08-02-2024, 09:10 PM
Anyone know what happened to p99 wiki?
Rimitto
08-03-2024, 06:31 AM
red server
grims
08-03-2024, 07:49 AM
Anyone got a guide for whitelisting wiki so I dont have to click accept on every page?
Thank you kindly for your time and effort ahead of time
loramin
08-03-2024, 11:18 AM
The security cert expired, which it does every 13 months or so. Rogean needs to replace it with a fresh one.
Until he does, hackers could (hypothetically) intercept your Magelo updates, or other wiki edits. Your browser doesn't understand that, thinks your credit card is going to be stolen, and freaks out.
As a workaround some browsers might have ways to disable invalid https certificate warnings, but if they do they will be "secret" (eg. https://dev.to/moshe/a-secret-way-to-bypass-chrome-s-security-privacy-error-4h6i), because browsers really don't want peoples' credit cards getting stolen.
Rygar
08-03-2024, 02:09 PM
Maybe try archive.org in the meantime
Sadre Spinegnawer
08-03-2024, 04:40 PM
Now it links to www.groaningrannies.com
Swish
08-03-2024, 06:42 PM
http://web.archive.org - use an older version if it's a problem.
Wakanda
08-05-2024, 01:05 PM
lol it keeps telling me the page isnt safe for me to visit. is there a gofundme we can set up where we all donate or something??? like that wiki page is useful even on TLPs because its easier to navigate than ahllakahazam
loramin
08-05-2024, 01:18 PM
Change the URL: it currently says "http://...", but if you add an "s" ("https://...") it should fix it.
Most websites will see that you're on HTTP, and automatically forward you to HTTPS without you having to do anything. However, (presumably because Rogean doesn't have time to configure things properly, and doesn't trust anyone like myself to help) the wiki doesn't.
If Rogean ever does feel motivated, he literally just has to change one line of config: https://stackoverflow.com/questions/10997614/simplest-way-to-get-mediawiki-to-require-https-on-all-pages. But until he makes that one line change, we just have to deal with this confusion (and add the "s" ourselves).
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.