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

  • SalamanderA
    4·
    2 years ago

    Type

    docker compose logs -f lemmy

    (or docker-compose) to see the logs.

    Is the last message saying that the database migration is going to be run? If so, you need to wait. It can take a few hours.

    • SalamanderA
      2·
      2 years ago

      Also, did you change the variables in the Lemmy UI environment?

      (Edit to specify, in the docker-compose.yml file the variables are now different)

      The lemmy-ui environment variables have changed, and should now look like:

  environment:
    - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
    - LEMMY_UI_LEMMY_EXTERNAL_HOST={{ domain }}
    - LEMMY_UI_HTTPS=true

      There are also other instructions that you need to follow. Are you following the release note instructions?

      See: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md#lemmy-v0170-release-2023-01-31

      • suspended@lemmy.mlOP
        2·
        2 years ago

        Thanks for this. I had no idea these existed. I’ll have to read through and make changes.

        • SalamanderA
          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?

          • suspended@lemmy.mlOP
            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.

            • SalamanderA
              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.

              • suspended@lemmy.mlOP
                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@lemmy.ml
                    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 :)