SSL problem

  • Unknown's avatar

    I have people trying to view my blog both on mobile and desktop, and are getting this: Nothing on mobile (Safari). Chrome says “You attempted to reach arabellaproffer.wordpress.com, but instead you actually reached a server identifying itself as 192.0.78.13. 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”

    I have no idea what to do, or if this is a WordPress issue?

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

  • Unknown's avatar

    http://www.arabellaproffer.com/ is NOT hosted by WordPress.COM and there is no domain mapping upgrade for arabellaproffer.com.
    arabellaproffer.com is hosted by DreamHost
    whois
    Name Servers:
    ns1.dreamhost.com
    ns2.dreamhost.com
    ns3.dreamhost.com

    I’m sorry but we are unable to provide support for any sites that are not hosted here at WordPress.COM and our support docs do not apply to your site.

    WordPress.COM and WordPress.ORG are completely separate and have different logins, features, run different versions of some themes with the same names, and have separate support forums. http://en.support.wordpress.com/com-vs-org/

    If you don’t have a username account at WordPress.ORG click http://wordpress.org/support/ and register one on the top right hand corner of the page that opens, so you can post to the Theme support forums there.

    Resetting your WordPress.ORG password http://codex.wordpress.org/Resetting_Your_Password

    WordPress.org support docs are at https://codex.wordpress.org/Main_Page

  • Unknown's avatar

    Know that if you are forwarding from http://arabellaproffer.wordpress.com/ to http://www.arabellaproffer.com/ that is not supported and not reliable.

    To set up domain mapping, assuming that’s what you are trying to do see here for mapping an existing domain that you already own http://en.support.wordpress.com/domains/map-existing-domain/

    After you do the primary blog set up it can take between 24 – 72 hours for domain name propagation to take place throughout the internet. You can view the DNS changes here > http://www.whatsmydns.net/ What’s important during that stage is to be patient.

  • Unknown's avatar

    If you are not trying to domain map please post again to let us know that and we can work from there.

  • Unknown's avatar

    I don’t mean arabelaproffer.com, I mean just the blog hosted by WordPress arabellaproffer.wordpress.com

    thanks

  • Unknown's avatar

    The blog site itself is not hosted by Dreamhost and it is a .com, not .org issue.

  • Unknown's avatar

    Howdy @vendettabella – Just to be clear, we’re only talking about arabellaproffer.wordpress.com, not arabelaproffer.com. Is that correct?

    I just tested your site out in several browsers, and I wasn’t able to recreate the issue. In Chrome, the site is loading correctly for me. Normally, this sounds like an http vs. https issue, but that shouldn’t happen with .wordpress.com addresses.

    Can you let me know if you’re still experiencing this issue?

  • Unknown's avatar

    Hi, yes! Ignore the straight-up arabellaproffer.com

    I’m not having a problem wit arabellaproffer.wordpress on my end, in fact I tried on a few browsers and my phone, but it appears a lot of people using Safari, Chrome, or have firewalls in place can’t view it or get the message…

    “You attempted to reach arabellaproffer.wordpress.com, but instead you actually reached a server identifying itself as 192.0.78.13. 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”

    I’ve never had anyone tell me they had this kind of problem before, so I wasn’t sure if it was always ongoing or this is new. I was just told to contact WordPress about it by my more tech savvy friends.

  • Unknown's avatar

    Thanks for the additional information! We just recently made some adjustments to our SSL certificates (more https-related items). I’m wondering if the individuals are still experiencing the error or if that happened previously? If they’re still experiencing the issue, could you possibly catch a screenshot and pass it along by uploading it to your Media Library?

  • The topic ‘SSL problem’ is closed to new replies.