ssh - git fails on symlinks to my repo -

i created local git user repos inside /opt/git/repo1.git/, /opt/git/repo2.git/ etc. setup public key auth , can access git repos on ssh follows: git@ubuntu:/opt/git/repo1.git. when set up, made symlink in git's home dir points repo1:

ln -s /opt/git/repo1.git ~/ 

so @ first able access repo git@ubuntu:repo1.git, stopped working (not sure what's changed on ubuntu box, perhaps update installed only). error tortoise git when try git pull:

git.exe pull --progress --no-rebase -v "origin"  fatal: 'repo1.git' not appear git repository fatal: not read remote repository.  please make sure have correct access rights , repository exists. 

i still can access using git@ubuntu:/opt/git/repo1.git, why access symlink stopped working , can debug it? side node, symlink in /home/git/repo1.git still exist , points right location. i'm absolutely sure used work, because when cloned repo on windows box cloned using shorter symlink, i've done few pulls , pushes since then, stopped working symlinks: cannot access existing repo , cannot clone new copies.

edit: noticed still can local git clone using symlink, if local terminal (e.g. if try ssh session fail, perhaps because ssh detects i'm trying ssh login second time)

i've been trying figure out, , appears found reason such strange behavior. reason, when using putty started login local username instead of user name git.

on windows use jdoe local user name , ubuntu has same user. so, when added repo1.git symlink inside /home/jdoe on ubuntu started work tortoise git.

the reason behavior seems tortoise git uses saved putty sessions login remote instead of using keys pageant. when deleted saved putty sessions , created new 1 logs in git@ubuntu tortoise git started work without creating symlinks in /home/jdoe

edit: after digging details, appears reason failure in [tortoisegit]plink.exe:

plink: command-line connection utility release 0.67 usage: plink [options] [user@]host [command]        ("host" can putty saved session name) 

in case saved putty session called ubuntu, host name. that's why getting issue.