-
Notifications
You must be signed in to change notification settings - Fork 258
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
"Autofill" credentials doesn't work #986
Comments
I'm not sure why you got the "Couln't get API credentials" message (may be unrelated), but the 500 HTTP response indicates that the problem is with the server. Most likely, the app is uploading a URL that your server can't handle, so the synchronization fails and no articles are downloaded to the app. You need to check your server log (wallabag's (You need or beta for the following. Get it from releases or Google Play.) You can also check which URL the app is trying to send by going to |
This is from the server log: [2020-05-22 11:45:46] request.INFO: Matched route "api_get_tags". {"route":"api_get_tags","route_parameters":{"_controller":"Wallabag\ApiBundle\Controller\TagRestController::getTagsAction","_format":"json","_route":"api_get_tags"},"request_uri":"https://xxxxxxxxxxxxx.com/wallabag/web/api/tags.json","method":"GET"} [] |
Can't find "Dump to file" anywhere. |
You can try to find the problem article by running the following query on your server: select id, url, published_by from wallabag_entry where published_by like 'a:1:{i:0;s:26:%'; BTW, what database do you use?
As I said, you need the beta version of the app. |
Thank you! I found the dump in the meanwhile. I am using mysql, it is a share hosted domain. I don't have the access to the server. What I don't get, how can wrong author disable autofill of api credentials? API credentials are the first thing that are not autofilled. |
Reinstall, new log:
|
I don't think this is related. Maybe it's not even a problem anymore, I'm not sure what your current state is. The log suggests that the problem article is somewhere in the range 30-60: that is, if you start counting from your oldest articles ("all entries", not just "unread"), somewhere after the 30th article and before the 60th there should be an article that has something wrong with its "author" field. I suggest you to open each article (in that range) in your web browser and check the field. I'm not sure what exactly to look for, but hopefully the problem value will be noticeable. If you find something, you may try to re-fetch the article or [temporarily] delete it. The latest log doesn't have anything related to the problem. |
My current state is that I cannot login with the android app by providing username and password. The message I am receiving now is: No access to API: {"error":"access_denied","error_description":"OAuth2 autentication required"}. |
OK... I went through the articles. Deleted a couple that were fishy although I am not sure why. There are some whose content cannot be fetched but I guess those shouldn't cause problems. |
Manually filled in API credentials Error Server error |
Went to phpMyAdmin. Found the author "a:1:{i:0;s:26:"??..." and some others that were causing problems. Now android app can fetch articles from the server (and bag them as well like before) |
Are there any "minification" modules (that optimize or rewrite web pages in any way) enabled on the web server? The wallabag Android app parses the HTML to get API credentials, so any unexpected differences may cause such problems. |
Can you reproduce the issue with the article which was causing the problem? If yes, it would be cool if you can open an issue at the server repository (https://github.com/wallabag/wallabag/) |
I am not sure what minification modules are. This is shared hosting linux server I use to host my domain. Wallabag has it's own database, and folder inside public_html folder. In public_html are wordpress, tt-rss and nextcloud, all in their folders. I can access wallabag when I go to domain.com/wallabag/web |
If you access your wallabag, can you have a look at the HTML source code? |
It looks like a normal code. |
I guess it may also be caused by wallabag server being server from a subdirectory instead of its own sub-domain (but I'm pretty sure it worked before and IIRC the code wasn't changed in a while). @brdobrdo can you gather Android logs while the setup via the connection wizard is being performed? Alternatively you can create an empty account on your server and send me the credentials so I can debug the app myself. |
Sorry... I am new to this. How and where do I create an empty account? And how do I send you a message? |
There's a "Users management" menu in the left bar (wallabag web; you need to be logged in as your main account/admin), there is a "create a new user" button in there. You can send me an email to <my nickname> at gmail.com. |
@brdobrdo I received your email and I was able to reproduce the problem once, but haven't figured out what the problem is. I'll debug more later, so don't remove the test account yet. |
@brdobrdo you may delete the test user now. |
Thank you! |
Issue details
Duplicate?
Have you searched the issues of this repository if your issue is already known? yes
Actual behaviour
Wallabag on android stopped showing new articles that were bagged. Wallabag on the server showed them. So bagging works, showing of new articles on the android does not.
When checked the connection, I got the message: Couln't get API credentials. When manually filled in Cliend ID and secret, notification appears: Server Error; Error: com.di72nn.stuff.wallabag.apiwrapper.exceptions.UnsuccessfulException: HTTPresponse: 500
Expected behaviour
Wallabag should show new articles and connect and "read the API" from the server
Steps to reproduce the issue
2.Setup connection
Environment details
Logs
wallabag server
Please paste relevant wallabag server logs here (from file
<wallabag>/var/logs/prod.log
):Web server
Please paste relevant web server logs (e.g. from nginx, Apache, …) here:
NOTE: Be super sure to remove sensitive data like passwords, note that everybody can look here!
Your experience with wallabag Android app
Have you had any luck using wallabag Android app before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
It worked like a charm. I love it! Don't break my heart now...
The text was updated successfully, but these errors were encountered: