# SSH Runner clone fails with "could not read Username" after upgrade to Gitea 1.15.3

**URL:** <https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073>\
**Category:** Drone Support\
**Created:** [October 9, 2021, 8:15am UTC](https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073 "2021-10-09T08:15:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![michalbieber](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/michalbieber/32/6602_2.png) [@michalbieber](https://drone.discourse.group/u/michalbieber)\
**Post date:** [October 9, 2021, 8:15am UTC](https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073/1 "2021-10-09T08:15:04Z")

</div>

I’am running drone 2.4.0 and every thing woked fine until I updated the connected gitea to 1.15.3.  
The docker pipeline including the clone step still works fine only the ssh runner fails with the following message

- git init  
Initialized empty Git repository in /tmp/drone-5t63456y1G1vqNnE/drone/src/.git/
- git remote add origin https://
- git fetch origin +refs/heads/master:  
fatal: could not read Username for ‘’: terminal prompts disabled

I restored to gitea 1.14.5 and then everything works fine again. I also tried to set the gitea oauth signing algorithm back to JWT\_SIGNING\_ALGORITHM=HS256 as this seems to change the token size, but it did’t help.

Could you help me with this problem?

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [October 11, 2021, 12:30am UTC](https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073/2 "2021-10-11T00:30:36Z")

</div>

This is caused by Gitea changing token sizes. You need to follow the database update instructions in the below thread. The account that activated the repository needs to logout and login for the new token to be refreshed and take effect.

> [@SSl Not working for 0.7 version of drone](http://discuss.harness.io/t/problem-with-authorization-in-gitea-1-15-x/9528):
>
> Hi Team, I am not able to configure ssl using 0.7 drone version Below is my docker-compose file version: ‘3’ services: drone-server: image: drone/drone:0.7 ports: - 80:8000 - 443:443 volumes: - /var/lib/drone:/var/lib/drone - /etc/certs/drone.foo.com/server.crt:/etc/certs/drone-server/server.crt - /etc/certs/drone.foo.com/server.key:/etc/certs/drone-server/server.key restart: always environment: - DRONE\_SECRET=vQO8Ke4eUNjoMo5ScuiFvCRwzRVpnk8ZXuN5rIw2NDb5DBzmrC6AnrzpIfzhAa7dH - D…

If the above thread does not work I recommend reaching out to the Gitea community to better understand if there are any known issues or regressions in their release.

---

<div class="post-metadata">

**Author:** ![michalbieber](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/michalbieber/32/6602_2.png) [@michalbieber](https://drone.discourse.group/u/michalbieber)\
**Post date:** [October 11, 2021, 5:37am UTC](https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073/3 "2021-10-11T05:37:00Z")

</div>

Thanks for the hint, but I already extended the size of the columns. As described the docker pipeline is running fine only the ssh pipeline/runner is not working. I did a logout and a login and I also revoked the application authorization in gitea and created it again while logging in to drone. The error still exists. I am running the ssh runner 1.0.1. Do you have any additional hints?  
I discovered that I had set the JWT\_SIGNING\_ALGORITHM=HS256 in the wrong gitea.ini. Now the ssh runner works with this configuration. But not without.