Probably more eloquent than my usual contributions but, in fact, it was a case of “computer says no” when I tried to submit any text as accessing this site via safari has sent my iPad into complete meltdown since Friday. Chrome seems ok still once I ignore all the security warnings.
So is the issue with how the site looks on the Safari browser in iOS linked to the out of date certificate problem?
Seems that way. I’ve started visiting here on the Chrome app and haven’t had issues, while it’s been practically unusable on iOS for a few days now.
That was me trying to post on the Chrome app via IOS and I could only get that far by ignoring the warning. Can't do anything on Safari at all, or on Chrome for Windows. The only one which works for me is Edge. It seems to be taking quite a long time to sort out a pretty major problem...
Quite. And if the owner sees this site as a business (or part of a business) as previously mentioned on here, you'd think getting it sorted might be a bit higher up the priority list.
It has got to the point where i’ve had to download tapatalk to access the forum. Sent from my iPhone using Tapatalk
You don't know what you're doing, You don't know what you're doing, You don't know what you're doing,
Apple are trying to protect you by blocking elements they think are potentially dangerous. I don't have access to an iOS device to check right now, but my guess is they've disabled the TLS 1.0 and 1.1 protocols, requiring 1.2 or later. The site isn't currently serving up TLS 1.2.
I bet you're getting more enjoyment out of watching our misery than you are out of looking at your own shiny, working forum.
In the interests of trying to help out here, I did some sniffing around to see what I could work out. I obviously have no access to any of the backend so this is just based on publicly available info. It looks like this forum is running Xenforo on an Apache Web Server. The web server is enabled for a number of outdated protocols: SSL 3.0 TLS 1.0 TLS 1.1 And does not support the following recommended protocols: TLS 1.2 (consider this mandatory) TLS 1.3 (this is more optional, but good if you can do it and will future proof you) To fix this, you will likely need to modify the Apache server to support recommended protocols, and remove support for the deprecated ones. Depending on how old the forum code and backend is, this may require an upgrade, or it may just be a case of needing to modify the appropriate files. I don't remember what version is required for TLS 1.2, but I think 1.3 required Apache 2.4.38 or higher. The file you generally need to modify is httpd.conf (or equivalent - it can vary depending on what your backend web server is, and I can't see that). To appropriately enable/disable the relevant protocols, the SSLProtocol line should probably look like this: SSLProtocol -all +TLSv1.2 If your Apache version is high enough to support TLSv1.3 you could add that too (I believe that should be +TLSv1.3 - put a space after the 2 in 1.2 and add it there). SSLProtocol -all +TLSv1.2 +TLSv1.3 Remember that these configuration files are case sensitive.
Just a quick update folks, we have now passed the matter on to a third party to resolve. Thank you very much to Arakel for the additional help, this will be resolved shortly.
Would NEVER* have happened with Gloryhorns!! * The rubber band running the server would have snapped before hand
We are updating the server as the old server is having a hissy fit, it may go offline for a bit but we will forewarn you lot. Maybe.
I'm still having troubles getting on here via Firefox on my phone. Also, just downloaded tapatalk, tried to download the wfcforums but it keeps saying network error. It allows me to download other forums fine. Any help appreciated
I need to contact admin. Is there a direct email someone can box me because the contact us isn't working for me...
Doesn't seem to have been mentioned but Tapatalk on Android doesn't seem to work either. Fortunately, Watford aren't doing anything apart from wishing everyone under the sun a happy birthday lately. Signings are secondary.
Thanks to all involved in resolving this issue, that had made the site unusable on my iPad. It obviously became more complex, and the time and effort is much appreciated.
Once I saw the warnings, I stayed away from the site like a scaredy-cat! Technology freaks me out and the use of terminology that sounds made up is annoying to me, to the great amusement of my kids. But the site is back up and running so well done to the techies.
