502 Error on fresh Gitlab Instance
After Setup, I get a 502 when i access the ip with a browser
Any ideas?
1 Answer
This question was answered by @ryanpq:
What size droplet are you running Gitlab on? If the gitlab process itself is halted due to a lack of memory it would result in a 502 from nginx.
Have another answer? Share your knowledge.
What size droplet are you running Gitlab on? If the gitlab process itself is halted due to a lack of memory it would result in a 502 from nginx.
thanks with 1gb it works