I have a similar issue. I suspect the underlying issue is that the CI is running behind https using a self-signed certificate. Is there anywhere to tell GitLab to trust it? I know gitlab shell has such a setting for gitlab.
On Thursday, October 17, 2013 9:41:07 PM UTC-4, Nicolas Heine wrote: > > Easy fix: there was a problem in name resolution. the gitlab server could > not see the gitlab-ci server with proper domain name etc. All working fine > now! > > On Friday, 18 October 2013 10:35:17 UTC+9:30, Nicolas Heine wrote: >> >> Hi >> >> I have >> >> - one server running gitlab 6.1.0 e4ba93 >> - one server running gitlab-ci 3.2.0 e0c0609 >> >> In gitlab-ci I can see all the gitlab projects. I followed the "Setup >> guide: >> 1. I could setup a runner and was able to register it. -> good >> 2. I activated the gitlab-ci server for the project inside gitlab -> good >> 3. I hit the try "test settings" button -> after a little while gitlab >> redirects me to a page: 500 - something went wrong >> 4. I could not do any more >> >> How do I find out what went wrong? Are there log pages somewhere that >> explain why I got the 500? >> >> Cheers >> Nico >> >> >> -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
