Not able to access gitlab internally after reverse proxy setup

Viewed 248

Currently I'm getting a 422 The change you requested was rejected error when trying to login to gitlab.

The only thing I changed was to follow the official doc on how to setup gitlab behind a reverse proxy. The funny thing is, if I access gitlab from the outside via https, it works perfectly and to login is possible. But accessing the gitlab instance via the internal lan directly, the above error gets thrown.

Do I miss some configuration for the nginx when http gets used?

1 Answers

Try first and check if your proxy is used when your are using the internal lan.

I usually set

no_proxy='localhost,.company.com'

That will avoid using the proxy for intranet access.

Related