The Canadian Guitar Forum banner

1 - 20 of 22 Posts

·
Premium Member
Joined
·
8,713 Posts
There's no risk, what is bugging you exactly? include gcadmin with @ in front of the name in your response :)
 

·
Premium Member
Joined
·
1,206 Posts
No Scott, that is unfortunately not correct. www. is not listed as a valid name in the current certificate and, thus, that form fails authentication still. Kevin has indicated In a PM that he's got his tech guys on it, but not done yet. Try The Canadian Guitar Forum for a demonstration, clearing any cache you wish.
 

·
Premium Member
Joined
·
1,398 Posts
Using my phone and google is frustrating. There are two security warnings or more you must go through for every thing you click on.
 

·
Administrator
Joined
·
15,823 Posts
No Scott, that is unfortunately not correct. www. is not listed as a valid name in the current certificate and, thus, that form fails authentication still. Kevin has indicated In a PM that he's got his tech guys on it, but not done yet. Try The Canadian Guitar Forum for a demonstration, clearing any cache you wish.
I am currently showing green on my chrome.
 

·
Administrator
Joined
·
263 Posts
Hey guys

I know it's frustrating. I'm trying to light a fire under this with the tech team. For now, if you come to the site and it gives you a warning, delete everything in url before guitarscanada.com and reload the page. Https will load fine then.

Kevin
 

·
Registered
Joined
·
7,736 Posts
Hey guys

I know it's frustrating. I'm trying to light a fire under this with the tech team. For now, if you come to the site and it gives you a warning, delete everything in url before guitarscanada.com and reload the page. Https will load fine then.

Kevin
It may be a bit of nitpicking on my part Kevin, but if you get a warning coming to this site, how do you get this message so you can get to the site to get this message?

Kind of a "Catch 22"
 

·
Administrator
Joined
·
263 Posts
Fair point. Email notification would have the reply in them, but that doesn't help those who aren't subscribed to the thread. Will chew on this. Might be necessary to send out a mass email about this.

Kevin
 

·
Administrator
Joined
·
263 Posts
No nothing is infected. It's just an alert to say that the https security is not working properly. The links used in email notifications aren't loading that security feature.

I need permission to get a mass email sent out. Not something I can just do it seems.

Kevin
 

·
Registered
Joined
·
4,998 Posts
I think it should be easier to fix than to send out a mass email. :D
There seem to be guys on this forum who could show your IT guys a thing or two thousand. ;)
 

·
Administrator
Joined
·
263 Posts
Me? Yes. The techs? They seem pretty smart, just busy as hell.

Today, my request to get the fix expedited went through, and it should be fixed now!

Kevin
 

·
Premium Member
Joined
·
1,206 Posts
On a really quick check, I can confirm the fix with both www. and non-www, more testing much later.

Now let's please make sure it doesn't expire again in 2.5-3 months with a 2 week fix delay.

On another check, note that the fix is actually installation of a second certificate for www., independent from non-www. Frankly, that's just asking for trouble at expiration time. They are timed to expired on different dates! People always seem to insist on setting themselves up for failure ...
 

·
Registered
Joined
·
2,532 Posts
On my HP Laptop I can get on here with no problems https shows on wifi, on my iMac on wifi I show https with a "403 forbidden" message on safari and chrome. On my other iMac I get through with no problems, shows https both safari and chrome, on Ethernet. All three computers run off the same connection. WTF.
 

·
Premium Member
Joined
·
2,184 Posts
On my HP Laptop I can get on here with no problems https shows on wifi, on my iMac on wifi I show https with a "403 forbidden" message on safari and chrome. On my other iMac I get through with no problems, shows https both safari and chrome, on Ethernet. All three computers run off the same connection. WTF.
It's nothing to do with your connection. It is how various browsers and operating systems handle certificates.
 
1 - 20 of 22 Posts
Top