-
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
Wallabag & Google Chrome #396
Comments
Hi @ingenius,
Should look like:
Maybe it is also a good idea not to use a too complicated password with special characters others than I am using Firefox with this extension, I don't have chrome installed here. What is your Wallabager-addon version? |
Good morning,
Thank you for your prompt response.
When I create a new client in the wallabag API I only have the possibility
to put:
- A customer name
- Redirection address (optional)
Then I have information
: Customer ID
: Secret key
But I don't have a password...
I am attaching a screen of the information that I put on the Wallabagger
extension from the Chrome Store
I don't understand where I find this password?
Thank you in advance for your support
Le dim. 14 juil. 2024 à 16:01, Holger ***@***.***> a écrit :
… Hi @ingenius <https://github.com/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?
—
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APW7A2QNHDQ6DCGOAJ6A3PDZMKAE7AVCNFSM6AAAAABK3FLKJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGM3DAMJXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
Me again,
Well despite the explanations that I follow to the letter, this does not
want to work.
wallabag API token Not granted.
Everything is green except the password.
And yet this is the password to connect me
https://www.wallabag.ingeenus.fr/web/login
But for Chrome extension the password is not granted
I will have to copy and paste links that I want to keep directly in
wallabag. The Chrome extension would have been more practical.
Le dim. 14 juil. 2024 à 16:54, Holger ***@***.***> a écrit :
… 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.
—
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APW7A2WW62Z2TIBCJPJHHDLZMKGJBAVCNFSM6AAAAABK3FLKJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGM3TMNJZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 |
Thank you very much for this feedback.
However, I don't know anything about server settings.
I got a domain name and hosting from O2switch.
And for the installation of wallabag, this is done automatically with the
Softaculous software...
So, since I don't know anything about it, what can I do?
And what is the impact for the Wordpress site that I host and the software
that I install in its subfolder?
Thank you very much for your lights
Le dim. 14 juil. 2024 à 17:46, Holger ***@***.***> a écrit :
… *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
—
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APW7A2UA7OFPGAENTCSBIYDZMKML7AVCNFSM6AAAAABK3FLKJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGM4TCNZWHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
@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: 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 |
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 !
The text was updated successfully, but these errors were encountered: