diff --git a/frontend/src/main.js b/frontend/src/main.js
index ee918dcd..8cf0c965 100644
--- a/frontend/src/main.js
+++ b/frontend/src/main.js
@@ -5,16 +5,12 @@ import VueObserveVisibility from 'vue-observe-visibility'
import VueClipboard from 'vue-clipboard2'
import VueCookies from 'vue-cookies'
import VueI18n from 'vue-i18n'
-import * as Sentry from "@sentry/browser";
-import * as Integrations from "@sentry/integrations";
import router from './routes'
import "./mixin"
import "./icons"
import store from './store'
import language from './languages'
-const errorReporter = "https://bed4d75404924cb3a799e370733a1b64@sentry.statping.com/3"
-
const App = () => import(/* webpackChunkName: "index" */ '@/App.vue')
Vue.component('apexchart', VueApexCharts)
@@ -32,11 +28,6 @@ const i18n = new VueI18n({
Vue.$cookies.config('3d')
-Sentry.init({
- dsn: errorReporter,
- integrations: [new Integrations.Vue({Vue, attachProps: true, logErrors: true})],
-});
-
Vue.config.productionTip = process.env.NODE_ENV !== 'production'
Vue.config.devtools = process.env.NODE_ENV !== 'production'
Vue.config.performance = process.env.NODE_ENV !== 'production'
diff --git a/frontend/src/pages/Help.vue b/frontend/src/pages/Help.vue
index 61654a40..a189b19a 100755
--- a/frontend/src/pages/Help.vue
+++ b/frontend/src/pages/Help.vue
@@ -13,6 +13,8 @@
Notifiers
+ Issues and Solutions
+
Bulk Import ServicesEnvironment Variables
@@ -326,6 +328,44 @@ func AttachNotifiers() error {
+
+
Issues and Solutions
+
+
+
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
+- or download tar.gz file from Latest Releases and extract for statping.
+
+
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. 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)
+
+
Deleting Old Records
+
+
+
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
-Automatically generated from Statping's Wiki on 2020-09-15 19:09:14.703237 +0000 UTC
+Automatically generated from Statping's Wiki on 2020-12-20 10:21:49.484474 +0000 UTC
+ 