Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 500 with Wallabag server 2.3.5 #757

Closed
biva opened this issue Dec 23, 2018 · 5 comments
Closed

Error 500 with Wallabag server 2.3.5 #757

biva opened this issue Dec 23, 2018 · 5 comments

Comments

@biva
Copy link

biva commented Dec 23, 2018

Hello,
I just updated to 2.3.5 and my wallabag on android (2.1.0) displays now this error:
Error: com.di72nn.stuff.wallabag.apiwrapper.exceptions.UnsuccessfulResponseException: HTTP response: 500 Internal Server Error
I tried to reinstall the app, but same issue :(

I see a lot of related issues but I don't find a solution for me (#649 or #97 or #731 for example)

@biva biva changed the title Error 500 with Wallabag Error 500 with Wallabag server 2.3.5 Dec 23, 2018
@biva
Copy link
Author

biva commented Jan 2, 2019

@j0k3r thank you for your comment in wallabag/wallabag#3817

It's a bad configuration.

Is it a bad configuration on my wallabag server? My Android client? Of wallabag server in general?
How could I investigate this issue?

For reference:

  • Android client and Firefox addon were working before I updated to 2.3.5
  • Firefox addon is still working with 2.3.5
  • Android client is not working anymore ("error 500"), but the identification is working (a new client/token is created after I enter my credentials on Android app 2.1.0 beta (108)
  • I tried to clear the cache on the server cache:clear -e=prod

@j0k3r
Copy link
Member

j0k3r commented Jan 2, 2019

I said it's a bad wallabag configuration for the related issue, not yours.
Can you check for logs in wallabag? like var/logs/*

@biva
Copy link
Author

biva commented Jan 2, 2019

logs:

[2019-01-02 15:47:09] request.INFO: Matched route "api_get_version". {"route":"api_get_version","route_parameters":{"_controller":"Wallabag\ApiBundle\Controller\UserRestController::getVersionAction","_format":"json","_route":"api_get_version"},"request_uri":"https://www.mywallabag.com/api/version.json","method":"GET"} []
[2019-01-02 15:47:09] app.ERROR: Authentication failure for user "", from IP "192.168.1.1", with UA: "okhttp/3.11.0". [] []
[2019-01-02 15:47:10] request.INFO: Matched route "api_get_entries". {"route":"api_get_entries","route_parameters":{"_controller":"Wallabag\ApiBundle\Controller\EntryRestController::getEntriesAction","_format":"json","_route":"api_get_entries"},"request_uri":"https:// www.mywallabag.com/api/entries.json?order=desc&page=1&perPage=1&since=0&sort=created","method":"GET"} []
[2019-01-02 15:47:10] request.CRITICAL: Uncaught PHP Exception InvalidArgumentException: "The directory "/var/www/html/wallabag/var/cache/prod/jms_serializer" is not writable." at /var/www/html/wallabag/vendor/jms/metadata/src/Metadata/Cache/FileCache.php line 39 {"exception":"[object] (InvalidArgumentException(code: 0): The directory "/var/www/html/wallabag/var/cache/prod/jms_serializer" is not writable. at /var/www/html/wallabag/vendor/jms/metadata/src/Metadata/Cache/FileCache.php:39)"} []

@biva
Copy link
Author

biva commented Jan 2, 2019

I made the directory writable with
sudo chown -R www-data:www-data bin app/config vendor data web var
And now it works :)
Thank you!!

@biva biva closed this as completed Jan 2, 2019
@j0k3r
Copy link
Member

j0k3r commented Jan 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants