| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 123160 | 2012-02-07 21:49:00 | SSL error on Trademe site ... what to do next ... help appreciated | SP8's (9836) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1257944 | 2012-02-07 21:49:00 | Hi Guys n Girls My week is just getting better & better ... car now a crumpled heap and want to get some parts off Trademe. Have an account but keep getting the SSL warning with Site Security Cert not trusted ... haven't struck this before and not sure whether it was safe to proceed so backed out. Can someone please advise what I have to do to get logged in safely please ... or advise whether others are having the same problem. Thanks in advance |
SP8's (9836) | ||
| 1257945 | 2012-02-07 22:14:00 | Is the date/time/year on your computer the right date/time/year?? Looks like you can get that error if it's not current / today | Speedy Gonzales (78) | ||
| 1257946 | 2012-02-07 22:23:00 | Date, time, location all good Speedy ... this is the first time it's ever happened and only with Trademe ... all other Secure sites (banking. etc) are OK ... thought it may have just been a Trademe problem. | SP8's (9836) | ||
| 1257947 | 2012-02-07 22:28:00 | Might be trademe. I cant check. I'm not on trademe. Are you using FF, IE or something else? | Speedy Gonzales (78) | ||
| 1257948 | 2012-02-07 22:33:00 | No worries ... just checked with my son and he's able to get onto the site no worries. Thanks anyway. | SP8's (9836) | ||
| 1257949 | 2012-02-07 22:34:00 | No probs, might be your system if yours isnt to date. Since some updates also update the certs | Speedy Gonzales (78) | ||
| 1257950 | 2012-02-07 22:50:00 | Just checked for updates ... none. Doing a couple of scans just to make sure there's nothing screwing with it. | SP8's (9836) | ||
| 1257951 | 2012-02-08 07:43:00 | Hi, I have a cURL script that downloads sales from TradeMe, and that started failing on 3/2/2012 after working fine for many months. Checking the cURL commands individually, the one to https://secure.trademe.co.nz was the one giving the trouble (no HTTP response). Turning on cURL's trace option, I saw that the certificate was being rejected, either because it has expired (most likely) or they have changed authority. Turning on cURL's --insecure option gets around the problem. Hope this helps someone out there in SSL land! |
cubenz (13077) | ||
| 1257952 | 2012-02-08 08:45:00 | Is the date/time/year on your computer the right date/time/year?? Looks like you can get that error if it's not current / today I get the SSC not trusted etc warning all the time if I go on line with my W2K computer set to 1999, as it must be to get my non-Y2K compliant instrument software to work. Cheers Billy 8-{) |
Billy T (70) | ||
| 1257953 | 2012-02-09 00:11:00 | I have had a deep look at the SSL cert at trademe... the problem is likely going to be "self signed certificate in certificate chain" |
robsonde (120) | ||
| 1 2 | |||||