Lemmy Support

4650 readers

1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

[RESOLVED] Getting a 404 Fetch Error When Attempting to Upgrade to 0.17.0 (lemmy.ml)

submitted 2 years ago by suspended@lemmy.ml to c/lemmy_support@lemmy.ml

12 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] suspended@lemmy.ml 1 points 2 years ago (1 children)

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

[–] Sal@mander.xyz 2 points 2 years ago (1 children)

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.ml 1 points 2 years ago (1 children)

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.

[–] Sal@mander.xyz 4 points 2 years ago (1 children)

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.ml 4 points 2 years ago (3 children)

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

[–] picoblaanket@lemmy.ml 3 points 2 years ago

Nice, that is a good feeling.

[–] Sal@mander.xyz 3 points 2 years ago

Ah, great! Congratz!

[–] SOVERSHENEN@lemmy.ml 1 points 2 years ago (1 children)

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

[–] SOVERSHENEN@lemmy.ml 1 points 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 :)