Misconfiguration after buying a domain name

• 

  simonetrentino · Member · Jun 9, 2014 at 6:01 am

  • Copy link
  • Add topic to favorites

  I can’t make changes at my blog. Everytime that I try this is what pops up:

  “This is probably not the site that you are looking for!
  You attempted to reach brisbanevents.com, but instead you actually reached a server identifying itself as *.wordpress.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of brisbanevents.com.
  You should not proceed, especially if you have never seen this warning before for this site.
  Proceed anyway Back to safety
  Help me understand
  When you connect to a secure website, the server hosting that site presents your browser with something called a “certificate” to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party trusted by your computer. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website that you intended and not a third party (such as an attacker on your network).

  In this case, the address listed in the certificate does not match the address of the website that your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached *.wordpress.com, but cannot verify that that is the same site as brisbanevents.com which you intended to reach. If you proceed, Chrome will not check for any further name mismatches.”

  The blog I need help with is: (visible only to logged in users)

• 

  jeremeylduvall · Member · Jun 9, 2014 at 8:12 pm

  • Copy link

  Hi there,

  This occurs when you yourself or a visitor to your site try to load your page over an HTTPS connection. Basically, the browser is looking for a certificate from brisbanevents.com. Instead, it sees a certificate from your default WordPress.com address (address.wordpress.com). The mismatch triggers an error.

  Fortunately, most users are going to be visiting your site over an HTTP connection unless they’ve set their browser up to prefer a secure connection (most haven’t). There are two ways around this:

  1. You could have them set an exception within their browser to ignore the certificate mismatch. This can be setup through your browser settings. In Chrome, you can find this setting by navigating to Chrome -> Preferences -> Show Advanced Settings -> Privacy -> Content Settings -> Cookies -> Manage Exceptions.
  2. Avoid using an HTTPS prefix when visiting your site

  Unfortunately, it isn’t possible for us to issue a certificate that makes it possible for visitors to view your site over an HTTPS connection without first setting up an exception.

  Let me know if you have any additional questions!