Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Wallabag
  3. sync-errors in Wallabag-App for Android

sync-errors in Wallabag-App for Android

Scheduled Pinned Locked Moved Wallabag
wallabagandroiderror msg
4 Posts 2 Posters 706 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • steinhmorS Offline
    steinhmorS Offline
    steinhmor
    wrote on last edited by
    #1

    I'm not able to use the wallabga app for Android with my Cloudron-Wallabag instance.

    The server connection in the app looks fine (getting the token works fine), but when I try to sync I get the following error and no items are synced:

    Serverfehler
    wallabag.apiwrapper.exceptions.UnsuccessfulResponseException: HTTP response: 500 
    Stacktrace:
    wallabag.apiwrapper.exceptions.UnsuccessfulResponseException: HTTP response: 500 
    	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:1012)
    
    

    Wallabag and cloudron are up to date, I tried the wallabag app from fdroid and the play store.
    I tested wallabag with two different cloudron-servers (Hetzner and netcup).

    Any ideas how to fix this? I would appreciate your help 😀

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      Besides maybe increasing the memory limit, I think this needs to be reported upstream in the wallabag issue tracker.

      steinhmorS 1 Reply Last reply
      0
      • nebulonN nebulon

        Besides maybe increasing the memory limit, I think this needs to be reported upstream in the wallabag issue tracker.

        steinhmorS Offline
        steinhmorS Offline
        steinhmor
        wrote on last edited by
        #3

        Thanks @nebulon! I've set the memory from 1 to 2 GB. This does not solve the problem.

        1 Reply Last reply
        0
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #4

          Then we can rule this out and it is better reported upstream. Maybe you can create an issue at https://github.com/wallabag/wallabag/issues and if so, please link it here then for context.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search