summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBenjamin Brahmer <info@b-brahmer.de>2021-05-12 17:26:04 +0200
committerBenjamin Brahmer <info@b-brahmer.de>2021-05-12 17:27:26 +0200
commit66920a02099d1196ffde27a2a33299e637aedca9 (patch)
tree6ebe3bac78f3d146f34e050b086d20814c69301d
parent71d8ada51aadc31197c8a87d1419e23753a3e679 (diff)
small fixes for faq
Signed-off-by: Benjamin Brahmer <info@b-brahmer.de>
-rw-r--r--docs/clients.md2
-rw-r--r--docs/faq.md16
2 files changed, 8 insertions, 10 deletions
diff --git a/docs/clients.md b/docs/clients.md
index c71065f61..5a515bf20 100644
--- a/docs/clients.md
+++ b/docs/clients.md
@@ -28,4 +28,4 @@ A sync client can be used to read news and synchronize via the API.
An update client uses the nextcloud API or the OCC CLI to update the feeds in News.
-* [Python mulithread updater](https://github.com/nextcloud/news-updater)
+* [Python multithread updater](https://github.com/nextcloud/news-updater)
diff --git a/docs/faq.md b/docs/faq.md
index dd62e19e4..3063922dc 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -39,16 +39,16 @@ The only fix for this issue is that feed providers serve their content over HTTP
This is very often caused by missing or old files, e.g. by failing to upload all the News app files or errors during installation. Before you report a bug, please recheck if all files from the archive are in place and accessible.
## Feeds not updated
-Feeds can be updated using Nextcloud's system cron or any program that implements the [News app's updater API](https://github.com/nextcloud/news/tree/master/docs/externalapi), most notably [Nextcloud News Updater](https://github.com/nextcloud/news-updater). **The feed update is not run in Webcron and AJAX cron mode!**
-
-System Cron:
+Feeds can be updated using Nextcloud's system cron or an [external updater](https://nextcloud.github.io/news/clients/#update-clients) via the API
+**The feed update is not run in Webcron and AJAX cron mode!**
+### System Cron
* Check if you are using the system cron (Cron) setting on the admin page. AJAX and Web cron will not update feeds
* Check if the cronjob exists with **crontab -u www-data -e** (replace www-data with your httpd user)
* Check the file permissions of the **cron.php** file and if **www-data** (or whatever your httpd user is called like) can read and execute that script
* Check if you can execute the cron with **sudo -u www-data php -f nextcloud/cron.php** (replace www-data with your httpd user)
* Check your **data/nextcloud.log** for errors
-* Check if the cronjob is ever executed by placing an **error_log('updating');** in the [background job file](https://github.com/nextcloud/news/blob/master/lib/Cron/Updater.php#L28). If the cronjob runs, there should be an updating log statement in your httpd log.
+* Check if the cronjob is ever executed by placing an **error_log('updating');** in the [background job file](https://github.com/nextcloud/news/blob/master/lib/Service/UpdaterService.php#L55). If the cronjob runs, there should be an updating log statement in your httpd log.
* If there is no **updating** statement in your logs check if your cronjob is executed by executing a different script
* Check if the **oc_jobs** table has a **reserved_at** entry with a value other than 0. If it does for whatever reason, set it to 0. You can check this by executing:
@@ -66,12 +66,9 @@ You will get two rows where column `class`will be `OCA\News\Cron\Updater` and `O
* If your cron works fine but Nextcloud's cronjobs are never executed, file a bug in [server](https://github.com/nextcloud/server/)
-[Nextcloud News Updater](https://github.com/nextcloud/news-updater):
+### External Updater
* Check if your configuration is set to **not** use the system cron.
-* Start the updater in loglevel info mode and check if the feed update urls are polled, e.g.:
-
- nextcloud_news_updater --loglevel info -c /path/to/config.ini
-
+* Consult the documentation of the updater
* Check your **data/nextcloud.log** for errors
## Adding feeds that use self-signed certificates
@@ -79,6 +76,7 @@ If you want to add a feed that uses a self-signed certificate that is not signed
If you have control over the feed in question, consider signing your certificate for free on one of the following providers:
+
* [letsencrypt.com](http://letsencrypt.com/)
If you do not have control over the chosen feed, you should [download the certificate from the feed's website](http://superuser.com/questions/97201/how-to-save-a-remote-server-ssl-certificate-locally-as-a-file) and [add it to your server's trusted certificates](http://www.onlinesmartketer.com/2009/06/23/curl-adding-installing-trusting-new-self-signed-certificate/). The exact procedure however may vary depending on your distribution.