-
Notifications
You must be signed in to change notification settings - Fork 2
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
Can not start Pixelfed instance without OAUTH_ENABLED #32
Comments
Hmm, i've not been able to reproduce this - would you be able to share your config info ? |
Thanks for picking this up @aneillans ! @Murazaki and I discovered this when troubleshooting MySQL connections over SSL. There is a chance this could be an interaction with something else though which makes it tricky. However, as soon as I set OAUTH_ENABLED=false my Pixelfed web container will no longer start up and fail with:
The problem is if I start up with OAUTH_ENABLED=true I am not able to log into the Pixelfed instance: |
At this stage I do not require any OAUTH logins and would prefer this to be 'FALSE'. |
Some further debug info: When starting the instance with OAUTH=true the actually error message after decoding the diagnostic details:
However, when changing the OAUTH=false after starting the container the OATH error seems to be due to some problems with routes.
|
You can not seem to start the pixelfed instance with the environment setting of:
OAUTH_ENABLED=false
That's using the current pixelfed-glitch/pixelfed:develop Docker image.
The text was updated successfully, but these errors were encountered: