Custom domain name comes up as un-trusted site

• 

  usethings · Member · Apr 7, 2015 at 11:31 pm

  • Copy link
  • Add topic to favorites

  This is the second time someone has told me there is a problem using the custom domain name for my site:

  ” I tried to click on your ClimbDesign.co link today from your recent blog comment, and it didn’t work because Chrome says the Climb Design site isn’t “secure.”
  Once I took the “s” out of the https, it totally worked, but I got blocked in Chrome initially.
  works: http://climbdesign.co/
  doesn’t work in chrome, coming from the US: https://climbdesign.co/”

  I expect this will be effecting my traffic for users not so savvy as the above. How can I resolve this?

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

• 

  thatrobyn · Member · Apr 8, 2015 at 12:03 am

  • Copy link

  Hey there,

  This warning can be dependent on whether or not they are checking out your site on a non-secure wifi connection, or a public connection.

  You can tell your visitors that they can add your site as a Trusted Site to their browser, and this will alleviate the issue:

  https://en.support.wordpress.com/https/#frequently-asked-questions

  Your site IS safe, it’s just that their computers don’t know it yet. You can test out those instructions yourself and see how they work for you…and you can ask any visitors what browser they are using, and copy/paste our instructions.

  That should do the trick! If I can help in any other way, please drop me a line. Cheers :)

• 

  usethings · Member · Apr 8, 2015 at 1:19 am

  • Copy link

  Thanks thatrobyn
  This sorts that one readers problem but for future publishing of a link to my site (emails, comments, promotional material, etc) should I revert to the climbdesign.wordpress.com address so people following the link won’t be put off by their own security settings/warnings?
  That being the case the custom domain becomes redundant.
  I do worry that in the fickle world of the internet people lose patience quickly so any obstacle is important. There are few that will persist and even fewer kind enough to alert me to the problem.

• 

  thatrobyn · Member · Apr 8, 2015 at 4:47 pm

  • Copy link

  Hello there!

  Personally, I wouldn’t change to my WordPress.com site name because of this issue. Chances are the number of folks with super high security on their browsers (or always browse via https) is really low. Most folks are checking out websites via http connections.

  Of course, we want you to feel comfortable, so I can help with whatever you want to do.

  I think one of my colleagues wrote a nice description of what is happening here:
  https://en.forums.wordpress.com/topic/misconfiguration-after-buying-a-domain-name?replies=2

  You let me know how you want to proceed and if I can assist in any way. Thanks again.

• 

  usethings · Member · Apr 8, 2015 at 11:24 pm

  • Copy link

  Thanks Thatrobyn
  Now I’m aware of it I’ll use the wordpress address in hyperlinks. In the begging I went with the WordPress address because WordPress is cool, but then thought .co looked more substantial than a free blog and liked to support WordPress.com too. Anyway it’s too late now, I still like both so have posted about the warnings on my blog.
  Cheers
  Tim

• 

  thatrobyn · Member · Apr 8, 2015 at 11:29 pm

  • Copy link

  Hey Tim,

  I think you found the perfect balance, then. If eventually, you wish to let go of the custom domain name, or fully embrace the custom domain name, the world is your oyster. Nothing is permanent, so if you change your mind, or have any questions in the future, please do let us know!

  Thanks much :)