Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 


Awesome
4813 posts

Uber Geek
+1 received by user: 1062

Trusted
Subscriber

  Reply # 1512211 13-Mar-2016 10:13
Send private message

timmmay:

 

Probably not, but it will give more information. I know my servers were generally more compatible and worked with more browsers when I added TLS 1.1 and 1.0 than when I was 1.2 only.

 

 

Yes, I've gone with TLS1.2 for the highest security. As it's exclusively for my own use I have no need to support legacy tech.

 

Nonetheless, last night I did try both TLS1.1 and 1.0. Exactly the same result.





Twitter: ajobbins


14267 posts

Uber Geek
+1 received by user: 2590

Trusted
Subscriber

  Reply # 1512216 13-Mar-2016 10:37
Send private message

Assume you googled the error message and found this post on SF? One suggestion is to try disabling TLS1.2. Again it's just diagnosis, not suggesting you stay like that.





AWS Certified Solution Architect Professional, Sysop Administrator Associate, and Developer Associate
TOGAF certified enterprise architect
Professional photographer


 
 
 
 


2284 posts

Uber Geek
+1 received by user: 375

Trusted
Subscriber

  Reply # 1512223 13-Mar-2016 11:16
Send private message

Try going to https://www.howsmyssl.com/ and check the difference between the browsers and add whatever Cipher to your config that you're missing. 


1586 posts

Uber Geek
+1 received by user: 156

Trusted

  Reply # 1512224 13-Mar-2016 11:16
Send private message

Use ssllabs.com as I posted earlier.

 

 

under "Handshake Simulation" it has the various versions of Android

 

If you have version 4.4.2 of android on your device or greater you should be fine.

 

 

Happy to have you pm the url you having issues with.




CPU: Intel 3770k| RAM: F3-2400C10D-16GTX G.Skill Trident X |MB:  Gigabyte Z77X-UD5H-WB | GFX: GV-N660OC-2GD gv-n660oc-2gd GeForce GTX 660 | Monitor: Qnix 27" 2560x1440

 

 




Awesome
4813 posts

Uber Geek
+1 received by user: 1062

Trusted
Subscriber

  Reply # 1512225 13-Mar-2016 11:34
Send private message

OK I have resolved it. I'm not 100% sure this is what it was, but when I created the initial key pair for the client cert, I used 2028 bits instead of 2048 (Assume a typo in the guide I was following).

 

I generated a new cert with 2048 instead and it's all working now. Guess Windows was fussier about it than other things were.





Twitter: ajobbins


1 | 2 
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.