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

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?

1 Like

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.

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.

1 Like

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.

1 Like