# SSH access agent forwarding to deploy environment fails

**URL:** <https://discuss.circleci.com/t/ssh-access-agent-forwarding-to-deploy-environment-fails/16349>\
**Category:** Bug Reports\
**Tags:** ssh, deployment\
**Created:** [September 8, 2017, 9:51am UTC](https://discuss.circleci.com/t/ssh-access-agent-forwarding-to-deploy-environment-fails/16349 "2017-09-08T09:51:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gr4per](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gr4per/32/9049_2.png) [@gr4per](https://discuss.circleci.com/u/gr4per)\
**Post date:** [September 8, 2017, 9:51am UTC](https://discuss.circleci.com/t/ssh-access-agent-forwarding-to-deploy-environment-fails/16349/1 "2017-09-08T09:51:44Z")

</div>

It stopped working this night, all our nightly builds fail.  
When going into buildbox (docker) with ssh, we can manually perform ssh -A and nested ssh via jumpbox without probs.  
But the initial run via the buildscript fails.

---

<div class="post-metadata">

**Author:** ![gr4per](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gr4per/32/9049_2.png) [@gr4per](https://discuss.circleci.com/u/gr4per)\
**Post date:** [September 8, 2017, 11:50am UTC](https://discuss.circleci.com/t/ssh-access-agent-forwarding-to-deploy-environment-fails/16349/2 "2017-09-08T11:50:02Z")

</div>

Forget about this please. EIFOK i was making incorrect assumption about user name which was changed.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:35am UTC](https://discuss.circleci.com/t/ssh-access-agent-forwarding-to-deploy-environment-fails/16349/3 "2018-06-18T11:35:08Z")

</div>