Broken after update

Question

Broken after update

Closed this issue 3 years ago · 11 comments

Answer 1 · 2022-01-06T14:00:14.000Z

it auto logs in
can't make a user
can't do anything really
tried deleting the docker images and git clone from scratch
this is the result.
any ideas on how to fix?

Answer 2 · 2022-01-07T01:22:37.000Z

Hey 👋 From what version did you update? I've testing updating from the previous version (v1.7.0) and deploying from scratch (after deleting all docker images, volumes and cloning the repo from scratch) and it's working for me.

Could you show me logs generated by the backend container (which seems to be at fault here). You can do so by running docker logs xss-catcher_backend_1.

Answer 3 · 2022-01-07T01:40:13.000Z

gprime31 commented 3 years ago

Answer 4 · 2022-01-07T01:41:27.000Z

not sure what version i updated from... it's been awhile.
But i removed all docker containers and images and re git cloned and same result.
so no idea what is going on.

Answer 5 · 2022-01-07T02:00:52.000Z

Hmm seems like it's the database container which is having trouble starting 🤔 I believe running docker logs xss-catcher_db_1 will give us the reason why it is not working!

Answer 6 · 2022-01-07T02:04:36.000Z

gprime31 commented 3 years ago

Answer 7 · 2022-01-07T02:05:11.000Z

Thanks for all the help btw. :)

Answer 8 · 2022-01-07T02:06:55.000Z

shoulden't this update when I deleted everything and installed fresh?
postgresql is part of the docker pull right?

Answer 9 · 2022-01-07T02:57:53.000Z

Yes, actually the problem comes from the fact that the postgres version in the db container was updated, but the data was created using postgres13, and this is still persisted in /var/lib/docker/volumes. That's why I hardcoded the postgres version to 14 in the latest update (I didn't know better before 😅).

You have two ways to fix this:
A) First stop XSS-Catcher using make stop, then run docker volume rm xss-catcher_xss-db. This will effectively delete the XSS-Catcher data and allow you to start from a clean postgres14 database using make start 🙂 However, this will delete your data.
B) If your data is important and you cannot just delete the database, you can go into docker-compose.yml and change line 9 to postgres:13.5-alpine3.15. Then, run make update. This will allow you to run on postgres13 instead of 14.

If the data is not important, I would personally go for option A.

Let me know if it works!

Answer 10 · 2022-01-07T03:16:25.000Z

Option A worked perfectly.
Thanks very much!!!!

Answer 11 · 2022-01-07T03:20:12.000Z

Glad to hear that! My pleasure! 🎉 🥳