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
DATABASE_PATH cannot be changed without error "Authentication request could not be processed due to a system problem." #7352
Comments
I was able to resolve this: the database_path absolutely must be This is still an issue: why is this? Can it be fixed? If not, should this be a user-configurable variable at all? (Probably not.) |
Can't this be a permission issue? Maybe wallabag can't write on the file you defined before? |
same error, docker on Ubuntu 20.04 LTS after Wallabag update. Been running this for years without problems. |
@airdogvan from what version to what version? |
not sure, last time I updated was about 6 months ago. Any way to get the current version? I can run docker exec -it wallabag_container sh. |
It's available in the |
https://my_wallabag/about results in https://my_wallabag/login Cannot login ... |
Otherwise |
version: 2.6.8 |
ok, problem solved. Hadn't update in a while and forgot to do: docker exec wallabag_container_name /var/www/wallabag/bin/console doctrine:migrations:migrate --env=prod --no-interaction Now works fine. Sorry for the trouble. |
@airdogvan I executed that command, and now I get |
Locally testing the server using docker (as per https://github.com/wallabag/wallabag/blob/master/.github/CONTRIBUTING.md#using-docker) always throws the error "Authentication request could not be processed due to a system problem." when trying to authenticate at the login page.
Confirmed with an existing database and also a brand new sqlite database created with new user wallabag/wallabag.
As far as I can tell there is no useful output in any logs.
Wallabag is installed fresh and successfully through the installer:
Environment
My
app/config/parameters.yml
is:The text was updated successfully, but these errors were encountered: