Notices by Masto.host (mastohost@mastodon.social), page 5

I know it's Saturday and you are all getting ready to go party :P but I would like to ask you to do this before you https://masto.host/changing-your-instances-dns-settings

It's not mandatory and nothing will happen if you don't but I think you should *wink wink*

This will hopefully be the last time I ask you to play with DNS settings.

Did you know that is currently under testing the ability to add custom CSS via the Administration interface https://github.com/tootsuite/mastodon/pull/8399

If all goes well, soon you will be able to customize your instance design even if you don't have access to the server or you don't want to mess with SCSS?

Big thanks to @Gargron

Here is something for Masto.host shared hosting admins that like to test stuff: https://masto.host/testing-new-dns-settings-for-shared-hosting

Be aware that this is just a test and most of you can IGNORE THIS.

Upgrade finished! All instances hosted by Masto.host are now on
:mastodon: v2.4.4

Let me know if you run into any issues. Thanks

I will be starting the installation of the Mastodon patch for all instances hosted in Masto.host soon.

Instances will go down one by one for a couple of minutes. This process it take several hours.

Details on the patch: https://github.com/tootsuite/mastodon/releases/tag/v2.4.4

Some instances were down for a couple of minutes because of a sudden burst in load in App Server 3. Checking to see what happened and will be moving some instances out of that App Server to try and avoid it happening again.

OK, maintenance finish for those servers and all is looking good on my end.

Any issues, please let me know and thank you for your patience.

TL;DR some instances will be restarted and a couple of minutes of downtime

OK! So, I believe I found what was driving me crazy for the past 48 hours and it should be the source of this: https://github.com/tootsuite/mastodon/issues/8263

I used OVH Debian image and didn't notice the /var partition size that it auto creates. I was randomly hitting out of space inside the containers because of /tmp files.

I am going to move Docker outside of /var and we should be good :)

I had to add a notice on Masto.host website:

"Notice due to high demand new instances can take up to 24 hours to be installed"

Hopefully I will catch up in the next days but currently it's not possible to do better.

I am getting reports of an issue where a Mastodon service gets halted and only after manual restart it comes back.

I have just reported this: https://github.com/tootsuite/mastodon/issues/8263

Please keep an eye out until I manage to understand what is causing it and let me know if you experience some odd behaviour in your instance (timeline not updating, stuck in "under maintenance page").

Thanks

I just had to move 2 app servers into a new bare metal server because they got unresponsive and 15% of the instances were down for a while.

I know I am repeating myself but I am truly sorry. I just can't add servers fast enough into the shared hosting cloud.

I will continue as fast as possible.

OK, we are back.

It was close to 8 minutes of downtime but every instance should be up and running.

Let me know if you experience any problem ?

Masto.host instances upgrade to v2.4.3

I started the upgrade for all Masto.host instances and it should gradually reach all instances hosted by Masto.host during the next hours.

As always, you should expect a couple of minutes of downtime on each instance.

Let me know if you run into any issues.

As GDPR is about to get into action, I decided to make a new Privacy Policy page for Masto.host: https://masto.host/privacy/

I did this without any legal help just using common sense and following this: https://gdprchecklist.io/

If any of you have suggestions on how to improve it, I am all eyes/ears :)