Errors while fetching articles
Why does the fetch of an article fail?
There may be several reasons:
- network problem
- wallabag can't fetch content due to the website structure
Check production log for debug / error message
By default, if a website can't be fetched because of a request error (a 404 page, a timeout, a SSL problem, etc.) the error log message will be displayed in the
If you find a line starting with
graby.ERROR during the timeframe of your test it means the request failed because of an error.
Please report that error (and the whole text around in the log file) when opening an issue on GitHub.
Enable log to help us identify the problem
If you can't find an error message in the log and really can't find a way to parse the content after trying the previous 2 steps, you can enable log which will help us to find why it fails.
- replace in line 18
rm -rf var/cache/*
- empty file
- reload your wallabag and refetch the content
- paste the file
var/log/prod.login a new issue on GitHub
How can I help to fix that?
You can try to fix this problem by yourself (so we can be focused on improving wallabag internally instead of writing siteconfig :) ).
You can try to see if it works here: http://f43.me/feed/test (it uses almost the same system as wallabag to retrieve content).
If it works here and not on wallabag, it means there is something internally in wallabag that breaks the parser (hard to fix: please open an issue about it).
You can test it on f43.me website: click on Want to try a custom siteconfig? and put the generated file from siteconfig.fivefilters.org.
Repeat until you have something ok.
Then you can submit a pull request to
which is the global repo for siteconfig files.
If you can't wait for update from fivefilters - you can place your config file into directory
vendor/j0k3r/graby-site-config in your wallabag main directory.
Keep in mind these changes will be erased if you update your wallabag.
How can I try to re-fetch this article?
If wallabag failed when fetching an article, you can click on the reload button (the third on the below picture).