amazon web services - GitLab Container Registry behind AWS Load Balancer -

i have gitlab instance setup behind aws load balancer (just achieve https amazon issued certificate). i'm running nginx main gitlab service following settings (from /etc/gitlab/gitlab.rb):

nginx['enable'] = true nginx['listen_port'] = 80 nginx['listen_https'] = false nginx['proxy_set_headers'] = {     "x-forwarded-proto" => "https",     "x-forwarded-ssl" => "on" } 

i trying setup similar container registry:

registry_nginx['enable'] = true registry_nginx['listen_port'] = 5000 registry_nginx['listen_https'] = false registry_nginx['proxy_set_headers'] = {   "x-forwarded-proto" => "https",   "x-forwarded-ssl" => "on" }  gitlab_rails['registry_enabled'] = true gitlab_rails['registry_host'] = "<redacted>" gitlab_rails['registry_port'] = "5005" 

however, whenever try login local machine via docker 400 bad request. believe traffic flowing such:

local --|https:5005|--> aws elb --|http:5000|--> registry nginx --|http:5005|--> gitlab container registry

is correct? issue traffic hitting container registry in form of http , being rejected container registry service? if so, how correct setup? i'd use gitlab's container registry if possible, using aws ecr possibility.

update: tried logging in gitlab instance container registry , received 400 error code stating request header or cookie large. i'm trying figure out how update nginx configuration container registry allow larger request sent.