Hi.
https://gitlab.common-lisp.net is currently returning http 502.
On Jan 7, 2018, at 00:17, R. Matthew Emerson rme@acm.org wrote:
Hi.
https://gitlab.common-lisp.net is currently returning http 502.
This seems to have been resolved. Please let us know if it is still not the case for you so that we may investigate further.
I fear that https://gitlab.common-lisp.net is returning http 502 again.
On Jan 20, 2018, at 2:29 AM, Mark Evenson evenson@panix.com wrote:
On Jan 7, 2018, at 00:17, R. Matthew Emerson rme@acm.org wrote:
Hi.
https://gitlab.common-lisp.net is currently returning http 502.
This seems to have been resolved. Please let us know if it is still not the case for you so that we may investigate further.
Fixed again. Thanks for the heads up!
I'll be looking into what it is causing the site not to come up correctly after reboot.
On Jan 29, 2018 09:05, "R. Matthew Emerson" rme@acm.org wrote:
I fear that https://gitlab.common-lisp.net is returning http 502 again.
On Jan 20, 2018, at 2:29 AM, Mark Evenson evenson@panix.com wrote:
On Jan 7, 2018, at 00:17, R. Matthew Emerson rme@acm.org wrote:
Hi.
https://gitlab.common-lisp.net is currently returning http 502.
This seems to have been resolved. Please let us know if it is still not
the case for you so that we may investigate further.
While working on the engineering copy, I ran into this multiple times today and ended up fixing the problem. Now, after a reboot or upgrade, GitLab will get back up correctly all by itself.
Regards,
Erik.
On Mon, Jan 29, 2018 at 10:07 AM, Erik Huelsmann ehuels@gmail.com wrote:
Fixed again. Thanks for the heads up!
I'll be looking into what it is causing the site not to come up correctly after reboot.
On Jan 29, 2018 09:05, "R. Matthew Emerson" rme@acm.org wrote:
I fear that https://gitlab.common-lisp.net is returning http 502 again.
On Jan 20, 2018, at 2:29 AM, Mark Evenson evenson@panix.com wrote:
On Jan 7, 2018, at 00:17, R. Matthew Emerson rme@acm.org wrote:
Hi.
https://gitlab.common-lisp.net is currently returning http 502.
This seems to have been resolved. Please let us know if it is still
not the case for you so that we may investigate further.