http POST http://localhost:8000/oauth/v2/token \
grant_type=password \
client_id=1_3o53gl30vhgk0c8ks4cocww08o84448osgo40wgw4gwkoo8skc \
client_secret=636ocbqo978ckw0gsw4gcwwocg8044sco0w8w84cws48ggogs4 \
username=wallabag \
password=wallabag
grant_type=password \
client_id=1_3o53gl30vhgk0c8ks4cocww08o84448osgo40wgw4gwkoo8skc \
client_secret=636ocbqo978ckw0gsw4gcwwocg8044sco0w8w84cws48ggogs4 \
username=wallabag \
password=wallabag
in postman it works for me but in integromat, zappier, n8n or any other it doesn't
I am currently running Wallabag 2.3.8 (docker) tied to a postgres 9.6 (metal) instance. I really like my 2000 articles. I will pay someone $100 to help me migrate this instance to Wallabag 2.5 (docker), postgres 14 (docker) orchestrated with docker compose. Please email bobberb@gmail.com if interested.
Caveat: I like my cached images too, this has been hard to move correctly
@JuanAlberjon It looks like your getting the token is correct, it matches that I have. You then have to explicitly extract the OAuth token from the response.
{
...
"data_from_event": "{{ body | unescape }}",
...
"extract": {
"access_token": {
"path": "$.access_token"
}
},
...
}
Then put the access token into the attempt to POST the URL to Wallabag.
Hang on...
{
"post_url": "https://wallabag.example.com/api/entries.json",
"expected_receive_period_in_days": "365",
"content_type": "form",
"method": "post",
"payload": {
"url": "{{ url }}"
},
"emit_events": "true",
"no_merge": "true",
"output_mode": "merge",
"headers": {
"Authorization": "Bearer {{ access_token }}"
}
}
Hello. I've installed wallabag on my LAN (non docker install). Where do I set wallabag to listen on a different port? I've tried changing the Apache config to another port, but when I check via nmap, wallabag is not listening on the port I set. Any help is appreciated.
6 replies
Good morning folks. I am trying to connect my own code project to my Wallabag, but I am having a heck of a time trying to get the OAuth tokens for the API. The documentation directs you to make the call to https://app.wallabag.it/oauth/v2/token - but as I am self hosting I have changed it to be [base wallabag url]/oauth/v2/token - But that isn't working, anyone know where I should be directing it for my own instance?
@trickjarrett_twitter: Okay. I'm hosting my own too, on my LAN. I will try after work and see if I get an error too.
Have you tried using a token created in the UI of your instance and see if that works?
21 replies
@trickjarrett_twitter: I was doing something for work and a thought occurred to me. Although given the recent discussion and the fact that you can access your instance via browser without any problem, I suspect what I say next is moot. However, I would assume that you have given Apache appropriate permissions for your wallabag directory (and subs)? When I first did my setup I'd forgotten to do that and was getting errors, albeit for different reasons than you.
1 reply
Perhaps I can find a workaround. I'm working this code on the same server as my Wallabag installation. Is there a way I can utilize that to allow me to insert a URL into Wallabag? I guess I could insert it into the database directly but that wouldn't trigger the scraping, etc as far as I can tell. Any insights?
Hi everyone, I had an issue updating wallabag to 2.5.0 on my Debian/testing, with the following stacktrace when executing SYMFONY_ENV=$ENV $COMPOSER_COMMAND install --no-dev -o --prefer-dist of scripts/update.sh:
> Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap
PHP Fatal error: Uncaught TypeError: Symfony\Component\Process\Process::__construct(): Argument #1 ($command) must be of type array, string given, called in /var/www/ril.example.com/wallabag/vendor/sensio/distribution-bundle/Composer/ScriptHandler.php on line 310 and defined in /usr/share/php/Symfony/Component/Process/Process.php:143
Stack trace:
#0 /var/www/ril.example.com/wallabag/vendor/sensio/distribution-bundle/Composer/ScriptHandler.php(310): Symfony\Component\Process\Process->__construct()
#1 /var/www/ril.example.com/wallabag/vendor/sensio/distribution-bundle/Composer/ScriptHandler.php(88): Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::executeBuildBootstrap()
#2 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(389): Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap()
#3 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(238): Composer\EventDispatcher\EventDispatcher->executeEventPhpScript()
#4 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(104): Composer\EventDispatcher\EventDispatcher->doDispatch()
#5 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(218): Composer\EventDispatcher\EventDispatcher->dispatch()
#6 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(119): Composer\EventDispatcher\EventDispatcher->doDispatch()
#7 /usr/share/php/Composer/Installer.php(372): Composer\EventDispatcher\EventDispatcher->dispatchScript()
#8 /usr/share/php/Composer/Command/InstallCommand.php(139): Composer\Installer->run()
#9 /usr/share/php/Symfony/Component/Console/Command/Command.php(298): Composer\Command\InstallCommand->execute()
#10 /usr/share/php/Symfony/Component/Console/Application.php(1015): Symfony\Component\Console\Command\Command->run()
#11 /usr/share/php/Symfony/Component/Console/Application.php(299): Symfony\Component\Console\Application->doRunCommand()
#12 /usr/share/php/Composer/Console/Application.php(336): Symfony\Component\Console\Application->doRun()
#13 /usr/share/php/Symfony/Component/Console/Application.php(171): Composer\Console\Application->doRun()
#14 /usr/share/php/Composer/Console/Application.php(131): Symfony\Component\Console\Application->run()
#15 /usr/bin/composer(84): Composer\Console\Application->run()
#16 {main}
thrown in /usr/share/php/Symfony/Component/Process/Process.php on line 143After investigation, it seems that it's caused by my composer system installation that uses Symfony/Process from Debian package instead of the one from vendors. Is there any solution to that?
3 replies
So, under the belief that the core of my above issue with /oauth/v2/token url 404'ing is something to do with the install, I am attempting a fresh install from github. I follow the instructions on github, but I get an error after running:
cd wallabag && make installI get the following output:
composer.phar not found, we'll see if composer is installed globally.
Updating files: 100% (9/9), done.
Note: switching to '2.5.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 84c02608 Merge pull request #5799 from wallabag/release/2.5.0
[RuntimeException]
require.composer is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "^[a-
z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]?|-{0,2})[a-z0-9]+)*$".
make: *** [install] Error 255
Any insights from you all?
@trickjarrett_twitter: Update your composer version (but not too much) wallabag/wallabag#5823
2 replies
hmm strange, on Debian, composer is 2.2.12, but symfony is too recent for wallabag :/
BTW, I did not forget about you. My ISP was out at home for two days. They refuse to say what happened or how widespread. But from a local newspaper article, at least most of my county and the one next to us were out of service.
After running wallabag for a year with no issues I had to move it to new hardware. After restoring the postgres backup I got this error
*1 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'wallabag.wallabag_internal_setting' doesn't exist in /var/www/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:129I think I fixed it with the help of this wallabag/wallabag#4923
Now I that error is gone but now walllabag redirects me to http://www6.your-wallabag-url-instance.com/
I checked the DB and the content is there, and the domain_name is set correctly..
Any help would be appreciated
Is saving facebook posts supported in wallabag by default or do we need to do some setup?
im using the app.wallabag.it version
there's no support for facebook authentication and support for public posts is not guaranteed
1 reply
Also Facebook scrambles on purpose the page structure to avoid scraping
I was trying to get some public facebook posts to my kindle. I could do it find with some simpe sendokindle bookmarklets. Where they can easily get the post content cleanly. So I was wondering why wallabag couldnot do it .
Hi, i have made a contribution to wallabag : wallabag/wallabag#4883. This contribution should have been released with https://github.com/wallabag/wallabag/releases/tag/2.5.0 but it seems that this contribution is not in 2.5.0 nor 2.5.1. Do you have a problem with this contribution ? I was waiting for this release for a while :( Thanks for your answer.
Yep that's strange. Looks like it was lost during some rebase or merge. I'm sorry about that. Regarding what the PR changes we'll have to put it in the 2.6.0
1 reply
Essentially I would like to use all the main features of Wallabag but also be able to browse my Kindle Highlights and newsletters I have signed up to.
@dairefagan: there is no native way to do that, you may be able to implement something using the API but you'll need to develop something
@kdecherf:matrix.org Thanks for the info, I could look at that some time. For now, do you know if there is somewhere I can view existing integrations? I have seen mention of wallabag and calibre. It would be really great if I could chain wallabag >> calibre server/moon reader+ >> obsidian.