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
Getting static login page, unable to login from android application / wallabagger #7211
Comments
It's only the login page with is broken? Once logged in, styles are ok? Can you share the html of the login page? |
Yes that's correct, only the login page is broken, styles load on login. This is the html for the login page:
|
Hey, did you manage to figure anything out? Anything you'd suggest I try? Would really love to get Wallabag up and running again. |
Hey, sorry to bump, but would still really like some help woth this :) |
Hi, I am not a dev and I haven't heard about NixOS yet. But I was wondering if there is also a webserver in front of wallabag? Apache2? Maybe you can post that webserver-config for wallabag. Some people like to change this, because wallabag is/was open for new user registration as a standard. So it is a good idea to prevent access to /register. I am just wild guessing if this config is blocking more, than it should. |
Environment
My
app/config/parameters.yml
is:What steps will reproduce the bug?
I have a systemd installation script for making the installation declarative, and am running it through a reverse nginx proxy on my LAN, as well a module for configuring wallabag which you can browse here. I can make this easier to reproduce if you're willing to install NixOS. The module also details my entire Nginx / phpfpm setup for inspection too (ie the root is set to
/web
)The login page looks like this
I have little understanding of php, but reading through the
autoload_real.php
file I believe it may be related to static login page? As you can see, it's not attempting to load any of the other resources. When I try to login through the wallabag android app I get "no wallabag instance found at that URL", and the wallabagger extension fails without logs (I'm not sure where to find add-on debug logs to be fair).I have had this installation since wallabag 2.6.6 and had previously ran this same setup with no issue, so I'm not sure what changed. Once I login, wallabag is working correctly, so I presume it's something going wrong with the login page, not the installation.
Happy to answer any other questions, would love some help getting this fixed, wallabag is crucial to my workflows
systemd installation script
Thank you for making wallabag♥️ it's great software
The text was updated successfully, but these errors were encountered: