Make CSS Multi-User Mode (first get SSL running)

which steps do I have to take to make a Community Solid Server running in public Multi-User mode ? the default seems to be local Single-User mode.

  1. what I’ve done so far

    • obtained two certs (domain and wildcard)
    • edited config/example-https-file.json with the location of the Cert and the private key
    • edited config/identity/email/default.json with the Email Credentials / Port from gmail
    • followed Using NGINX as a reverse proxy · Solid (with some minor adjustments)
    • started a very first basic testrun with community-solid-server -c @css:config/default.json -b https://solidweb.me/
  2. what I think how to proceed

    • get SSL running
    • get mashlib recipe
    • write script to populate user folders at signup (advice from @jeffz )
    • think well and work in very little steps
  3. my environment

    • Debian 8, Node 12.22, actual Nginx, CSS 1.0.0
  4. log

2021-08-29T09:36:51.067Z [Components.js] info: Initiating component discovery from /usr/lib/node_modules/@solid/community-server/
2021-08-29T09:36:51.655Z [Components.js] info: Discovered 130 component packages within 1485 packages
2021-08-29T09:36:51.657Z [Components.js] info: Initiating component loading
2021-08-29T09:36:54.614Z [Components.js] info: Registered 408 components
2021-08-29T09:36:54.617Z [Components.js] info: Loaded configs
2021-08-29T09:36:56.076Z [RootInitializer] info: Root container not found; initializing it.
2021-08-29T09:36:56.140Z [RootInitializer] info: Initialized root container with 3 resources.
2021-08-29T09:36:56.141Z [BaseHttpServerFactory] info: Starting server at http://localhost:3000/

Bildschirmfoto_2021-08-29_11-13-25

1 Like

I’ve thought it over.
the remarked “minor adjustments” might have been crucial.
in detail:

  • nginx didn’t accept the http2 parameter and the TLSv1.3 parameter
  • where do I get /etc/ssl/certs/lets-encrypt-x3-cross-signed.pem;
  • how do I create /etc/ssl/certs/dhparam.pem;

advice appreciated.

One step you forgot : wait until the new SolidOS stack is released with the adjustments for the spec-compliant auth. The current SolidOS uses solid-auth-client which will not work on CSS. Mashlib can’t currently login to CSS so you have to wait. It should only be a matter of a week or two, but you will only get frustrated if you try to make the current mashlib databrowser work in CSS.

1 Like

:wink: smile, thank you. in the meantime I make a recherche on SSL :wink:

1 Like

FYI: solved, https://solidweb.me up and running
[edit] waiting for mashlib 1.7.5

2 Likes