# SSH Runner clone fails with "could not read Username" after upgrade to Gitea 1.15.3 **URL:** \ **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:** 1\ **Showing post:** 2
**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")
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. --- _[View the full topic](https://drone.discourse.group/t/ssh-runner-clone-fails-with-could-not-read-username-after-upgrade-to-gitea-1-15-3/10073)._