Solution is to reduce monitoring history and frequency, as described here or add more CPU cores to the pod.
You may see offline monitors while either using the Shrink Database feature or reducing the number of days to keep. This can last for 5 to 10 minutes, depending on the data size.
This error means that a DNS lookup for your monitored site time out for some reason. This is perfectly normal, when doing many thousand monitoring requests a day.
To avoid getting an alert in such cases, be sure to set Retry to at least 2 or 3. That way you can be really sure a site is really down before triggering an alert.
PikaPods itself doesn’t implement a local DNS cache, but provides popular public resolvers to each pod.
To reset any user’s password:
- Stop the pod
- Enable SFTP in Edit Pod > Files.
- Download the current version of the SQLite database. Usually named
kuma.db. Keep a copy as backup
- Open the database with any SQLite tool and find the
- Add any bcrypt-hashed password. E.g. this is for just “password”:
$2y$10$IWoZl5q9Tvvp1wxROvi4hOul7XP.rfyrvm4xbm7ufVANke1nfvLIu. (Please change this later in the GUI when using it.)
- Put your edited database copy back in the same place.
- Start your pod back up and log in using the new password