GitLab CE never wakes up after a a few days of inactivity


I have installed a Gitlab CE instance on a Debian Jessie machine and all is working fine, the users are very happy with the features that it offers.
However, if we do not use this instance for about 4 days, it stops responding when we come back, all we get is the 502 error page.
We came up with the following workaround:

Login on the server
gitlab-ctl stop
wait 30 seconds
gitlab-ctl start
wait 5 minutes

With this, the instance is back up and working as expected.
When issuing the stop command, we get a timeout error on the sidekiq item.

Is this a known issue?
Is there a fix/workaround?

We are currently using version 8.9.4 but I could not see anything obviously related in the changelog for later versions.

Any help would be most welcome.

Same here. I thought it was just me. We are having the same problem, error 502.

It just started happening after the last update to Gitlab. For the past year or two Gitlab CE has worked perfectly. I did an update a few weeks ago and now we just get error 502 every day.