I’m trying to stand up an instance of Cryptpad on a VPS. I have followed 3 different articles to try to get my way through it. They all end in the same result, browser errors and I see the Cryptpad logo with “loading” and that’s it.

Browser error is always some variation of this:

NOTE: Actual error I receive right now, blurring out my domain name

And I don’t know enough of HTML and JS to figure this out beyond it’s missing something it’s looking for. I did get it to load once, where the icons for the various apps loaded, but clicking on any of them yielded similar errors.

The tutorials I tried (formatting and reloading the OS between attempts):

  1. Official documentation
  2. How To Forge
  3. Make Tech Easy

Option 3 was the clearest tutorial by far, but I still ran into issues. I followed each step exactly and still can’t seem to figure this out. Does anyone have a second set of eyes and point out what I’m clearly doing wrong? I don’t think I missed any steps in my multitude of attempts, but clearly I am.

I know I can pay someone to host it or use a public instance, but I’d really like to know what I missed so I can learn from it.

    • Father_Redbeard@lemmy.mlOP
      1·
      1 year ago

      Just running node as that is what the instructions mentioned. Do you have a link or something I can search for that might lead me to how I should replace one with the other?

      The diagnosis link goes nowhere for me. I double checked my DNS records on Cloudflare:

      1. A record for root domain pointing to VPS target, not proxied through CF
      2. A record for subdomain pointing to VPS target, not proxied through CF

      From my understanding I don’t need any others? At least I think I read that right.

      Hmm. We’re having trouble finding that site. We can’t connect to the server at cryptpad.mydomain.com. If you entered the right address, you can:

      • Try again later
      • Check your network connection
      • Check that Firefox has permission to access the web (you might be connected but behind a firewall)
      • Mylemmy@lemmy.ml
        2·
        1 year ago

        Sounds like the server isn’t running or serving.

        In the documentation search for "forever"as they link it. Then just run the same command they have but foreverjs instead of node