First I'm upgrade from 1.5.10 to 1.5.11, and run migrate command. Everyting is fine, I can access console.
And after that, I'm upgrade from 1.5.11 to 1.6.0, and run migrate command. And I refresh the console, it return like the image attached.
Summary
Developers upgraded from version 1.5.11 to 1.6.0 but encountered a 404 error when trying to access the console page. To fix this issue, ensure all added environment variables are thoroughly checked and verify the migration command ran successfully. It is also recommended to have backups in case re-running the process is needed.
bluesky
Rank 2: Process
Sep 21, 2024, 08:19
This log from the server
bluesky
Rank 2: Process
Sep 21, 2024, 08:20
If I check, the api (/v1) is working fine, but I can't access the console.
bluesky
Rank 2: Process
Sep 21, 2024, 08:29
I notice this, should I add this to my docker compose ya?
D5
Sep 21, 2024, 10:20
Did the migration command run successfully?
D5
Sep 21, 2024, 10:20
What happens if you run it again?
D5
Sep 21, 2024, 10:20
Also, do you have backups?
D5
Sep 21, 2024, 10:21
Yes
D5
Sep 21, 2024, 10:21
You have upgraded it manually then?
bluesky
Rank 2: Process
Sep 21, 2024, 10:29
Yeah successfully
bluesky
Rank 2: Process
Sep 21, 2024, 10:29
Yeah, custom docker compose, manually chang version
Joshi
Sep 21, 2024, 10:47
You have to manually check all the added environment variables as well