I made the two version number changes to my docker-compose.yml file. Ran Docker Compose Down then Docker Compose Up -D.

Visit https://beehaw.org and you’ll see the error in your browser:

404: FetchError: request to http://0.0.0.0:8536/api/v3/site

  • suspendedOP
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    I’ve followed all of those instructions, making the necessary changes, and now I’m getting this error:

    404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy

    • Salamander@mander.xyz
      link
      fedilink
      arrow-up
      2
      ·
      2 years ago

      If you go to your lemmy directory and type docker-compose logs -f lemmy, what does it say?

      Can you share your docker-compose.yml file, removing the database password and any other private information?

      • suspendedOP
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        thread ‘main’ panicked at ‘Failed to load settings file: LemmyError { message: None, inner: TrailingCharacters at 99:4 at “email: {\n# #”, context: “SpanTrace” }’, crates/utils/src/settings/mod.rs:18:33

        I’ll see about getting you the docker-compose.yml file.

        • Salamander@mander.xyz
          link
          fedilink
          arrow-up
          4
          ·
          2 years ago

          Oh, that looks like an error in your lemmy.hjson settings file. If you share that one too with the passwords redacted I can check.

          • suspendedOP
            link
            fedilink
            arrow-up
            4
            ·
            2 years ago

            I just found the typo in that file and fixed it. Site is back up and running! Thank you for your help!

            • nameasd
              link
              fedilink
              arrow-up
              1
              ·
              2 years ago

              what the typo did you have? i have the same problem

              • nameasd
                link
                fedilink
                arrow-up
                1
                ·
                2 years ago

                I find solves: when u updated, dont forget check lemmy-ui environment variables

                I skipped second word LEMMY:

                LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536

                LEMMY_UI_LEMMY_EXTERNAL_HOST={{ domain }} \

                when i restore this -> all work fine :)