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 
ajobbins

5052 posts

Uber Geek

Trusted

  #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




timmmay
20574 posts

Uber Geek

Trusted
Lifetime subscriber

  #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.


insane
3236 posts

Uber Geek

ID Verified
Trusted

  #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. 




mentalinc
3225 posts

Uber Geek

Trusted

  #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: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB:  Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440

 

Quic: https://account.quic.nz/refer/473833 R473833EQKIBX 


ajobbins

5052 posts

Uber Geek

Trusted

  #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





News and reviews »

Air New Zealand Starts AI adoption with OpenAI
Posted 24-Jul-2025 16:00


eero Pro 7 Review
Posted 23-Jul-2025 12:07


BeeStation Plus Review
Posted 21-Jul-2025 14:21


eero Unveils New Wi-Fi 7 Products in New Zealand
Posted 21-Jul-2025 00:01


WiZ Introduces HDMI Sync Box and other Light Devices
Posted 20-Jul-2025 17:32


RedShield Enhances DDoS and Bot Attack Protection
Posted 20-Jul-2025 17:26


Seagate Ships 30TB Drives
Posted 17-Jul-2025 11:24


Oclean AirPump A10 Water Flosser Review
Posted 13-Jul-2025 11:05


Samsung Galaxy Z Fold7: Raising the Bar for Smartphones
Posted 10-Jul-2025 02:01


Samsung Galaxy Z Flip7 Brings New Edge-To-Edge FlexWindow
Posted 10-Jul-2025 02:01


Epson Launches New AM-C550Z WorkForce Enterprise printer
Posted 9-Jul-2025 18:22


Samsung Releases Smart Monitor M9
Posted 9-Jul-2025 17:46


Nearly Half of Older Kiwis Still Write their Passwords on Paper
Posted 9-Jul-2025 08:42


D-Link 4G+ Cat6 Wi-Fi 6 DWR-933M Mobile Hotspot Review
Posted 1-Jul-2025 11:34


Oppo A5 Series Launches With New Levels of Durability
Posted 30-Jun-2025 10:15









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.