One of the machines on which the forum runs experienced a significant hardware failure, details are unknown to me as the hosting provider didn't provide clarity, but it resulted in them restoring a snapshot from just before the failure to a new piece of metal.
Unfortunately this resulted in changes in IP addresses, and that resulted in my iptables and ufw rules not allowing the machines to speak to each other, which then triggered the outage.
I was on mobile and out for a few hours so couldn't get back in and fix it even though I suspected firewalls were to blame.
It's back up now, should survive... I've made a couple of small changes to make it survive better next time, but I won't know if they work until the next time the machine reboots... I may trigger that later just to give myself peace of mind.
Don't worry about formatting, just type in the text and we'll take care of making sense of it. We will auto-convert links, and if you put asterisks around words we will make them bold.
Tips:
Create headers by underlining text with ==== or ----
To *italicise* text put one asterisk each side of the word
To **bold** text put two asterisks each side of the word
Embed images by entering: ![](https://www.google.co.uk/images/srpr/logo4w.png) That's the hard one: exclamation, square brackets and then the URL to the image in brackets.
* Create lists by starting lines with asterisks
1. Create numbered lists by starting lines with a number and a dot
> Quote text by starting lines with >
Mention another user by @username
For syntax highlighting, surround the code block with three backticks:
```
Your code goes here
```
Just like Github, a blank line must precede a code block.
If you upload more than 5 files we will display all attachments as thumbnails.
One of the machines on which the forum runs experienced a significant hardware failure, details are unknown to me as the hosting provider didn't provide clarity, but it resulted in them restoring a snapshot from just before the failure to a new piece of metal.
Unfortunately this resulted in changes in IP addresses, and that resulted in my
iptables
andufw
rules not allowing the machines to speak to each other, which then triggered the outage.I was on mobile and out for a few hours so couldn't get back in and fix it even though I suspected firewalls were to blame.
It's back up now, should survive... I've made a couple of small changes to make it survive better next time, but I won't know if they work until the next time the machine reboots... I may trigger that later just to give myself peace of mind.