Hello! I have been struggling through a few tutorials on getting a lemmy instance to work correctly when setup with Docker. I have it mostly done, but there are various issues each time that I do not have the knowledge to properly correct. I am familiar with Docker, and already have an Oracle VPS set up on ARM64 Ubuntu. I already have portainer and an NGINX proxy set up and working okay. I have an existing lemmy instance “running” but not quite working. My best guess here would be to have someone assist with setting up the docker-compose to work with current updates/settings, as well as the config.hjson.

TIA, and I cant wait to have my own entry into the fediverse working right!

  • I eat words@group.lt
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    from the logs it seems that lemmy docker does not communicate with outside servers.

    also i have a bit different config for lemmy.hjson

    {
      # for more info about the config, check out the documentation
      # https://join-lemmy.org/docs/en/administration/configuration.html
    
      setup: {
        # username for the admin user
        admin_username: "adminuser"
        # password for the admin user
        admin_password: "adminpassword"
        # name of the site (can be changed later)
        site_name: "group.lt"
      }
    
      opentelemetry_url: "http://otel:4317"
    
    
    
      # the domain name of your instance (eg "lemmy.ml")
      hostname: "group.lt"
      # address where lemmy should listen for incoming requests
      bind: "0.0.0.0"
      # port where lemmy should listen for incoming requests
      port: 8536
      # settings related to the postgresql database
      # address where pictrs is available
    pictrs: {
        url: "http://pictrs:8080/"
        # api_key: "API_KEY"
    }
      database: {
        # name of the postgres database for lemmy
        database: "lemmy"
        # username to connect to postgres
        user: "lemmy"
        # password to connect to postgres
        password: "lemmy"
        # host where postgres is running
        host: "postgres"
        # port where postgres can be accessed
        port: 5432
        # maximum number of active sql connections
        pool_size: 5
      }
    #  # optional: email sending configuration
      email: {
    #    # hostname and port of the smtp server
        smtp_server: "postfix:25"
        smtp_from_address: "from@group.lt"
        tls_type: false
      }
    
    
    }
    

    also check in admin interface if federation is enabled and you do not blacklist instances

    (https://lemmy.bulwarkob.com/admin) and maybe you can try to enable federation debug mode for awhile

    • Jattatak@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      The differences I see are the otel link, and the TLS setting:

        # Whether the site is available over TLS. Needs to be true for federation to work.
        tls_enabled: true
      

      I see you dont have it on there, which I would assume means you cant be federated? I have added the otel link and enabled the debug mode. Federation is already enabled and the instance is set to “ALL”. Still no luck on this end. Same status, except now im not getting any log errors in the container logs (Viewed from Portainer).

      Including this in case it is a possible issue: federation enabled, host is lemmy.bulwarkob.com

      Starting http server at 0.0.0.0:8536

      • I eat words@group.lt
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        also pictrs: { url: “http://pictrs:8080/” # api_key: “API_KEY” }

        about tls setting - don’t remember why i have removed it, but group.lt federates fine. not sure about what you mean instance set to ALL.

        what about network isolation in portainer? maybe it is on?

        • Jattatak@beehaw.orgOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          I see my Pictrs appears to be the same as what you had sent over. Protainer network isolation does not appear to be in place. All are bridged networks, and I would assume access issues would be more encompassing if that were a direct correlation to the issue. Im still betting on User Error for configuration so far. Being myself, of course.

          • I eat words@group.lt
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            well probably you are right about the user error, but from the logs it seems that it cannot reach other instances - can you enter the shell of the container and check if you are able to ping/curl https://group.lt for example? and network isolation is a checkbox in portainer, according to docs.

            for the federation itself i have also experienced it not working, when my nginx config was pointing wrongly to lemmy and lemmy-ui depending on the headers.

            as i have said before - i can reach your instance from my lemmy, but don’t receive anything back.

            • Jattatak@beehaw.orgOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              It would seem it was called “Internal” as opposed to isolated on my Portainer. That appears to have been it though. I can get to other communities now. Still having disparity with posts and comments showing up, but Im hoping that will be something to update in time.