HTTPS is the issue. You can connect to the site fine using standard HTTP. If you click on the the WFCForums.com logo at the top of any page, or the home button, it will redirect you to an HTTPS url, which isn't currently working. Recommend using the "back" button to navigate instead. Until they fix the SSL certificate issue (looks like it's expired) the site is HTTP only.
I'm OK with the "Not secure" in itself showing in the address bar (I use Chrome), as that's what you get with old sites like bsad.org and they are harmless, but the fact it appears in red looks a bit dodgy.
Unable to log in on either Chrome or Safari this morning - have not had any previous problems. This was the message on Chrome: This site ues an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site. NET::ERR_SSL_OBSOLETE_VERSION The connection used to load this site used TLS 1.0 or TLS 1.1, which are deprecated and will be disabled in the future. Once disabled, users will be prevented from loading this site. The server should enable TLS 1.2 or later. This is clearly becoming a serious problem and it really needs fixing asap.
These sort of messages appear when the certificate is being updated. Looks like we need to give them a short while as somethings obviously happening.
Our plan is working, that's one of the political ones thinking about leaving. A few more to go and the certificate will be reinstated.
Amusing, but - you are on the case, right? Because there will be more than the political types giving up soon...
If it's any consolation, It's actually a good error to be getting (considering where we came from). It means the server is now using encrypted connections, albeit on a deprecated protocol. That's a much better situation than it was, where the connection was being made completely unencrypted. While the earlier TLS protocols are less secure than 1.2, they're significantly better than a completely unencrypted connection. Essentially the older protocols just need to be disabled at this point (making TLS 1.2 the default) and everything should be good.
If you say so, guv. All I know was that I couldn't access the site via methods that had always worked in the past.
Yes, it'll definitely be inconvenient since modern browsers try very hard to protect us. Just wanted to reassure that it's not as dire as the warning makes it sound (although it does need to be fixed). Plain text passwords are now not at risk, and it would require a much more sophisticated attack to take advantage of the vulnerability in the older protocols so it's very much an improvement overall.
It's getting worse, viewing it on my mobile is like I've gone back in time to the browser wars, and I can't reply to anything or see my alerts without clicking on Show All. It probably explains why there's been so little traffic lately.
Same here tried on Safari and Google on Laptop, same on Mobile, it's strange, as sometimes I can get on, but have to go a few warnings to get there and then the graphics are all out , and a plain white background. Been like this for nearly 2 weeks now.
Dammit beginning to wish I hadn't retired now. Will have to put up with your onlyfans account I suppose.
Thanks UEA - I have had this since Friday but my iPad is also not allowing me to post anything in that format. So I can press the reply button but can’t then actually write anything! Your post alerted me to try something other than safari so I am here on chrome instead and it works - still had to bypass a load of security warnings though.
