From 12a06b91024ebe1dc8039d8116a54084795aa9f2 Mon Sep 17 00:00:00 2001 From: Suresh Alse Date: Wed, 28 Sep 2016 09:52:50 -0700 Subject: [PATCH] Update issues.md --- README/issues.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README/issues.md b/README/issues.md index 60b4573..9ac439c 100644 --- a/README/issues.md +++ b/README/issues.md @@ -8,3 +8,7 @@ __crontab-ui is running but is not accessible on browser__ - This is usually because the place where your crontab-ui is installed does not give access to others. It can be resolved by either giving permission to the user (Recommended) or running crontab-ui as root. Refer [this](https://github.com/alseambusher/crontab-ui/issues/8) __Hosting crontab-ui : it works on localhost but not outside the server__ - You have to host it using nginx, apache2, etc. Refer [this](nginx.md). + +__crontab-ui stopped working__ - It can happen that your crontab-ui can stop working for some reason like adding incorrect jobs or timings. In order to fix it, you can just go ahead a remove the job from `crontab.db` or `env.db` in "crontabs" folder and restart crontab-ui. + +__Where is my root node_modules folder__ - You can find it by `npm root -g`