wallabag / wallabag/wallabagger

Unable to get token since migrating Wallabag database

Open
#246 4 comments 0 reactions 0 assignees View on GitHub
Awaiting response
Dominant language
JavaScript
Stars
471
Forks
71
Avg merge
4d 17h
Merged PRs (30d)
4

Description

Hi there,

First of all, thanks for the great work on this extension. Have been using it valuably for many years. Thanks!

I recently migrated my Wallabag database up to the latest version, which I should've done some time ago. This required a little hackery. Mostly deleting all rows from `wallabag_oauth2_auth_codes` and `wallabag_oauth2_refresh_tokens`, if I remember. Everything now seems to be ok, but now I have the problem that I can't get a token for the extension anymore:

![Screenshot 2020-12-17 at 11 13 40](https://user-images.githubusercontent.com/557391/102474770-578c1f80-4059-11eb-95d3-0f806fa75b83.png)

I tried creating a new client and using those details. Also disabling 2FA which I had newly enabled. No luck.

When I try to get a token, I get the following in the Wallabag docker logs:

`172.22.0.255 - - [17/Dec/2020:11:03:10 +0100] "POST /oauth/v2/token HTTP/1.1" 500 4768 "-" "-"`

500 error. How can I get more information so I can diagnose the problem, please?

I hope someone can help.

Thanks in advance

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.