I have tried the docker, ansible, and scratch methods. I have been troubleshooting for a month now. I have gotten nowhere. I need someone to help walk me through how to deploy a lemmy server because the guides are absolute trash.

Please help. I’m wasting money running this VPS and for literally nothing.

Edit: So, I’ve tried the ansible method, but I can’t access my server this way. It just keeps saying “UNREACHABLE”. I have generated a dozen keys, none of them work. I have NO PROBLEMS with ssh in Putty. I can use Putty all day. Putty works fine using my ssh key. Ansible does not. No amount of new keys has made any difference. I have countless keys in my stupid droplet because of this hacky garbage.

  • Max-P@lemmy.max-p.me
    4·
    1 year ago

    Hmm, I see. In that case I’m afraid you will definitely need to get familiar with a lot of stuff really fast, because there’s a lot of rough edges right now. It’s super beta software after all. Even the admins of lemmy.world and beehaw.org are hitting pretty complex problems that needs a lot of digging. You’ll definitely need to become fairly intimate with how Lemmy works under the hood if you want to scale up to hundreds of users. Especially the pict-rs storage as it grows pretty fast. People have been having to migrate it to object-storage.

    You can always join the install support Matrix room for additional help: https://matrix.to/#/#lemmy-support-new-instance:discuss.online. Or the whole Lemmy Matrix Space at #lemmy-space:matrix.org.

    I don’t want to demotivate you or anything - it’s a great learning experience! But beware you’ll definitely have to troubleshoot and spend some time to keep it running smoothly. It’s far from set and forget at the moment, particularly at scale.

    But one thing at a time, lets see how Ansible does on a blank droplet, and lets figure out how to fix your Ansible problems first before getting into manual installs and scaling up.

    • ZMonster@lemmy.worldOP
      1·
      1 year ago

      I can’t even get that far.

      I used a different PC, installed WSL, created a new rsa key stored at “/home/wsl/.ssh”. Added the public key to my DO droplet. Rebuilt the droplet to ensure that the keys transferred.

      ssh -i /home/wsl/.ssh/id-rsa root@ip

Permission denied (public key)

      every 👏 fucking 👏 time 👏

      I would love to try the ansible method, but apparently I’m the only person to not just instinctively know how to ssh from another pc. I’ve searched for a reference to this and none of them help. Any advice?

      • Max-P@lemmy.max-p.me
        1·
        1 year ago

        I think that’s supposed to be an underscore in id_rsa, not id-rsa, unless you changed it from the default.

        • ZMonster@lemmy.worldOP
          1·
          1 year ago

          I figured out the problem, digital ocean was only applying the top RSA key, which is my Putty key. The keys I added to DO via WSL were not getting added to the authorized key list. So I added my key to the authorized keys file and it worked. Well, it let ansible access the server. I’m having other issues but will work on them later.