Open gerroon opened 2 years ago
You should check server logs - an Internal Server Error
occurs when the app is simply trying to load articles via API.
You should check server logs - an
Internal Server Error
occurs when the app is simply trying to load articles via API.
Thanks but why would it start doing it suddenly? The web app works, and I have not anything else on the server between the versions?
Hard to say. Some data may cause errors on the API, but not on the web UI. Maybe the updated version handles something differently. It should be clear(er) after checking the logs.
Hey there. I had the same issue of the android app getting a 500 when trying to perform a quick sync. Also started out of the blue.
What I did:
44.33.22.11 - - [27/May/2022:09:57:27 +0200] "GET /api/entries.json?perPage=30&page=1&sort=updated&detail=full&order=asc&since=1653464118 HTTP/1.1" 500 5538 "-" "okhttp/4.9.1"
44.33.22.11 - - [27/May/2022:10:04:12 +0200] "GET /api/entries.json?perPage=30&page=163&sort=created&detail=full&order=asc&since=0 HTTP/1.1" 500 5538 "-" "okhttp/4.9.1"
@gerroon: maybe you can try this out if it's not too many articles?
My config in case it could help:
@njean42 I had that issue before and I was able to get the app back by removing last article however in this case between the upgrades there were not any new articles, so in my view that would not be an article related issue, given the app started freaking out aftert the upgrade.
makes sense indeed
did you solve the error? I have problemms too, but seems a different error:
Unbekannter Fehler wallabag.apiwrapper.exceptions.UnsuccessfulResponseException: HTTP response: 403 Stacktrace: wallabag.apiwrapper.exceptions.UnsuccessfulResponseException: HTTP response: 403 at wallabag.apiwrapper.WallabagService.checkResponse(WallabagService.java:1525) at wallabag.apiwrapper.WallabagService.checkResponseBody(WallabagService.java:1503) at wallabag.apiwrapper.WallabagService.execAndCheckBody(WallabagService.java:1499) at wallabag.apiwrapper.WallabagService.lambda$getArticles$0$WallabagService(WallabagService.java:218) at wallabag.apiwrapper.-$$Lambda$WallabagService$PrzoUvX9wnRBX2jTxVqPJ-eD3zU.run(Unknown Source:4) at wallabag.apiwrapper.NotFoundPolicy.call(NotFoundPolicy.java:140) at wallabag.apiwrapper.NotFoundPolicy.call(NotFoundPolicy.java:133) at wallabag.apiwrapper.NotFoundPolicy.call(NotFoundPolicy.java:128) at wallabag.apiwrapper.WallabagService.getArticles(WallabagService.java:218) at wallabag.apiwrapper.ArticlesQueryBuilder.execute(ArticlesQueryBuilder.java:282) at wallabag.apiwrapper.ArticlesPageIterator.hasNext(ArticlesPageIterator.java:80) at fr.gaulupeau.apps.Poche.service.workers.ArticleUpdater.performUpdate(ArticleUpdater.java:183) at fr.gaulupeau.apps.Poche.service.workers.ArticleUpdater.update(ArticleUpdater.java:127) at fr.gaulupeau.apps.Poche.service.workers.ArticleUpdateWorker.updateArticles(ArticleUpdateWorker.java:77) at fr.gaulupeau.apps.Poche.service.workers.ArticleUpdateWorker.update(ArticleUpdateWorker.java:37) at fr.gaulupeau.apps.Poche.service.tasks.UpdateArticlesTask.run(UpdateArticlesTask.java:17) at fr.gaulupeau.apps.Poche.service.tasks.ActionRequestTask.run(ActionRequestTask.java:25) at fr.gaulupeau.apps.Poche.service.-$$Lambda$0cveUIqKhxWljSld0gpOhfhYfj0.run(Unknown Source:2) at fr.gaulupeau.apps.Poche.service.TaskService.run(TaskService.java:162) at fr.gaulupeau.apps.Poche.service.TaskService.lambda$PgumDII_lptJcUDKRD70B1M_ER8(Unknown Source:0) at fr.gaulupeau.apps.Poche.service.-$$Lambda$TaskService$PgumDII_lptJcUDKRD70B1M_ER8.run(Unknown Source:2) at java.lang.Thread.run(Thread.java:920)
Web pages work fine, first seem after the upgrade. Any Ideas? TIA Micha
I was not able to solve it. I just stopped using the app.
@Micha-Btz I would suggest to start with re-running the connection wizard, because the error you get seems to be related to authentication.
@gerroon so you didn't find anything useful in the server logs?
@di72nn re-running the connection wizard solved the issue for me. Thanks.
Well F###.
It appears running the connection wizard will not only re authenticate but will also wipe your local database. This if very frustrating as I lost a few days of reading and some articles I will never remember about :(
The issue had been happenning to me for about a week (?) on the official app.wallabag.it.
Hi
I upgraded my Wallabag from 2.4.2 and 2.4.3 and the app started having problems and throws these exceptions/
I host Wallabag with Apache and Mysql on Debian testing. I use the 2.4.3 version of the app on Android 18.1. This was working fine in Wallabag 2.4.2