RAF Commands Forum problem

[Roundway]

Apologies for the delay, Alex, only just logged on. No, I didn't, mainly because Jagan posted earlier in the thread and his advice that the problem was widespread. That said I logged on to RAFCommands OK this morning just before posting this, so assume the matter has been resolved.

Brian

[Andy Mitchell]

Thanks - appears to be back on-line.

Jagan's post below related to an issue in 2022....

[Alex Smart]

Thank you Andy and Brian for your replies.
Yes I tried it and it does seem to be back. However the notice given was to the effect that the whole thing may 4ake a while, even weeks to correct and/or update. So I expect there may be more intruptions to come.

[Roundway]

Problem has reappeared. This time it's a privacy error and Google will not let me access the site. Having managed to get a little further I'm told the website cannot be found.

Brian

[Luc Vervoort]

Hi,

RAF Commands FB mentions :

The site will be migrated over from the current internet service provider to a new provider.
Time line
16 Mar - Forum will be locked down - No New posts or replies
18 Mar - Forum will be offline.
+/- over 3-7 days, we will come up either on www.rafcommands.com OR forum.rafcommands.com (To be determined)
For the Rest of the Site
The main site (Wordpress) and the Database Section will be available with very little downtime.
The Gallery will go away (Though the images will be in place)
Old forum Pre-2007 Archive and static pages will still be available.
Get your updates from www.facebook.com/rafcommands or twitter.com/rafcommands.

Best regards

Luc

[Roundway]

Thank you Luc. I wasn't aware as I don't use either FB or Twitter.

Brian

[Luc Vervoort]

Hi,

Just seen on RAF Commands FB

FORUM is ALIVE!!
https://forum.rafcommands.com

Best regards

Luc

[JaganP]

Thanks Luc for the posting the update.

For those not in the know - the RAFCommands Forum software runs on vbulletin 4. the software is outdated and has been running on PHP version that is also seriously out of date. an ultimatum from the hosting provider forced the outage and an upgrade into a new host/software version.

Hence the new URL - its hosted on a different server from the main site and database.