Gitlab-ce Installation on Ubuntu 18.04 fails with message on database migration

I am installing GitLab CE on Ubuntu 18.04 using instructions here:

It fails as shown below:

Running handlers:
There was an error running gitlab-ctl reconfigure:

bash[migrate gitlab-rails database] (gitlab::database_migrations line 54) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of "bash"  "/tmp/chef-script20190924-19945-2vwp6d" ----
STDOUT: rake aborted!
Your current database version is too old to be migrated. You should upgrade to GitLab 11.11.0 before moving to this version. Please see
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/migrate/schema_check.rake:13:in `block in <top (required)>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:49:in `block (3 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => db:migrate => schema_version_check
(See full trace by running task with --trace)
---- End output of "bash"  "/tmp/chef-script20190924-19945-2vwp6d" ----
Ran "bash"  "/tmp/chef-script20190924-19945-2vwp6d" returned 1

Running handlers complete
Chef Client failed. 0 resources updated in 39 seconds

Most services are down as a result. Therefore, I started it again with sudo gitlab-ctl start. It seems all is up:

ok: run: alertmanager: (pid 24156) 0s
ok: run: gitaly: (pid 16425) 1721s
ok: run: gitlab-monitor: (pid 24215) 0s
ok: run: gitlab-workhorse: (pid 24217) 0s
ok: run: logrotate: (pid 24224) 1s
ok: run: nginx: (pid 24244) 0s
ok: run: node-exporter: (pid 24247) 3s
ok: run: postgres-exporter: (pid 24270) 0s
ok: run: postgresql: (pid 15770) 1764s
ok: run: prometheus: (pid 24273) 0s
ok: run: redis: (pid 15753) 1765s
ok: run: redis-exporter: (pid 24286) 2s
ok: run: sidekiq: (pid 24299) 4s
ok: run: unicorn: (pid 24313) 1s

However, when I try to access the URL in browser, the request times out with a 502. Please help me get around this issue.

Hi @chainhead, did you resolve this problem? I have too :frowning: