While running this command on my DigitalOcean install:
$ sudo systemctl restart forem-traefik.service
Enter fullscreen mode
Ex...
For further actions, you may consider blocking this person and/or reporting abuse
Hey @tien thanks for trying out Selfhost!
Can you show us some logs from
forem-container.service
? That's what handles retrieving the Forem container, and if there are issues pulling that container, nothing will really work.Hi, thanks for your fast comment.
This is logs from
forem-container.service
.Ok, that's fine; looks like it's correctly pulling down the
quay.io/forem/forem:latest
container.Can you show your logs for
forem-rails.service
as well? Looks like it's restarting, wonder if there are any obvious errors in there.Hi, this is my logs for
forem-rails.service
:)Not sure what's going on there - can you reboot your droplet and see if you're still getting errors on
forem-rails.service
? Thanks!Thanks! But unfortunately it still doesn't work :(.
I recently ran into this same issue when building the Docker config at github/forem/forem.
This is not very helpful, but my temporary "fix" was to comment out the offending
index_exists?
invocations in that particular migration and then everything was ok..ish:Hi, thank you, I will try :)
With this PR, now you should not face any such migration issues.
Hi, thank you so much! :)
were you able to fix? can you explain what have you done? @tien
how to use this PR solve this issue? @akhil