From f7de16fa6b2b0bfec3abe63140409eb08d614698 Mon Sep 17 00:00:00 2001 From: Hunter Long Date: Fri, 18 Sep 2020 12:49:08 -0700 Subject: [PATCH] Created Issues (markdown) --- Issues.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 Issues.md diff --git a/Issues.md b/Issues.md new file mode 100644 index 0000000..fde3319 --- /dev/null +++ b/Issues.md @@ -0,0 +1,19 @@ +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. + +### Update to Latest Version +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` + +### Blank/White Page +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 + +### Database Migration Errors +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. +- 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) \ No newline at end of file