Apologies to all who may have encountered that error on the forum here when trying to post, or anything else which may have triggered it, this should now be fixed. I've been recently updating server software and making a couple of configuration changes, and didn't notice any problems until just a bit ago when I ran into that error.