-
-
Notifications
You must be signed in to change notification settings - Fork 655
Issues and Solutions
Hunter Long edited this page Dec 22, 2021
·
9 revisions
If you have issues with your Statping instance, this page will help you solve them. Before doing anything, I recommend updating to the latest version of Statping.
Updating Statping is very simple, you can choose one of the options below:
- Run command:
statping update
(you may need to run sudo depending on your server) - or Run command:
curl -o- -L https://statping.com/install.sh | bash
- or download tar.gz file from Latest Releases and extract for
statping
.
If your Statping instance is only showing a blank white page, this means there's an issue with CSS or JS assets.
- Update to the latest version of Statping
- Delete the
assets
folder if you have one - Restart Statping instance
If you notice a database error during migration, you can reset your Statping instance while keeping previous data so you won't have to re-input.
- In your Statping directory (contains config.yml) run command:
statping export
. This will export all elements into a timestamped JSON file. This file will not include previous hits or failures. - Delete
assets
folder if you have one. - Delete and Recreate MySQL, Postgres database, or delete
statping.db
. - Import previous data by running:
statping import backup.json
(replace backup.json with your exported filename)
-
DELETE FROM hits WHERE created_at < '2020-02-21 00:00:00';
// Delete hits older than -
DELETE FROM failures WHERE created_at < '2020-02-21 00:00:00';
// Delete failures older than
Statping.com | Demo | Docker | Notifiers | API
Email: info@statping.com