Problem during signup to CryptPad

I tried to signup to cryptpad hosted at pad.garudalinux.org. After I've entered my username and password, the website gets stuck at "Hashing your password, this might take some time.".

I have attached a dump of the JS Console for reference.

XHRGEThttps://pad.garudalinux.org/block/eJ/eJGcqPzjNfG-BDmHankIgR1xvrl6tRIKgPAu3qKX0A8=
[HTTP/2 404 Not Found 340ms]

no block found login.js:186:29
GETwss://pad.garudalinux.org/cryptpad_websocket
[HTTP/1.1 101 Switching Protocols 822ms]

allocating random bytes for a new user object login.js:293:25
GETwss://pad.garudalinux.org/cryptpad_websocket
[HTTP/1.1 101 Switching Protocols 830ms]

XHRHEADhttps://pad.garudalinux.org/common/feedback.html?REGISTRATION=8610ad4fa1f91
[HTTP/2 200 OK 300ms]

GEThttps://pad.garudalinux.org/common/pinpad.js?ver=3.24.0-1613388866222
[HTTP/2 200 OK 275ms]

GEThttps://pad.garudalinux.org/common/rpc.js?ver=3.24.0-1613388866222
[HTTP/2 200 OK 296ms]

loaded rpc module login.js:392:25
initializing rpc interface login.js:397:21
rpc initialized login.js:406:25
creating request to publish a login block login.js:409:21
Error: EACCES: permission denied, mkdir '/cryptpad/block/eJ' login.js:421:46
NOT_READY cryptpad-common.js:34:17
XHRHEADhttps://pad.garudalinux.org/common/feedback.html?TIMEOUT_OUTER=1b4e4c2b6516c
[HTTP/2 200 OK 303ms]

NOT_READY cryptpad-common.js:34:17
XHRHEADhttps://pad.garudalinux.org/common/feedback.html?TIMEOUT_OUTER=bc4f3b7201b7
[HTTP/2 200 OK 1732ms]
3 Likes

Should be fixed now, thanks for reporting :slight_smile:
And welcome to the forum btw :grin:

4 Likes

Awesome - you boys are hosting a CryptPad instance. :call_me_hand:

Have you included this service in your website, or at the top of the forum? Curious, as the OP was the first I've heard of it.

GM

start.garudalinux.org

3 Likes

Ok, a number of tools accessed from Garuda Welcome.

Thanks,
GM

1 Like

This may be slightly out of scope of this forum, but I'm rolling a cryptpad instance and I have the exact same issue. May I ask what it is exactly that you changed to fix this issue for your instance?

Thanks,
aiisreaq

Iirc permissions (directory) had to be adjusted :eyes:

4 Likes