Skip to content
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

Wallabag & Google Chrome #396

Open
ingeenus opened this issue Jul 14, 2024 · 8 comments
Open

Wallabag & Google Chrome #396

ingeenus opened this issue Jul 14, 2024 · 8 comments

Comments

@ingeenus
Copy link

Good morning,

I installed Wallabag on my server.
Impeccable installation.
For ease, because I use Google Chrome, I wanted to install the extension: Wallabagger.

Setting :
I give my wallabag URL
https://app.wallabag.it

Afterwards :
Client ID: for here it is ok and valid in green.
Secret key: for here it is ok and valid in green.
Username: for here it is ok and valid in green.

Password
This is where it gets stuck, because when you press the button: Obtain a token..... Nothing happens, the field remains red and in the checklist on the right the Wallabag API Token is Expired

Status Checklist
wallabag URL verified OK
Wallabag permission verified Accepted
wallabag API version 2.6.9
wallabag API Token Expired
The token expires in

Do you have any instructions or a solution to make this extension work?

If anyone has managed to make this button work which should generate a TOKEN I am interested

Thank you in advance for your support !

@HolgerAusB
Copy link

Hi @ingenius,

  • I assume, the given server name https://app.wallbag.it is just to mask the real server address for this post?
  • If you don't have SSL/TLS certificate, you should deactivate 'Use HTTPS' option and maybe set the ip as address. But the better way, of course, is to have a letsencrypt cert with your own domain to reach your wallabag with your mobile too.
  • you added a client at example.com/developer ? While example.com is your server name or ip.
  • you took your credentials from this page and copy that to wallabagger?

Should look like:

option content example comment
wallabag URL: wallabag.example.com set your real domain or IP
Use HTTPS: on/off depends, if you have SSL/TLS cert
Client ID: 1_xxx123...xxx 40 digits after the underscore
Client secret: zzz789...zzz 40 digits
User login: username your user at wallabag, the same from which you created the client credentails. NOT email address.
User password verysecret

Maybe it is also a good idea not to use a too complicated password with special characters others than .-#_!
Non-ascii letters could also be a problem: e.g. Á è ü

I am using Firefox with this extension, I don't have chrome installed here. What is your Wallabager-addon version?

@ingeenus
Copy link
Author

ingeenus commented Jul 14, 2024 via email

@HolgerAusB
Copy link

HolgerAusB commented Jul 14, 2024

When you open wallabag the first time in your browser, it ask you for username and password. This first user is also the admin of wallabag server. Maybe you want to register a second non-admin user.

When you creating the api client in /developer you should only provide a name, so you can remember which Software is using this clientID/clientSecret combination. I don't know in which cases the redirect URI is needed. It is empty here. So for the name of client choose something like 'HomePC Chrome' or 'iPhone FieryFieds'

The password you choose at login in wallabag is the same you have to put in the password field of wallabager's options page. Username should also be the same, of course.

I don't see a screenshot attachment.

@ingeenus
Copy link
Author

ingeenus commented Jul 14, 2024 via email

@HolgerAusB
Copy link

ALERT. you should protect your /register folder in your apache/nginx config or anyone can sign up to your server.

This has nothing to do, with your main problem, but you should really protect the register function/button

@ingeenus
Copy link
Author

ingeenus commented Jul 14, 2024 via email

@HolgerAusB
Copy link

As I don't know anything about Softaculous, shut down the server until a pro answers your questions. I am just a user, not a dev.

@HolgerAusB
Copy link

@ingeenus, Your server is still on. So I tried to register an account, just to check, if I can connect my firefox wallabagger (I will not install chrome!).

But after sending the register-form with (fake)email, username, password I got an error, which might be a hint to your problem, too:

grafik

And I found a video with a how-to install wallabag with Softaculous via cPanel

So you have to set your wallabag's admin username and password there. Hopefully you are remembering this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants