LuKe's picture
LuKe - Thu, 2018/03/08 - 13:54

Hi,

I'm testing the gitlab 14.2 appliance on virtualbox/windows7.

When I try to access the gitlab interface, it responds very slowly and most of the time I get a nginx error: "504 Gateway Time-out".

But if I enter the Webmin interface everything goes very well and fast. Same behavior if I access via ssh.

What can be the problem?

Intel Core i3-2120 3.30 GHz
8 GB RAM
Windows 7 Pro SP1
VirtualBox 5.2.8
 

LuKe

Forum: 
Support
OSS Virt's picture

OSS Virt - Mon, 2018/03/12 - 11:44

Hi LuKe,

this is a known issue with Gitlab. It's an incredibly resource hungry application. How much memory have you allocated it in the VM?

Here are their recommended hardware requirements

LuKe's picture

LuKe - Mon, 2018/03/12 - 16:46

It was 1 GB (the default value); now it is 4GB but I got an "502 Bad Gateway" error.

I found that it is related with the configuration of nginx but I cannot figure out how to solve.

 

Any ideas?

Jeremy Davis's picture

Jeremy Davis - Tue, 2018/03/13 - 08:51
In my experience, the backend service crashing is a common source of "502 Bad Gateway" errors on the GitLab appliance.

I suggest that you check whether that is running or not (or easier, just reboot it and give it a couple of minutes to start).

LuKe's picture

LuKe - Wed, 2018/03/14 - 13:31

I think the problem was that I had to wait for some minutes after a reboot to get the service working properly.

Now it works.

 

Jeremy Davis's picture

Jeremy Davis - Fri, 2018/03/16 - 01:49
Great, glad to hear that it's working for you now! :)

Add new comment