Gitlab Can't add ssh_key to authorized_keys file via GUI on web browse

[bin...@asiantech.vn]

Hello everyone, 

gitlab GUI (add ssh key) -> something in the middle -> authorized_keys file

I am experiencing some problems with gitlab.

it can't add key to authorized_keys file automatically via web browse and i don't know why.

I had tried to find a solution and i found a temporary way:

It could be added by exec command line "sudo -u git -H bundle exec rake gitlab:shell:setup RAILS_ENV=production". That means whenever new member add key on web browse i have to ssh to server and exec this command. 

Anyone can help me out? 

Some useful information: i checked gitlab-shell and i saw everything look like ok

1)Permission: 

-rw-------  1 git git 2625 Sep 14 08:14 authorized_keys

2)Ran check on gitlab-shell/bin:

Check GitLab API access: OK

Access to /home/git/.ssh/authorized_keys: OK

Send ping to redis server: OK

3)Checked on gitlab_shell_log i saw this event (please don't care to abc@abc because i changed it from my log):

I, [2016-09-14T08:07:12.801699 #7701]  INFO -- : Adding key key-11 => "ssh-rsa BBBBB3NzB21y22EBBBBDBQBBBBB2BQD23yPnm5+X0/zHv0Kt1p1Gnup1tUtEbTmIMG5KeEP9B2wWj18RHWEkSubXJZ47b3S6hwhrNYI4xOX3Gze36oU7Ths7uPjt22oKSnybL3F57jeqIEZHJnEtu7GsgdL0KEVeHSDW2BUXn2gBiEO9dDjnZqmYW/wl2QPwnT0YP/S2PwGodG3DP9oH2SJgRekyLpmWFTh1K0tYi8emPvK5BOxz22vhz7VOLgHG42Bp0VmuGQku+04FW/El1sJhxBB1ypv2BG1Y2/lkNvz1v3ujVn8jx0Wrhglm0r5SpBu3LYrw1BMbQqh1MTz+oJXy2xKmZ4sid87HWVIn9zwoZJ1hTNu0nWQ9fPOr6132d4flB4yVPwNIBZBJ1drvUBKx1ijohRef7NLwIBr2T1SDBo31ntBe+TunkSZBnLQvFJU2QDF5kbVo9opZ9rDISKpwFG+BlsmDOBTFPfb3hd66pD8JnSwlh0lknKP09m7tJIRRyUYKQe5nO26ZpgIobxWG+nzQK+KZH2M2PoP8V/963BBBx9F0tTLJ2qGuvB68+/eZ5uI0zxlisjuFnTf+R9i88f31X07UBxdgSE9kzle2+fkzxnX2duFBBzVXUiK2hzqwst2tq5WPU1eqzkRgvRfPbutQFNMnovxm4qE4GP8hssguGBByd2OUGxFKp7Y7wh7hOV9SwQ== abc@abc"

Thank you,

Best Regards,

PB

[Drew Blessing]

Can you please share the output of `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production`? Also, check the Sidekiq logs. When a key is added, it should spawn an async Sidekiq job to actually update the `authorized_keys` file.