Wow, that is strange behaviour of Chrome http://superuser.com/questions/188006/how-to-fix-err-unsafe-port-error-on-chrome-when-browsing-to-unsafe-ports
Thanks for reporting back. On Wed, Jul 9, 2014 at 6:56 PM, Matt Kidd <[email protected]> wrote: > So I got it working. After spending a day thinking the ports were blocked (I > changed all ports to be in the 6000-6010 range for all services) even though > I could see the redirect occur from a command line GET, I tried using a > different browser and Gitlab opened right up. The issue stemmed from Chrome > blocking percieved unsafe ports. > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/01375af9-738c-42d6-8d6a-5d16dff74919%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAEG31mMU%2B%3DPD2CytrmwayR3j2DQNTMgDLC%3DgQ-wLrae9je47Nw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
