Skip to content
This repository has been archived by the owner on Aug 17, 2023. It is now read-only.

502 bad gateway error on site #113

Open
rudietuesdays opened this issue Oct 21, 2020 · 0 comments
Open

502 bad gateway error on site #113

rudietuesdays opened this issue Oct 21, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request priority High priority issues
Milestone

Comments

@rudietuesdays
Copy link
Contributor

From @jheretic : "I suspect it might have been a memory issue on the VM, and the OOM killer got it. Memory usage seems stable so far, so we're not likely to get more info unless it happens again. I'm going to suggest modifying the default docker-compose setup so that containers auto-restart on failure, and look into the possibility of adding prometheus metrics if that's easy to do. "

@jheretic jheretic added the enhancement New feature or request label Oct 22, 2020
@jheretic jheretic added this to the MVP milestone Oct 22, 2020
@critzo critzo added the priority High priority issues label Nov 18, 2020
@jheretic jheretic self-assigned this Nov 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request priority High priority issues
Projects
None yet
Development

No branches or pull requests

3 participants