-
Notifications
You must be signed in to change notification settings - Fork 51
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
Wallabager refuses to check URL #408
Comments
Hi, |
No error in the console when you click on the "Check URL" button? |
Could you have any extension that can interfere with it? Can you try it with a fresh profile/another browser like Firefox? |
When I tried to link the Chrome extension to my hosted app.wallabag.it account in Thorium, I got this when I clicked "check URL": But when I set the "Disconnect" extension to "unblock site" when the tab with the Wallabagger options page was open, I was shown this when I clicked "check URL": When I entered my API keys, username and password, and clicked "get token", the extension worked. But sometimes I had to click the "Wallabag" icon twice for an article to be saved. |
Got a wallabag instance up and running, I can connect to it using the Android app without any issue.
On one (local network) computer I only managed to connect wallabager using the IP in HTTP, figured out it might have been a weird DNS issue.
But now I'm testing on my work PC and it just doesn't want to connect using the DNS name.
I enter the URL, hit "check URL" but the URL checked stays on "not checked" for some reason (on the following screenshot the permission checked got the "agreed", but refreshing the option page and trying again put it on "not checked")
If I copy and paste the URL in another tab, it works properly :
There is unfortunately nothing in the Chrome console when that happens:
And checking into the chrome extension manager, I can see the URLs being allowed for site access:
Wallabager version : 1.18.0
Wallabag version : 2.6.10
Chrome version: 131.0.6778.86
The text was updated successfully, but these errors were encountered: