Unable to save pages

[cotsuka]

Only change as far as I can tell is the new Firefox update (149.0). Extension was working properly before but now upon attempting to save an entry I'm seeing the following error (from the extension inspector):

[Simounet]

Hi @cotsuka can you give me your wallabagger version please?

[cotsuka]

@Simounet v1.23.0

[Simounet]

Can you try with this version please?

[cotsuka]

Confirmed that works! So it's something between v1.22 and v1.23. I tried with v1.23.1 and it also doesn't work for me.

[Simounet]

• Can you setup everything correctly?
• This error only occurring on page saving?
• Can you turn the debug mode on and try again please?

[cotsuka]

On v1.22 I'm able to set everything up correctly and don't see any errors in the debug mode:

Here's the same page, same setup on v1.23.1. This only works if I first configure everything while on v1.22, then update to v1.23/v1.23.1. Once I go into the Wallabagger options, my previous settings seem to be forgotten and I have to attempt re-configuring everything (which fails).

[Simounet]

Seems like it's a server issue (error 500) with the content wallabagger sent to it. Can you look at the logs from your server please?
Can you do it at the extension setup? The url should end with /oauth/v2/token.

[cotsuka]

Very interesting, I think I have saving articles fixed on my end. Setting the extension up doesn't seem to work still if I'm just plugging in my Wallabag URL and clicking "Check URL" but I don't think that CORS issue will really ever be fixed unless I implement SSL within my home network. If that isn't your expected result, let me know and I'm more than happy to help debug that portion further.

---

If someone finds this in the future, the article saving issue seems to stem from Arch's PrivateTmp=true in php-fpm's systemd service unit and php-fpm being unable to know which private namespace to then find the tmp directory in. I fixed this by creating a temporary directory in a static path and pointing php-fpm there.

I still don't quite know why v1.22 (and previous) didn't have any issues for me, whereas v1.23 and v1.23.1 do. I noticed your FetchApi and WallabagApi changes but it doesn't seem like you're really changing any logic there.

---

Logs and such in case this is helpful in the future, all on v1.23.1.

When attempting to setup the credentials by plugging in my Wallabag URL and clicking "Check URL", I see this in the addon inspector and nothing in my server logs:

If I manually add the credentials and then click "Get Token", setup seems to work fine. Upon attempting to save a page, I see this in the addon inspector:

And this in the server logs:

Apr 09 15:00:09 host nginx[2084255]: 2026/04/09 15:00:09 [error] 2084255#2084255: *1454 FastCGI sent in stderr: "PHP message: PHP Warning:  PHP Request Startup: Unable to create temporary file, Check permissions in temporary files directory. in Unknown on line 0; PHP message: PHP Warning:  PHP Request Startup: POST data can't be buffered; all data discarded in Unknown on line 0" while reading response header from upstream, client: <snip>, server: <snip>, request: "POST /api/entries.json HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm-legacy/php-fpm-wallabag.sock:", host: "<snip>"

[Simounet]

@cotsuka do you think possible for me to work on your install to fix this issue?

[cotsuka]

@Simounet what would this entail? I'm more than happy to try new versions, make certain local changes to test configurations, etc. My Wallabag instance isn't exposed to the internet though so I wouldn't have a way for you to log into it on my end.

[Simounet]

This is kind of hard to lead you. You should try to debug my commit from these changes: 2bbc3803802f32a2fd13a07c87fef59585c48e36^...a182a4c

[cotsuka]

I'm not very well-versed in creating test/local versions of extensions, but I think this one might be a manifest issue:

wallabagger/wallabagger/manifest.json

Lines 41 to 43 in fe7f8b4

	"optional_host_permissions": [
	"*://*/api/*"
	],

That seems to only allow the /api routes but /developer is outside of that path. When I click on the Check URL button, I think this function is running, hitting the /developer path, causing the CORS error and not continuing with the rest of the autofill try block.

wallabagger/wallabagger/js/options.js

Lines 357 to 363 in fe7f8b4

	async autoFillApiToken () {
	// @TODO extract these URLs to wallabag-api.js
	const urls = {
	developer: this.data.Url + '/developer',
	clientCreate: this.data.Url + '/developer/client/create',
	login: this.data.Url + '/login'
	};

[Simounet]

Can you try your solution, just to be sure? You can load this modified extension temporary in your browser.