blank page after registration credentials

Gabx

Cryptpad is up and running.
After inserted registration username and passwords credentials cryptpad shows a blank page.

Image description

Cryptpad looks poor on logs and i found just this WARN in the logs:

["WARN","2022-12-07T20:02:31.466Z","NODEJS_OLD_VERSION",{"message":"The CryptPad development team recommends using at least NodeJS v16.14.2","currentVersion":"v14.21.1"}] ["INFO","2022-12-07T20:02:31.488Z","UPDATING_FRESH_KEY",1670443351488]

I have upgraded nodejs to v16.18.1 but still no luck !

Mathilde

Hello!

Thanks for opening a dedicated topic for this new issue. 😊

As explained in our admin guide, upon installation you have to head over https://cryptpad.virebent.art:4433/checkup/ and check whatever warning & errors.

Gabx

Cryptpad is now on a dedicated VPS on https default port and available at this address.
https://cryptpad.virebent.art.
Thank you for your help.

Gabx

The https:///cryptpad.virebent.art/checkup/ link indicates that there are still errors. For example I added adminEmail and adminKeys and still indicates errors about it.
But also this Error:
The content served by the directory /block/ should have an X-Content-Type-Options header with a nosniff value.

when your configuration file has this

position  ~ /block/ {
    **add_header X-Content-Type-Options nosniff**;
    add_header Max-age cache control=0;
    try_files $uri =404;
}

Mathilde

Hello!

Can you try restarting Nginx?

sudo systemctl restart nginx.service

As well, after setting up the adminKey you have to restart CryptPad:

sudo systemct restart cryptpad.service

Hope this helps! 😊

Gabx

I ran npm run build and reduced the errors to 41. That leaves 7.
2 serious errors and 5 warnings.
the 2 errors are for the nginx header for the /block directory I mentioned before while the other is for the file /block/placeholder.txt. (?)

Warnings complain about the absence of adminEmail, adminKeys (as already mentioned it's been written in config/config.js).
To these we add another warning for lack of "support ticket functionality" that has been added with key generated by node . /scripts/generate-admin-keys.js and then inserted in 'supportMailboxPublicKey'.

The other two warnings concern the Privacy Policy and Terms of service .

# systemctl restart cryptpad.service nginx.service

This is config.js:

https://cryptpad.virebent.art/pad/#/2/pad/edit/88wOcuEsyMOUvVctPirBih1R/

Mathilde

Hello!

I see nothing wrong about your config.js file, however is CryptPad running properly on your server? A restart should suffice for it to acknowledge the new key.

In what directory are you running CryptPad? Did you updated the cryptpad.service file accordingly?

Best wishes,