-
Notifications
You must be signed in to change notification settings - Fork 15
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
Changing URL of wallabag breaks Android App Access #87
Comments
I suppose you can access your wallabag from your mobile web browser ? (to check if it's related to the app) |
Sure. That works absolutely fine. |
I have no clue about what could be the issue, and I don't undertand Yunohost change URL enough to know if that 302 redirect is related. |
Okay - i can live without the app for some time and will leave the setup as is to be able to provide logs. Shall i create/link some issue (not sure what context to tell them) or do you have experience how to do it? |
One option could be to uninstall the app an reinstall it, to check if it works - and if so, that would mean the issue comes from changing the URL in the app. |
Hey again, i couldn't let it go ;) i checked It is...
So the app does not like the SSOWat that yunohost uses... so i disabled the sso in nginx config for wallabag domain and it works
This makes you loose single sign on of course, but now the App works... I don't know if there is a better/nicer way. Another drawback is that yunohost will constantly complain that the file was changed... |
I had deleted the cache and data of the app which for me equals a reinstall. It was in fact no deal but it had apparently not helped. |
Well I'm not sure that SSO is enforced by default, and is necessary, as you can connect directly to Wallabag. In my case it wasn't necessary to connect, but once connected to Yunohost you don't have to connect to wallabag too. Maybe when we change the URl we miss a step that gives this behaviour... 🤔 |
Hi,
pre-info:
i'm not sure if this is a problem with the wallabag2_ynh package or with wallabag2 itself or with the wallabag android App. I'm just starting to investigate this and thought i'd let you know.
I'm starting to raise an issue here, because wallabag2_ynh is the part that has changed from a working setup.
I'm in the process of migrating Domains.
Wallabag URL change itself seems fine. After changing to a new domain (which i added before of course) access ot wallabag2 WebUI from my PC is fine. When i changed the URL in the Android App however, it constantly fails the connection test.
(2 lines) occur in the log for each attempt of the Android App to connect.
But it shows "Connection test failed - wallabag service not found - check URL"
As said before - access from PC works super fine. I can read and add articles to wallabag.
I checked the nginx config for the new wallabag domain and can't find any thing which would cause the 302 redirect though.
Also i ran a "grep -R olddomain.tld" in /var/www/wallabag to check if the migration did not change everything, but the only lines that are found are from old sessions/logins..
Any idea?
The text was updated successfully, but these errors were encountered: