Fresh install of Firefox 117.0.1, no extensions, fresh install of wallabagger.
The extension cannot get the token. With the help of the extensions debugger, I saw that Firefox redirects the request to https
HTTPS-Only Mode: Updating an unsecured http request://***/ api/entries.json" to use "https".
Wallabag instance is added to the exceptions for HTTPS-Only Mode and I can open it via http in Firefox, but requests from the extension are redirected to https anyway. Disabling this mode solves the problem and the extension is authorized and works. But if you turn it back on, it breaks the extension again.
Upd. It's a home lan of course, I don't have a domain and I can't issue a certificate
Fresh install of Firefox 117.0.1, no extensions, fresh install of wallabagger.
The extension cannot get the token. With the help of the extensions debugger, I saw that Firefox redirects the request to https
Wallabag instance is added to the exceptions for HTTPS-Only Mode and I can open it via http in Firefox, but requests from the extension are redirected to https anyway. Disabling this mode solves the problem and the extension is authorized and works. But if you turn it back on, it breaks the extension again.
Upd. It's a home lan of course, I don't have a domain and I can't issue a certificate