ECONNEREFUSED error about lemmy-ansible

[dessalines]

Run sudo docker-compose logs lemmy and paste the output.

[nixoye]

ERROR r2d2: FATAL: password authentication failed for user "lemmy" repeats a ton of times

[dessalines]

Okay, this means you didn't properly uninstall lemmy using those uninstall instructions. The volumes folder is still there, and its using the wrong password. You need to either follow the uninstall instructions, or run sudo docker-compose down, and delete the volumes folder manually.

The ansible auto-generates the password for you, do not change that.

[dessalines]

It has this line in bold in the instructions:

Edit that file and change the config to your liking. Note: Do not edit anything inside the {{ }} braces.

Did you edit the password in there?

[nixoye]

I ran ansible-playbook -i inventory/hosts uninstall.yml --become to uninstall like it says so im not sure how I could've uninstalled it wrong.

I didn't edit anything in the config file this time I just left everything on default

edit: I ran sudo docker-compose down and rm -rf to delete the volumes and then rebooted the server and then reinstalled it again and that fixed the issue. not sure why uninstalling with the ansible script and then reinstalling didnt fix it

[nixoye]

@dessalines after installing and running the instance should the database password and tls type be changed through the ui of the admin account? The documentation isn't very clear on the correct way to go about adding the options like where is the correct location to add strict_allowlist: true or other options.

[dessalines]

We might have an issue with our uninstall script then, I'll check it out.

There's no need to change the database password, its autogenerated and random.

You can add config blocks from that config file of options linked, but you don't need to copy the whole file, and especially not anything in the curly braces, as that bolded section clearly says.

[nixoye]

ok thanks!

last question before I close the issue. Do I add the config blocks by after the default config like this

{
  # for more info about the config, check out the documentation
  # https://join-lemmy.org/docs/en/administration/configuration.html

  database: {
    host: postgres
    password: "(redacted)"
  }
  hostname: "(redacted)"
  pictrs_url: "http://pictrs:8080"
  federation: {
    enabled: true
  }
  email: {
    smtp_server: "postfix:25"
    smtp_from_address: "noreply@(redacted)
  }
}

{

# Added Options


# Settings related to activitypub federation
# See the documentation for available config fields and descriptions:
# https://join-lemmy.org/docs/en/administration/configuration.html
{
  hostname: lemmy-alpha
  federation: {
    enabled: true
  }
  slur_filter:
    '''
    (fag(g|got|tard)?\b|cock\s?sucker(s|ing)?|ni((g{2,}|q)+|[gq]{2,})[e3r]+(s|z)?|mudslime?s?|kikes?|\bspi(c|k)s?\b|\bchinks?|gooks?|bitch(es|ing|y)?|whor(es?|ing)|\btr(a|@)nn?(y|ies?)|\b(b|re|r)tard(ed)?s?)
    '''

    # list of instances with which federation is allowed
    allowed_instances: [
      instance1.tld
      instance2.tld
      /* ... */
    ]
    # Instances which we never federate anything with (but previously federated objects are unaffected)
    blocked_instances: [
      string
      /* ... */
    ]
    # If true, only federate with instances on the allowlist and block everything else. If false
    # use allowlist only for remote communities, and posts/comments in local communities
    # (meaning remote communities will show content from arbitrary instances).
    strict_allowlist: true
    # Number of workers for sending outgoing activities. Search logs for Activity queue stats to
    # see information. If running number is consistently close to the worker_count, you should
    # increase it.
    worker_count: 64
}

I'm confused because looking at the config file linked in the docs it seems there are options inbetween settings in the {{}} cant be changed so I'm not sure where im supposed to add the options and whether or not I have to add

federation: {
    # Whether to enable activitypub federation.
    enabled: true

again to make sure strict_allowlist: true works

I think it would really help if there was a block in the docs that was ready to be copy pasted into the site configuration from the admin panel to configure the options

sorry for the dumb questions

[dessalines]

No, everything has to go within the top level {}. You can't have two hostname fields, like you've done above.

{{}} is referring to these fields.. Not sure how that could be more clear.

Those config blocks are optional, do not add them unless you know what they do, and what you want them to do.