Changes

Jump to navigation Jump to search
2,858 bytes added ,  06:03, August 29, 2020
Line 1,056: Line 1,056:     
:::::::::I tried the first suggestion, but it didn't work. Regarding the second idea, it was somewhat confusing, and I'm not sure if I did it right, but it didn't work either. I'm just wondering though, why would such an error even occur in the first place? That type of problem never happened for me before the server problems that started showing up around four weeks ago. —[[User:Liberaltears|Liberaltears]]<sup>'''''[[User:Liberaltears/mail|May Dataclarifier be well!]] | [[Special:Contributions/Liberaltears|Don't be an anti-Catholic zealot!]]'''''</sup> Saturday, 23:19, 28 August 2020 (EDT)
 
:::::::::I tried the first suggestion, but it didn't work. Regarding the second idea, it was somewhat confusing, and I'm not sure if I did it right, but it didn't work either. I'm just wondering though, why would such an error even occur in the first place? That type of problem never happened for me before the server problems that started showing up around four weeks ago. —[[User:Liberaltears|Liberaltears]]<sup>'''''[[User:Liberaltears/mail|May Dataclarifier be well!]] | [[Special:Contributions/Liberaltears|Don't be an anti-Catholic zealot!]]'''''</sup> Saturday, 23:19, 28 August 2020 (EDT)
 +
 +
Yeah, sorry about that...it's not a very intuitive process. They don't expect average users to be tinkering with that.<br />
 +
The answer to your question is somewhat complicated, but I will do my best to explain it. When CP changed over to its new server, the website's IP address changed. So, the domain name record was updated. This means that when you try going to "conservapedia.com," your browser retrieves the new server's IP, rather than the old one. It then connects to that IP address, and the average user is none the wiser that anything has changed. However, the domain name system is a complicated network of servers and caches, so it can take a little time for everyone to get the update. There are also safeguards in place to prevent anyone from being out of date for too long, typically. My thinking here is that perhaps your computer still has the old IP address, rather than the new one. This could happen for a few reasons, but realistically shouldn't happen for anywhere near this much time. Theoretically, your computer itself could have the old address cached. This means that it wouldn't even bother to ask anyone where to look for "conservapedia.com," but rather just go to where it always goes (which has recently become incorrect). However, there is an expiration date attached to that DNS record, so typically within a week, your computer will decide it is time to go ask someone else if the site has moved. (We forced it to do this, by clearing your DNS cache.) It gets an update by sending a request to your local DNS server, which is typically run by your internet service provider (ISP). Your ISP then in turn looks up that information from more authoritative source of information (ultimately an internet root server, although they may be intermediary servers). So, if your computer isn't caching the old DNS record longer than it should, my thinking was that perhaps it is getting a stale record from your upstream DNS server. That is why I suggested trying a different DNS server.<br />
 +
Here's another idea: Try connecting to Conservapedia's IP address, rather than domain name: https://96.125.173.110/Main_Page
 +
Your browser will give your a security warning or error message, because the HTTPS encryption isn't designed to work without a domain name. Most browsers still give you an option to continue to the site, although Chrome might not. I also would '''not''' recommend logging in to your account this way, since your credentials could be intercepted by malicious individuals online. However, there is no harm in just connecting, to see if you still get the error you have been getting. You should be getting the exact same site either way, just with the TLS encryption broken in this case. --[[User:DavidB4|<font color="ForestGreen">DavidB4</font>]] <sup>([[User talk:DavidB4|TALK]])</sup> 02:03, 29 August 2020 (EDT)
    
== Minuteman ==
 
== Minuteman ==
Block, SkipCaptcha, Upload, Automoderated users, Check users, delete, edit, Moderators, move, oversight, protect, ratelimit-exempt, rollback, Administrators
20,386

edits

Navigation menu