Andy

Teal’s brother.

As mentioned before the old server has been having some issues. There is a plan to move to a new/faster one, but there's some incompatibilities that need to be resolved first, hence taking a bit longer than we'd hoped. have made some configuration changes just now that _should_ alleviate some of the connection issues y'all have been seeing. May take up to an hour or so to take effect. thank you for your patience!

apologies. the old server is showing it's age. Was down a bit on Friday night and then yeh again this afternoon. We're in the process of moving to a newer/faster one with more capacity. so should improve in the next few days.

Hey, Sorry about the delay on this. @Teal had pinged me on it, but I was away on vacation without a laptop and unable to remedy it until today. So @Grafix please can you take a look and see if it's working for you? (It should be!) For those interested, it was one of those fun pandora box type probems. One of the 3rd parties Gun watch uses for sending emails deprecated the version of their API that Gunwatch was using, and had failed to tell @Teal or me ahead of time, which was annoying. Updating to the new version of API required us switching to a different library to talk to them, which required a different version of Ruby, which then meant a bunch of other stuff had to change too. It's all sorted now - so apologies for the inconvenience.

Fixed

Fixed

try now

Hey, I moved PW onto a new server today. As far as I can see everything is working as it should be. things should be slightly faster now too. Please holler if anything is broken. thanks!

I can provide all the details. Apologies for taking time do respond to this thread. Summary From Jan 31st 21:33:59 UTC until 13:22:47 UTC, the PigeonWatch forums were unavailable. Users will have experienced a server error due to an issue with the PHP module which provides database connectivity. This occurred following the routine application of security patches to the server hosting the Pigeonwatch website, Gunwatch website and the pigeonwatch forums. Due to a mistake on my part, I verified that www.pigeonwatch.co.uk and www.gunwatch.co.uk were up but failed to check the forums. As the forums were the only site using PHP, they were the only one affected. Details For some background, hundreds of updates have been applied to the underlying server with zero impact on availability over the years as such this was seen as a routine operation, without need for prior notification. The complication arose this time, because following the recent forum upgrade, the version of PHP in use on the server changed from 5.5.x to 7.1.x. However both package versioned remained on the server - with just the 7.1.x activated. Unfortunately due to an ordering issue in how the patches were applied, the system defaulted back to the prior 5.5.x version, which was incompatible with the new forum version, hence the errors being experienced by all. The reason it took so long to remediate, is with me being NYC based, 13:22, is 8:22am for me - so whilst I saw some emails from Teal saying there was an issue a few hours before, I was unable to respond. As soon as I saw there was an issue, I reacted and was able to bring the site back up. Next steps In terms of what we can do to prevent this happening again, I have: * updated the upgrade scripts to ensure we validate the forums are working * added a step to the upgrade checklist to check for errors in application logs for the forums * removed all traces of the prior version of PHP to avoid this specific issue being able to reoccur. hope this helps!

Not quite - the older version of PHP (5.5.9) had security updates until 2019. However InvisionBoard, who provide the forum code had stopped supporting version 3.4.x recently, thus meaning if there were bugs in that it would have been problematic.

looks great to me! Thank you Teal!

was out and about on saturday evening, and happened upon some Mallards on a pond. Couldn't resist taking a quick shot, and this is what I got