[v2] Cannot save

Well this is exciting! I have v2 up and running, but (sad face) nothing will save. Specifically, no matter what I edit, create, etc. I receive a red error stating “Could not save page, retrying again in 10s”.

The browser console has a variety of interesting errors, none of which look familiar to me (happy to provide more info about any or all of these):

v2 is deployed with docker-compose. User and group are 1000, and I’ve chown’ed (recursive) the directory containing the space.

Zen browser (Firefox clone) running on NixOS. The container is on an Ubuntu host.

Any ideas?

Try it in incognito mode. If it works, then clear the page cache and it should work.

This seems like some plugs are breaking your setup. Are you upgradeing from v1? If so, deleting everything under _plug, then reload your client a few times (and let it sync). If that fixes it, I’d be interested to learn which plugs you had installed to see how to address that. If not you may also want to try to run a System: Wipe Client and then reload again to completely reset all cached data in your browser.

The system.applyAttributeExtractors syscall has been removed in v2, so whatever is using that needs to be disabled.

Fascinating. It’s a clean, fresh v2 install. It’s in a container on the same host as my v1 install, and it’s a browser that’s using a v1 install, so I’m not sure if there could be some leakage there. I don’t know how well isolated webapps are in Firefox.

I tried it on a different machine and it works. Maybe more interesting: it actually WAS saving up to the server, as the changes I made showed up on a different machine, but something was triggering the error anyway. Clearing cache hasn’t worked (and I received the same error on a little-used Firefox install on the same machine), so this is a fascinating one indeed.

Going to wait it out and see what happens.

There shouldn’t be any leakage unless you access the new one on the same URL (host + port) are you doing that?

I’m not. Different ports for each (at the proxy level).

Just checked and it seems to have sorted itself out. I’ll update if I get the same error again. Very odd.

1 Like

Same here. I was using V1 on the same subdomain and have updated to V2 as a clean slate using a new storage.
Latest Firefox. Have cleared cache.

It should be noted that the .md file is saved correctly, even with the error.
I do expect this to clear up by itself, just thought I’d share the findings.