New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Tiny VPS with good uptime for Uptime Kuma
I'm using Uptime Kuma on PikaPods to keep an eye on all my things, but on PikaPods, I can't set the pod to use version 2 of Uptime Kuma, which would help with some performance issues. Since the stable version is still 1.x, that's what PikaPods uses.
So, I'm thinking about moving Uptime Kuma to a small VPS somewhere in Europe. It can be really small because I only need it for Uptime Kuma, but it should have great uptime since, well, I'm going to use it for uptime monitoring.
Any suggestions? Uptime Kuma is super light on resources, so a very tiny VPS would work.
Thanked by 1nghialele
Comments
I have one on oracle 1G free plan with good uptime but I wonder if the tiny spec is really enough for uptime kuma when your monitor list is a bit long because the response is quite slow for simple operation like login or delete servers.
1.heartbeat-it
2.LiteServer
I am using Uptime Kuma on Oracle Free Tier plan with a script that runs something every 15-20 minutes to prevent the 'suspend' part for no using VPS.
LE: Or maybe use strato.de 1 EUR/month VPS or netcup pika servers.
For me my netcup pika is struggling a lot when loading the UI.
checks and alarms run fine, but the UI takes forever to fill with data / servers.
But on the other hand those netcup servers almost never go down
Oracle/GCP have always free instances
EDIT: GCP only in the US tho
I can recommend free KVM NAT VPS from microLXC.
https://lowendtalk.com/discussion/165452/microlxc-public-test/p1
I use a server in Norway, uptime is about a year.
Thanks all, I prefer something more straightforward than Oracle/GCP and in the meantime I found a BF offer for RackerNerd for a 1c1g VPS in Dublin for $16/year so I got one of those and have migrated the app. It's working great now. Thanks all
Are you using v1? If yes I recommend switching to v2 beta which has support for embedded or external MariaDB and performs A LOT better.
This is good to know. I've been really struggling with Uptime Kuma recently (it works okay but is terribly slow). Will give v2 a try.
Believe me, the difference is like night and day. I'm not sure if it's because of the architectural changes in the app in v2, or because it's using MariaDB instead of SQLite, but the difference is huge. I don't think you can upgrade while switching the database type, though, so you might have to set up the new instance from scratch.
Yes, the difference is huge. However, fortunately you indeed can migrate while keeping the data. I tried it and it did take a while for me but the migration worked flawlessly.
https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2
i fixed this by simply removing the monitoring agent that oracle installs.. been working for years now :P
I was mostly talking about switching from Sqlite to MariaDB, which, as the page you linked also mentions at the end, isn't supported. Did you get it to work?
Greetings!
Feel free checking our Turkey/Istanbul located solutions
https://tarisu.com/category/vps-server
Regards.
Thanks, but how I mentioned a few posts above I already found a solution
But does is support IPv6?
You can use Cloudflare Workers for checking your server. It's free (it has limits, but you won't reach them in this use case) and you can write the app in Rust, JavaScript (or any derivative). Use resend(dot)com to send mail via API - it has free tier too. It is the "true" serverless setup with 100% uptime I'm using currently.
Whoops, so sorry, turns out I am dumb in the head haha.
I have been running V2 for like a week now, and to be honest I didn't read into the project all too much. Just moved to V2 because of performance issues too, and after migration it runs very well with no interface lag or anything of the sort. For some reason, I thought they dropped SQLite support for V2 because I saw that MariaDB Embedded was available in the full docker image (which I am using).
I just checked back the logs, and turns out yeah, I'm still on SQLite despite the fantastic performance now. Nevermind the MariaDB migration comment I mentioned!
I am migrating my instance from Fly.io to Netcup Pico. The database migration from SQLite to MariaDB is underway(it might take one or two hours more). Although I have kept data for six months, the database is growing day by day. It has already crossed 1GB in size, and I am not halfway done adding my monitors there, so I might cut the storage time to three months or lower. Let's see how my migration goes to v2, and of course, if everything goes perfectly, I am gonna stick with it for a long time, just like my Fly.io instance is still going good even after three years.
In a few concurrent user and low data situation like Uptime Kuma I find it very hard to believe that MariaDB would outperform SQLite. On the contrary, SQLite should beat MariaDB (and most other SQL databases) when it comes to read performance.
Tutorial pls
is this one systemctl status unified-monitoring-agent https://docs.oracle.com/en-us/iaas/Content/Monitoring/Tasks/verify-agent-installation.htm ?
im running ubuntu 24 so its installed using snap. simply run snap remove oracle-cloud-agent to remove it.
I'll migrate my over 400 monitors over to MariaDB and let's see
For now, SQLite has been horrible and can't even hold data for over 1d. Corrupted multiple times and like hundreds of MBs of failed log files.
AMD or Ampere? It seems that Ampere isn't installed by default.
Wow. I didn't know sqlite was that bad
I mean, 20s TCP checks on over 400 monitors is not easy to store
Something must be seriously wrong, I've ran SQLite databases close to 100G without any problems at all so unless you save like 10 years of history it should not be a problem.
idk, I either get sql constraint errors or some pool is full error?
still, probably related to uptime-kuma since I would assume it wasn't meant to be used with that many monitors.
Did migration yesterday from v1 to v2. Had around ~10 monitors. Converting sqlite to mysql did not work for me, so I deployed a fresh kuma stack (kuma beta 2 + mariadb in docker) and started from scratch. Have got ~70 monitors now. Let me know if anybody wants docker compose for the stack.
Hi there,
You can get up to 12 months free for a small VM in US, EU or CA with us.
More details: https://www.enginyring.com/en/freehosting