Unable to load Drive on new install

Williz-DMT

I've managed to get my admin user setup and 2fa but I can't load docs or the drive it gets stuck on 0%

I am getting this error in Chrome:

Image description

nginx conf:

## SPDX-FileCopyrightText: 2023 XWiki CryptPad Team <contact@cryptpad.org> and contributors
#
# SPDX-License-Identifier: AGPL-3.0-or-later

#   This file is included strictly as an example of how Nginx can be configured
#   to work with CryptPad. This example WILL NOT WORK AS IS. For best results,
#   compare the sections of this configuration file against a working CryptPad
#   installation (http server by the Nodejs process). If you are using CryptPad
#   in production and require professional support please contact sales@cryptpad.fr

server {
    listen 80;
    listen [::]:80;
    server_name cryptpad.dmt.co.uk sandbox.dmt.co.uk;

    access_log /dev/null;
    error_log /dev/null emerg;

    # Let's Encrypt webroot
    #include letsencrypt-webroot;

    # Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 http2 ssl;
    #add_header 'Content-Security-Policy' 'upgrade-insecure-requests';

    add_header 'Access-Control-Allow-Origin' '*';
    add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
    add_header 'Access-Control-Allow-Headers' 'Authorization';

    # Let's Encrypt webroot
    #include letsencrypt-webroot;

    # CryptPad serves static assets over these two domains.
    # `your-main-domain` is what users will enter in their address bar.
    # Privileged computation such as key management is handled in this scope
    # UI content is loaded via the `your-sandbox-domain`.
    # "Content Security Policy" headers prevent content loaded via the sandbox
    # from accessing privileged information.
    # This setup allows to take advantage of CryptPad's sandboxing techniques.
    # In the event of an XSS vulnerability in CryptPad's front-end code
    # this will limit the amount of information accessible to attackers.
    server_name cryptpad.dmt.co.uk sandbox.dmt.co.uk;

    # You'll need to Set the path to your certificates and keys here
    # IMPORTANT: this config is intended to serve assets for at least two domains
    # (your main domain and your sandbox domain). As such, you'll need to generate a single SSL certificate
    # that includes both domains in order for things to work as expected.
    ssl_certificate /etc/ssl/certificate.pem;
    ssl_certificate_key /etc/ssl/privatekey.pem;

    # diffie-hellman parameters are used to negotiate keys for your session
    # generate strong parameters using the following command
    ssl_dhparam /etc/nginx/dhparam.pem; # openssl dhparam -out /etc/nginx/dhparam.pem 4096

    # Speeds things up a little bit when resuming a session
    ssl_session_timeout 1d;
    ssl_session_cache shared:MozSSL:10m;
    ssl_session_tickets off;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;

    # HSTS (ngx_http_headers_module is required) (63072000 seconds)
    add_header Strict-Transport-Security "max-age=63072000; includeSubDomains" always;

    # OCSP stapling
    ssl_stapling on;
    ssl_stapling_verify on;

    # verify chain of trust of OCSP response using Root CA and Intermediate certs
    ssl_trusted_certificate /etc/ssl/certs/ca-certificates.crt;

    # replace with the IP address of your resolver
    resolver 8.8.8.8 8.8.4.4 1.1.1.1 1.0.0.1 9.9.9.9 149.112.112.112 208.67.222.222 208.67.220.220;

    location / {
        proxy_pass            http://localhost:3000;
        proxy_set_header      X-Real-IP $remote_addr;
        proxy_set_header      Host $host;
        proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
        client_max_body_size  150m;

        proxy_http_version    1.1;
        proxy_set_header      Upgrade $http_upgrade;
        proxy_set_header      Connection upgrade;
    }

    location ^~ /cryptpad_websocket {
        proxy_pass            http://localhost:3003;
        proxy_set_header      X-Real-IP $remote_addr;
        proxy_set_header      Host $host;
        proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_http_version    1.1;
        proxy_set_header      Upgrade $http_upgrade;
        proxy_set_header      Connection upgrade;
    }
}

and this is my config.js:

// SPDX-FileCopyrightText: 2023 XWiki CryptPad Team <contact@cryptpad.org> and contributors
//
// SPDX-License-Identifier: AGPL-3.0-or-later

/*  DISCLAIMER:

    There are two recommended methods of running a CryptPad instance:

    1. Using a standalone nodejs server without HTTPS (suitable for local development)
    2. Using NGINX to serve static assets and to handle HTTPS for API server's websocket traffic

    We do not officially recommend or support Apache, Docker, Kubernetes, Traefik, or any other configuration.
    Support requests for such setups should be directed to their authors.

    If you're having difficulty difficulty configuring your instance
    we suggest that you join the project's Matrix channel.

    If you don't have any difficulty configuring your instance and you'd like to
    support us for the work that went into making it pain-free we are quite happy
    to accept donations via our opencollective page: https://opencollective.com/cryptpad

*/
module.exports = {
/*  CryptPad is designed to serve its content over two domains.
 *  Account passwords and cryptographic content is handled on the 'main' domain,
 *  while the user interface is loaded on a 'sandbox' domain
 *  which can only access information which the main domain willingly shares.
 *
 *  In the event of an XSS vulnerability in the UI (that's bad)
 *  this system prevents attackers from gaining access to your account (that's good).
 *
 *  Most problems with new instances are related to this system blocking access
 *  because of incorrectly configured sandboxes. If you only see a white screen
 *  when you try to load CryptPad, this is probably the cause.
 *
 *  PLEASE READ THE FOLLOWING COMMENTS CAREFULLY.
 *
 */

/*  httpUnsafeOrigin is the URL that clients will enter to load your instance.
 *  Any other URL that somehow points to your instance is supposed to be blocked.
 *  The default provided below assumes you are loading CryptPad from a server
 *  which is running on the same machine, using port 3000.
 *
 *  In a production instance this should be available ONLY over HTTPS
 *  using the default port for HTTPS (443) ie. https://cryptpad.fr
 *  In such a case this should be also handled by NGINX, as documented in
 *  cryptpad/docs/example.nginx.conf (see the $main_domain variable)
 *
 */
    httpUnsafeOrigin: 'https://cryptpad.dmt.co.uk',

/*  httpSafeOrigin is the URL that is used for the 'sandbox' described above.
 *  If you're testing or developing with CryptPad on your local machine then
 *  it is appropriate to leave this blank. The default behaviour is to serve
 *  the main domain over port 3000 and to serve the sandbox content over port 3001.
 *
 *  This is not appropriate in a production environment where invasive networks
 *  may filter traffic going over abnormal ports.
 *  To correctly configure your production instance you must provide a URL
 *  with a different domain (a subdomain is sufficient).
 *  It will be used to load the UI in our 'sandbox' system.
 *
 *  This value corresponds to the $sandbox_domain variable
 *  in the example nginx file.
 *
 *  Note that in order for the sandboxing system to be effective
 *  httpSafeOrigin must be different from httpUnsafeOrigin.
 *
 *  CUSTOMIZE AND UNCOMMENT THIS FOR PRODUCTION INSTALLATIONS.
 */
     httpSafeOrigin: "https://sandbox.dmt.co.uk",

/*  httpAddress specifies the address on which the nodejs server
 *  should be accessible. By default it will listen on localhost
 *  (IPv4 & IPv6 if enabled). If you want it to listen on
 *  a specific address, specify it here. e.g '192.168.0.1'
 *
 */
    //httpAddress: 'localhost',

/*  httpPort specifies on which port the nodejs server should listen.
 *  By default it will serve content over port 3000, which is suitable
 *  for both local development and for use with the provided nginx example,
 *  which will proxy websocket traffic to your node server.
 *
 */
    //httpPort: 3000,

/*  httpSafePort purpose is to emulate another origin for the sandbox when
 *  you don't have two domains at hand (i.e. when httpSafeOrigin not defined).
 *  It is meant to be used only in case where you are working on a local
 *  development instance. The default value is your httpPort + 1.
 *
 */
    //httpSafePort: 3001,

/*  Websockets need to be exposed on a separate port from the rest of
 *  the platform's HTTP traffic. Port 3003 is used by default.
 *  You can change this to a different port if it is in use by a
 *  different service, but under most circumstances you can leave this
 *  commented and it will work.
 *
 *  In production environments, your reverse proxy (usually NGINX)
 *  will need to forward websocket traffic (/cryptpad_websocket)
 *  to this port.
 *
 */
     //websocketPort: 3003,

/*  CryptPad will launch a child process for every core available
 *  in order to perform CPU-intensive tasks in parallel.
 *  Some host environments may have a very large number of cores available
 *  or you may want to limit how much computing power CryptPad can take.
 *  If so, set 'maxWorkers' to a positive integer.
 */
    // maxWorkers: 4,

    /* =====================
     *       Sessions
     * ===================== */

    /*  Accounts can be protected with an OTP (One Time Password) system
     *  to add a second authentication layer. Such accounts use a session
     *  with a given lifetime after which they are logged out and need
     *  to be re-authenticated. You can configure the lifetime of these
     *  sessions here.
     *
     *  defaults to 7 days
     */
    //otpSessionExpiration: 7*24, // hours

    /*  Registered users can be forced to protect their account
     *  with a Multi-factor Authentication (MFA) tool like a TOTP
     *  authenticator application.
     *
     *  defaults to false
     */
    //enforceMFA: false,

    /* =====================
     *       Privacy
     * ===================== */

    /*  Depending on where your instance is hosted, you may be required to log IP
     *  addresses of the users who make a change to a document. This setting allows you
     *  to do so. You can configure the logging system below in this config file.
     *  Setting this value to true will include a log for each websocket connection
     *  including this connection's unique ID, the user public key and the IP.
     *  NOTE: this option requires a log level of "info" or below.
     *
     *  defaults to false
     */
    //logIP: false,

    /* =====================
     *         Admin
     * ===================== */

    /*
     *  CryptPad contains an administration panel. Its access is restricted to specific
     *  users using the following list.
     *  To give access to the admin panel to a user account, just add their public signing
     *  key, which can be found on the settings page for registered users.
     *  Entries should be strings separated by a comma.
     *  adminKeys: [
     *      "[cryptpad-user1@my.awesome.website/YZgXQxKR0Rcb6r6CmxHPdAGLVludrAF2lEnkbx1vVOo=]",
     *      "[cryptpad-user2@my.awesome.website/jA-9c5iNuG7SyxzGCjwJXVnk5NPfAOO8fQuQ0dC83RE=]",
     *  ]
     *
     */
    adminKeys: [

    ],

    /* =====================
     *        STORAGE
     * ===================== */

    /*  Pads that are not 'pinned' by any registered user can be set to expire
     *  after a configurable number of days of inactivity (default 90 days).
     *  The value can be changed or set to false to remove expiration.
     *  Expired pads can then be removed using a cron job calling the
     *  `evict-inactive.js` script with node
     *
     *  defaults to 90 days if nothing is provided
     */
    //inactiveTime: 90, // days

    /*  CryptPad archives some data instead of deleting it outright.
     *  This archived data still takes up space and so you'll probably still want to
     *  remove these files after a brief period.
     *
     *  cryptpad/scripts/evict-archived.js is intended to be run daily
     *  from a crontab or similar scheduling service.
     *
     *  The intent with this feature is to provide a safety net in case of accidental
     *  deletion. Set this value to the number of days you'd like to retain
     *  archived data before it's removed permanently.
     *
     *  defaults to 15 days if nothing is provided
     */
    //archiveRetentionTime: 15,

    /*  It's possible to configure your instance to remove data
     *  stored on behalf of inactive accounts. Set 'accountRetentionTime'
     *  to the number of days an account can remain idle before its
     *  documents and other account data is removed.
     *
     *  Leave this value commented out to preserve all data stored
     *  by user accounts regardless of inactivity.
     */
     //accountRetentionTime: 365,

    /*  Starting with CryptPad 3.23.0, the server automatically runs
     *  the script responsible for removing inactive data according to
     *  your configured definition of inactivity. Set this value to `true`
     *  if you prefer not to remove inactive data, or if you prefer to
     *  do so manually using `scripts/evict-inactive.js`.
     */
    //disableIntegratedEviction: true,


    /*  Max Upload Size (bytes)
     *  this sets the maximum size of any one file uploaded to the server.
     *  anything larger than this size will be rejected
     *  defaults to 20MB if no value is provided
     */
    //maxUploadSize: 20 * 1024 * 1024,

    /*  Users with premium accounts (those with a plan included in their customLimit)
     *  can benefit from an increased upload size limit. By default they are restricted to the same
     *  upload size as any other registered user.
     *
     */
    //premiumUploadSize: 100 * 1024 * 1024,

    /* =====================
     *   DATABASE VOLUMES
     * ===================== */

    /*
     *  CryptPad stores each document in an individual file on your hard drive.
     *  Specify a directory where files should be stored.
     *  It will be created automatically if it does not already exist.
     */
    filePath: './datastore/',

    /*  CryptPad offers the ability to archive data for a configurable period
     *  before deleting it, allowing a means of recovering data in the event
     *  that it was deleted accidentally.
     *
     *  To set the location of this archive directory to a custom value, change
     *  the path below:
     */
    archivePath: './data/archive',

    /*  CryptPad allows logged in users to request that particular documents be
     *  stored by the server indefinitely. This is called 'pinning'.
     *  Pin requests are stored in a pin-store. The location of this store is
     *  defined here.
     */
    pinPath: './data/pins',

    /*  if you would like the list of scheduled tasks to be stored in
        a custom location, change the path below:
    */
    taskPath: './data/tasks',

    /*  if you would like users' authenticated blocks to be stored in
        a custom location, change the path below:
    */
    blockPath: './block',

    /*  CryptPad allows logged in users to upload encrypted files. Files/blobs
     *  are stored in a 'blob-store'. Set its location here.
     */
    blobPath: './blob',

    /*  CryptPad stores incomplete blobs in a 'staging' area until they are
     *  fully uploaded. Set its location here.
     */
    blobStagingPath: './data/blobstage',

    decreePath: './data/decrees',

    /* CryptPad supports logging events directly to the disk in a 'logs' directory
     * Set its location here, or set it to false (or nothing) if you'd rather not log
     */
    logPath: './data/logs',

    /* =====================
     *       Debugging
     * ===================== */

    /*  CryptPad can log activity to stdout
     *  This may be useful for debugging
     */
    logToStdout: true,

    /* CryptPad can be configured to log more or less
     * the various settings are listed below by order of importance
     *
     * silly, verbose, debug, feedback, info, warn, error
     *
     * Choose the least important level of logging you wish to see.
     * For example, a 'silly' logLevel will display everything,
     * while 'info' will display 'info', 'warn', and 'error' logs
     *
     * This will affect both logging to the console and the disk.
     */
    logLevel: 'silly',

    /*  clients can use the /settings/ app to opt out of usage feedback
     *  which informs the server of things like how much each app is being
     *  used, and whether certain clientside features are supported by
     *  the client's browser. The intent is to provide feedback to the admin
     *  such that the service can be improved. Enable this with `true`
     *  and ignore feedback with `false` or by commenting the attribute
     *
     *  You will need to set your logLevel to include 'feedback'. Set this
     *  to false if you'd like to exclude feedback from your logs.
     */
    logFeedback: true,

    /*  CryptPad supports verbose logging
     *  (false by default)
     */
    verbose: true,

    /*  Surplus information:
     *
     *  'installMethod' is included in server telemetry to voluntarily
     *  indicate how many instances are using unofficial installation methods
     *  such as Docker.
     *
     */
    installMethod: 'unspecified',
};

Any help is greatly appreciated

Mathilde

Hello,

Your configuration files looks sound to me. However, have you checked if the CryptPad service is running properly?

You can do so with systemctl:

sudo systemctl status cryptpad.service

Williz-DMT

Hey Mathilde, the service is running using Pm2:

Image description

I had issues setting it as a daemon as it would look like it was running when it wasn't but seems to be fine under PM2 as I can login and authenticate against 2fa but anything past that like trying to open the drive or a document just hangs after building the interface and then times out:

Image description

Any help is appreciated as I'm scratching my head in confusion.

Mathilde

Thanks for your reply.

You can take a look at your Nginx error logs and CryptPad logs itself.

Williz-DMT

Mathilde

Thank you but even with the silly level set on logs I'm not getting much useful out from Cryptpad:

/root/.pm2/logs/server-out.log last 15 lines:
0|server   | ["INFO","2025-03-18T09:34:23.529Z","WEBSERVER_LISTENING",{"origin":"https://cryptpad.dmt.co.uk/"}]
0|server   | ["INFO","2025-03-18T09:34:24.036Z","NO_CUSTOMIZE_FOLDER",{"message":"CryptPad is customizable, see customize.dist/readme.md for details"}]
0|server   | ["INFO","2025-03-18T09:34:24.039Z","WEBSERVER_LISTENING",{"origin":"https://cryptpad.dmt.co.uk/"}]
0|server   | ["INFO","2025-03-18T09:34:24.583Z","NO_CUSTOMIZE_FOLDER",{"message":"CryptPad is customizable, see customize.dist/readme.md for details"}]
0|server   | ["INFO","2025-03-18T09:34:24.585Z","WEBSERVER_LISTENING",{"origin":"https://cryptpad.dmt.co.uk/"}]
0|server   | ["INFO","2025-03-18T09:35:13.218Z","NO_CUSTOMIZE_FOLDER",{"message":"CryptPad is customizable, see customize.dist/readme.md for details"}]
0|server   | ["INFO","2025-03-18T09:35:13.220Z","WEBSERVER_LISTENING",{"origin":"https://cryptpad.dmt.co.uk/"}]
0|server   | ["INFO","2025-03-18T09:35:13.228Z","WEBSOCKET_LISTENING",{"port":3003}]
0|server   | ["INFO","2025-03-18T09:35:13.433Z","UPDATING_FRESH_KEY",1742290513433]
0|server   | ["SILLY","2025-03-18T09:35:13.438Z","HK_LOADING","LOADING HISTORY_KEEPER MODULE"]
0|server   | ["VERBOSE","2025-03-18T09:35:13.438Z","HK_ID","History keeper ID: 164526f23949357f"]
0|server   | ["INFO","2025-03-18T09:35:13.681Z","WORKER_ENV_UPDATE","Updating HTTP workers with latest state"]
0|server   | ["INFO","2025-03-18T09:35:13.683Z","WORKER_CACHE_FLUSH","Instructing HTTP workers to flush cache"]
0|server   | ["INFO","2025-03-18T09:35:14.036Z","SERVER_TELEMETRY",{"version":"2024.12.0","installMethod":"unspecified","httpUnsafeOrigin":"https://cryptpad.dmt.co.uk","httpSafeOrigin":"https://sandbox.dmt.co.uk","consentToContact":false}]
0|server   | ["FEEDBACK","2025-03-18T09:39:46.761Z","TIMEOUT_OUTER",""]

It does seem like there is an issue looking at the nginx logs though relating to the api trying to load over 127.0.0.1 I think? Is there a way to change this and update the IP/hostname it's using?

2025/03/18 10:10:26 [error] 499425#499425: *1499 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /customize/pre-loading.js?ver=1.1 HTTP/1.1", upstream: "http://127.0.0.1:3000/customize/pre-loading.js?ver=1.1", host: "cryptpad.dmt.co.uk", referrer: "https://cryptpad.dmt.co.uk/"
2025/03/18 10:10:26 [error] 499423#499423: *1507 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /customize/application_config.js?ver=2024.12.0-1742290513433 HTTP/1.1", upstream: "http://127.0.0.1:3000/customize/application_config.js?ver=2024.12.0-1742290513433", host: "cryptpad.dmt.co.uk", referrer: "https://cryptpad.dmt.co.uk/"


2025/03/18 10:10:51 [error] 499423#499423: *1583 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /customize/CryptPad_logo.svg HTTP/1.1", upstream: "http://127.0.0.1:3000/customize/CryptPad_logo.svg", host: "cryptpad.dmt.co.uk"
2025/03/18 10:10:51 [error] 499424#499424: *1633 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /customize/favicon/main-favicon.png?ver=2024.12.0-1742290513433 HTTP/1.1", upstream: "http://127.0.0.1:3000/customize/favicon/main-favicon.png?ver=2024.12.0-1742290513433", host: "cryptpad.dmt.co.uk"
2025/03/18 10:10:51 [error] 499427#499427: *1626 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /api/instance?ver=2024.12.0-1742290513433 HTTP/1.1", upstream: "http://127.0.0.1:3000/api/instance?ver=2024.12.0-1742290513433", host: "cryptpad.dmt.co.uk", referrer: "https://sandbox.dmt.co.uk/"
2025/03/18 10:10:52 [error] 499426#499426: *1779 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /customize/src/less2/include/icons.less?ver=2024.12.0-1742290513433 HTTP/1.1", upstream: "http://127.0.0.1:3000/customize/src/less2/include/icons.less?ver=2024.12.0-1742290513433", host: "sandbox.dmt.co.uk", referrer: "https://sandbox.dmt.co.uk/drive/inner.html?ver=2024.12.0-1742290513433"
2025/03/18 10:10:53 [error] 499428#499428: *1908 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.108.10, server: cryptpad.dmt.co.uk, request: "GET /lib/diff-dom/diffDOM.js?ver=2024.12.0-1742290513433 HTTP/1.1", upstream: "http://127.0.0.1:3000/lib/diff-dom/diffDOM.js?ver=2024.12.0-1742290513433", host: "cryptpad.dmt.co.uk", referrer: "https://sandbox.dmt.co.uk/"

Mathilde

Couldn't it be a networking issue on your virtual machine? A firewall? Does your VM support IPv4? IPv6? Both?

Maybe you want to check this and then maybe give a try the httpAddress parameter in your config.js?

On another side, where do your TLS certificates comes from? Are they self-generated? Did you follow the instruction mentioning there should be one valid for both domains at the same time?