Update 2: a full reboot of the server took care of it. My best guess is that there was a second nginx server process running which was not killed by 'gitlab-ctl stop' and which blocked gitlab's invokation from acccessing port 80. Sigh at least I've successfully learned the restore-from-backup drill.
BH On Thursday, July 6, 2017 at 1:14:59 PM UTC-7, Blake Hannaford wrote: > > I accepted the latest gitlab upgrade yesterday from the gitlab ubuntu > repository and since then I get a 404 at our server's URL. Gitlab/nginx > has been working great on that server for the last six months with frequent > updates. I tried restarting gitlab and nginx, and rebooting. I tried > purging and re-installing nginx. I tried ">gitlab-ctl reconfigure". > I'm using the stock nginx config that comes from Gitlab. Nothing has > worked. > > Any ideas? > > Thanks > > Blake > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/1dde80c4-c547-4173-a240-39b3c85ac55a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
