Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MA
majorswitcher @lemmy.one
Posts 2
Comments 7
issues with lemmy server migration
  • seems like I was nearly there :) yes you copy the volumes folder, and change ownership to those folders. But then the db has the password from your previous installation stored, so you need to change that. Copy the password from your docker-compose.yml file, and add it to the database like this: docker exec -i FOLDERNAME_postgres_1 psql -U lemmy -c "alter user lemmy with password 'bleh'"

    (from https://join-lemmy.org/docs/en/administration/backup_and_restore.html)

  • postfix issues, possible to use sendgrid?
  • after installing with ansible, change the docker-compose.yml file on you server passing the api in the ENV variable:

    the postfix section now looks like this

      postfix:
        image: mwader/postfix-relay
        environment:
          - POSTFIX_myhostname=[yourdomain.tld]
          - POSTFIX_inet_protocols=ipv4
          - POSTFIX_smtp_sasl_auth_enable=yes
          - POSTFIX_smtp_sasl_password_maps=static:apikey:[api-key]
          - POSTFIX_smtp_tls_security_level=may
          - POSTFIX_smtp_sasl_security_options=noanonymous
          - POSTFIX_relayhost=smtp.sendgrid.net:587
          - OPENDKIM_DOMAINS=[yourdomain.tld]
        restart: "always"
  • Lemmy Support @lemmy.ml majorswitcher @lemmy.one

    issues with lemmy server migration

    I'm trying to migrate lemmyfly.org to a server with more capacity at a different provider. From the current running OK server I've downloaded the volumes folder using rsync. The new server is installed using ansible with success, all containers are up and running.

    Then I stop the containers, rm volumes, copy the volumes from the backup location to the new server.

    Now when trying to start the containers, the pictrs and postgres containers have errors. I noticed the volumes folder now have different owner (staff in stead of root). So I manually changed ownership of those folders to root. Now those containers can start ok. But now the lemmy container can't authenticate with postgres, although the password is all the same in the config files.

    There must be an easier way to restore a backup. What am I missing ?

    1
    do I need to manually add all instances that I want future members of my instance to be able to subscribe to ?
  • I see! I just need to keep my Allowed list empty :) Don't really understand the different visibility of comments yet. I can see your comments from my lemmy.one account. but they don't show up on my own instance. Bit hard to keep track of posts and comments, if I need a second account on a different instance to see replies ?

  • postfix issues, possible to use sendgrid?
  • thanks! got it working now. In SendGrip generated an api key, at - POSTFIX_smtp_sasl_password_maps=static:smtp_username:smtp_password filled in apikey:[theapikey] and relayhost=smtp.sendgrid.net:587

    also add a verified From address in SendGrid, which is added in your lemmy.hjson email.smtp_from_address

  • Lemmy Support @lemmy.ml majorswitcher @lemmy.one

    postfix issues, possible to use sendgrid?

    I have issues using postfix on my digitalocean droplet (they block the smtp port). Is it possible to setup using SendGrid for the email verification and notifications ?

    10