πŸ†• New at EU TechStack: UptimeRobot [πŸ‡²πŸ‡Ή]

UptimeRobot monitors websites, APIs and endpoints, alerting teams to downtime or performance issues via email, SMS, Slack and more.

Simple, reliable monitoring with a solid European footprint.

πŸ”— Tool page: https://eutechstack.eu/tool/uptimerobot
πŸ‘‰ Explore more: https://eutechstack.eu

#uptimerobot #eutechstack #techstack

In a matter of minutes I've been able to copy all my monitors from #uptimerobot to #uptimekuma .

I am just astounded this still worked, flawlessly, immediately, just... amazed.

https://github.com/Peppershade/uptimekuma-migrator

I spent longer finding the migration script than I spent using it!

thank you Peppershade 🫑

GitHub - Peppershade/uptimekuma-migrator: Simple migrator from UptimeRobot to UptimeKuma

Simple migrator from UptimeRobot to UptimeKuma. Contribute to Peppershade/uptimekuma-migrator development by creating an account on GitHub.

GitHub

Been receiving emails from UptimeRobot for a few days saying that my site is down, then up again. I thought that my server was having issues, or that I was being sieged by scrapers again.

But today I found out that UptimeRobot is changing the IP addresses for their checkers and some of those IPs are in the StopForumSpam daily lists.

After getting the updated IP list from https://uptimerobot.com/help/locations/ and adding them to the allowlist of my firewall, the alerts are gone.

#stopforumspam #uptimerobot

Locations and IPs | UptimeRobot

If you get any false positives, there is a strong chance that the IPs used are blocked by your hosting provider. Make sure that you allow-list these IPs!

It's interesting how Uptime Robot used to be a solid monitoring platform and then they entered their enshittification phase and now it's nothing but false alerts.

#uptimerobot #enshittification

Replaced #Uptimerobot with a selfhosted #uptimekuma instance.
Anyone else experiencing errors with their #UptimeRobot services? Status pages aren't loading and sign-in fails too

My #GoToSocial instance is now online. Pulled the image 0.18.0-rc2 and now everything seems back to normal:

services: gotosocial: image: superseriousbusiness/gotosocial:0.18.0-rc2

Here's the Github issues that explained what happened: https://github.com/superseriousbusiness/gotosocial/issues/3787

I now got the status back up notification from #UptimeRobot:

Monitor is UP: Deuts One ( https://deuts.one ). It was down for 31 hours and 14 minutes.

What did we learn from this experience?

  • Exclude GoToSocial in #Watchtower automatic updates.
  • Stick to explicit version number in your compose.yml file.
  • Time to re-think self-hosting your own Fediverse instance.
  • [bug] no such column: media_attachment.updated_at - table is called media_attachmentS Β· Issue #3787 Β· superseriousbusiness/gotosocial

    Describe the bug with a clear and concise description of what the bug is. After running Watchtower to update GtS Docker to the latest version, it now doesn't startup and complains about a missing c...

    GitHub

    #UptimeRobot was great but they kept bombarding me with emails about wanting me to upgrade even though I meet their criteria for a free plan. Language like "we suspect your are not meeting our TOS".

    So I moved to Uptime Monitor and Pulsetic, the later seems to be working out better.

    #Downtime #Uptime