Solving Omnibus + Apache + letsencrypt issue of "No vhost exists..."

The recommend SSL config files from web-server/apache · master · GitLab.org / GitLab recipes · GitLab generally have the SSL vhost paired in the same config file with port 80 vhost. This triggers a bug in letsencrypt: No vhost was selected · Issue #2776 · certbot/certbot · GitHub
Simply moving the <Virtualhost *:80> … into it’s own config file solves the issue.

I hope this helps someone. GitLab is a fantastic open resource!

I’m running into the same problem. Could you elaborate?