Welcome Guest!
In order to take advantage of all the great features that Waterloo Region Connected has to offer, including participating in the lively discussions below, you're going to have to register. The good news is that it'll take less than a minute and you can get started enjoying Waterloo Region's best online community right away.
or Create an Account




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SSL
#16
If changing hosts I'll definitely need some help
Reply


#17
What's wrong with GoDaddy?

(What a hilarious name, lol)
Reply
#18
(02-21-2019, 06:19 PM)Canard Wrote: What's wrong with GoDaddy?

(What a hilarious name, lol)

Think of them like the Walmart of hosting providers Smile
Reply
#19
(02-21-2019, 09:27 AM)Spokes Wrote: If changing hosts I'll definitely need some help

I'd be willing to help you as well source out a VPS solution that may possibly be cheaper than GoDaddy and allow more control depending on the needs. If you wish to discuss off thread, feel free to PM me.
Reply
#20
Thank you!
I've learned so much in the 4 years since creating WRC, but this is definitely not my area of strength. So many of you have helped and offered to help. Truly speaks to the greatness of this community.
Reply
#21
But if it's just for the free SSL certificate, it might make more sense to pay the $12/year for now (for a non-free one), there is non-trivial work involved in switching hosting. Of course, if there are other compelling reasons to switch ...
Reply
#22
(02-21-2019, 11:53 PM)tomh009 Wrote: But if it's just for the free SSL certificate, it might make more sense to pay the $12/year for now (for a non-free one), there is non-trivial work involved in switching hosting. Of course, if there are other compelling reasons to switch ...

I thought you had mentioned that it was $12/year for the first year and then escalated to $100... I did have the impression that GoDaddy is sort of evil (and one can search the Internet for details) although it doesn't seem to be in the news that much these days. Escalating does count as minorly evil to me.
Reply


#23
That's a major jump.  I'll definitely take care of it.  I've been in discussion with a member about some options, I just need to get on it.
Reply
#24
$100 per year is a relatively small amount of money compared to the time and effort of managing one's own server though, especially for folks who are not familiar with it. Spokes you're entirely capable of learning, and like the others I'd be happy to help with migration, administration, etc but you should also consider the value of your time when making the budget decisions.
Reply
#25
It's crazy how much I feel like I've learned compared to where I started.

You all need to be careful. I'm keeping track of who's offering help Wink
Reply
#26
So I've (finally) gotten started on the security for the site and gotten an SSL certificate.  The host says it's active, but Chrome is still saying it's not secure.  Anyone notice a change?  Any advice?

As a side note, thanks to everyone who's purchased a Premium Membership this year.  It's a little different than the donations of the past, but the same goal.  Your support for WRC has been so positive and reminds me how great of a community we have here.
Reply
#27
(08-13-2019, 01:46 PM)Spokes Wrote: So I've (finally) gotten started on the security for the site and gotten an SSL certificate.  The host says it's active, but Chrome is still saying it's not secure.  Anyone notice a change?  Any advice?

As a side note, thanks to everyone who's purchased a Premium Membership this year.  It's a little different than the donations of the past, but the same goal.  Your support for WRC has been so positive and reminds me how great of a community we have here.
Just tried the site with https:// its partially there. Style sheets etc seem broken.

Fix would be to change to make it agnostic to the protocol... 
BEFORE
<link type="text/css" rel="stylesheet" href="http://www.waterlooregionconnected.com/cache/themes/theme1/star_ratings.css" />
AFTER
<link type="text/css" rel="stylesheet" href="//www.waterlooregionconnected.com/cache/themes/theme1/star_ratings.css" />
Reply
#28
Have a look at https://www.godaddy.com/community/SSL-An...td-p/50372

I think there should be a setting somewhere in your forum admin settings for web site URL, I’d start with that and change the http to https in it. You may also need to add to a .htaccess file to force HTTPS 

https://htaccessbook.com/htaccess-redirect-https-www/

Also check any custom code you may have on your pages that may still be trying to access something on “http://waterlooregionconnected.com/stuff” and change that to https also
Reply


#29
(08-13-2019, 01:46 PM)Spokes Wrote: So I've (finally) gotten started on the security for the site and gotten an SSL certificate.  The host says it's active, but Chrome is still saying it's not secure.  Anyone notice a change?  Any advice?

As a side note, thanks to everyone who's purchased a Premium Membership this year.  It's a little different than the donations of the past, but the same goal.  Your support for WRC has been so positive and reminds me how great of a community we have here.

HTTPS by default runs in parallel with HTTP. So you can go to http://waterlooregionconnected.com to access over HTTP, or https://waterlooregionconnected.com to access over HTTPS. Unless one manually types HTTPS the default is HTTP.

Most sites setup a redirect on the HTTP site. So if you go to http://example.com you get immediately redirected to https://example.com. You'll need to setup that redirect, as jason897 explained, to get the proper experience.

Before doing so however, you need to fix the HTTPS site. Once you load a page over HTTPS, all the JavaScript, CSS, etc must also come over HTTPS. Otherwise the security is totally invalidated, as someone could inject malicious JavaScript via the unencrypted HTTP and take over a HTTPS page. Therefore modern browsers will simply ignore any references to JS, CSS, images, etc that are HTTP on a HTTPS site. You'll need to update the references (as neonjoe explained), probably via a setting in the admin panel, to use HTTPS URLs for all the JS/CSS/images/etc. It's okay if a HTTP site includes HTTPS assets, so don't worry about making HTTPS the default.
Reply
#30
(08-13-2019, 02:01 PM)neonjoe Wrote:
(08-13-2019, 01:46 PM)Spokes Wrote: So I've (finally) gotten started on the security for the site and gotten an SSL certificate.  The host says it's active, but Chrome is still saying it's not secure.  Anyone notice a change?  Any advice?

As a side note, thanks to everyone who's purchased a Premium Membership this year.  It's a little different than the donations of the past, but the same goal.  Your support for WRC has been so positive and reminds me how great of a community we have here.
Just tried the site with https:// its partially there. Style sheets etc seem broken.

Fix would be to change to make it agnostic to the protocol... 
BEFORE
<link type="text/css" rel="stylesheet" href="http://www.waterlooregionconnected.com/cache/themes/theme1/star_ratings.css" />
AFTER
<link type="text/css" rel="stylesheet" href="//www.waterlooregionconnected.com/cache/themes/theme1/star_ratings.css" />

Better yet:

<link type="text/css" rel="stylesheet" href="/cache/themes/theme1/star_ratings.css" />

It's unusual for a site’s links to itself to need to mention either the protocol or the site name — root-relative or in some cases even relative links are fine.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)

About Waterloo Region Connected

Launched in August 2014, Waterloo Region Connected is an online community that brings together all the things that make Waterloo Region great. Waterloo Region Connected provides user-driven content fueled by a lively discussion forum covering topics like urban development, transportation projects, heritage issues, businesses and other issues of interest to those in Kitchener, Waterloo, Cambridge and the four Townships - North Dumfries, Wellesley, Wilmot, and Woolwich.

              User Links