Recently started requiring https even for self-hosted instances

I have the same issue as another reviewer. The addon installs and tries to check the URL I typed in, but "Wallabag URL checked" remains at "Not checked" although "Wallabag permission checked" changes to "Agreed."

Clicking the toolbar button throws an error, "api.GetTags().then is not a function."

Wallabag itself is working fine. I'm using a self-hosted Wallabag instance - Wallabag is hosted on my NAS which is on the same LAN as the machine running Firefox and the addon. I can access the Wallabag instance from my laptop and save articles with it, but the addon stops at the "Wallabag permission checked" step like described above, unfortunately :/

Can't get it to work with Firefox 107. It tries to check the URL (which is correct) but "Wallabag URL checked" remains at "Not checked" although "Wallabag permission checked" changes to "Agreed."

Clicking the toolbar button throws an error, "api.GetTags().then is not a function."

Meanwhile, Wallabag itself is working fine, so I don't think the problem is there.

I have been using Wallabag for a long time. This extension will not save pages to my account after the configuration.

"You can get the Client ID and the Client secret from the wallabag's API clients management part. If you don't have any existing client, you can create one following these steps..."

???????????????

In short, having reinstalled firefox and lost my authentication token, I can't log in anymore, can't get a new token because I can't figure out how to make that happen (see above), and just can't be bothered with this. Life is too short.

no es mi gusto