URL rejected: Port number was not a decimal number between 0 and 65535 #263

jinzoningen commented 2025年06月05日 15:34:02 +02:00

I am having this error since today with woodpecker:

• git push -f https://$GIT_USERNAME:$GIT_PASSWORD@codeberg.org/ /pages.git pages
  fatal: unable to access 'https://:@codeberg.org//pages.git/': URL rejected: Port number was not a decimal number between 0 and 65535

I recently changed email, but I updated the secret accordingly.

I am having this error since today with woodpecker: + git push -f https://$GIT_USERNAME:$GIT_PASSWORD@codeberg.org/********/pages.git pages fatal: unable to access 'https://********:********@codeberg.org/********/pages.git/': URL rejected: Port number was not a decimal number between 0 and 65535 I recently changed email, but I updated the secret accordingly.

boldsuck commented 2025年06月05日 18:41:56 +02:00

I've never pushed to a git repo via https, therefore cannot help directly.

I find SSH much more convenient, especially when pushing to mirrored repos e.g. github and codeberg at the same time.

git remote -v # List your existing remotes

Copy your SSH pub key to Codeberg and change your remote's URL from HTTPS to SSH:
git remote set-url origin git@codeberg.org:USERNAME/REPONAME.git

Successful SSH connection test:

user@t520:~$ ssh -T git@codeberg.org
Hi there, boldsuck! You've successfully authenticated with the key named user@t520 id_ed25519_sk, but Forgejo does not provide shell access.
If this is unexpected, please log in with password and setup Forgejo under another user.

I've never pushed to a git repo via https, therefore cannot help directly. I find SSH much more convenient, especially when pushing to mirrored repos e.g. github and codeberg at the same time. `git remote -v` # List your existing remotes Copy your SSH pub key to Codeberg and change your remote's URL from HTTPS to SSH: `git remote set-url origin git@codeberg.org:USERNAME/REPONAME.git` Successful SSH connection test: ``` user@t520:~$ ssh -T git@codeberg.org Hi there, boldsuck! You've successfully authenticated with the key named user@t520 id_ed25519_sk, but Forgejo does not provide shell access. If this is unexpected, please log in with password and setup Forgejo under another user. ```

jinzoningen commented 2025年06月06日 14:54:49 +02:00

@boldsuck wrote in #263 (comment):

I've never pushed to a git repo via https, therefore cannot help directly.

I find SSH much more convenient, especially when pushing to mirrored repos e.g. github and codeberg at the same time.

git remote -v # List your existing remotes

Copy your SSH pub key to Codeberg and change your remote's URL from HTTPS to SSH: git remote set-url origin git@codeberg.org:USERNAME/REPONAME.git

Successful SSH connection test:

user@t520:~$ ssh -T git@codeberg.org
Hi there, boldsuck! You've successfully authenticated with the key named user@t520 id_ed25519_sk, but Forgejo does not provide shell access.
If this is unexpected, please log in with password and setup Forgejo under another user.

Thanks! However I found what the problem was, and it was human related :/ I miswrote the token generated.
Anyway, using ssh instead of https could be interesting.

@boldsuck wrote in https://codeberg.org/Codeberg-CI/feedback/issues/263#issuecomment-5010894: > I've never pushed to a git repo via https, therefore cannot help directly. > > I find SSH much more convenient, especially when pushing to mirrored repos e.g. github and codeberg at the same time. > > `git remote -v` # List your existing remotes > > Copy your SSH pub key to Codeberg and change your remote's URL from HTTPS to SSH: `git remote set-url origin git@codeberg.org:USERNAME/REPONAME.git` > > Successful SSH connection test: > > ```text > user@t520:~$ ssh -T git@codeberg.org > Hi there, boldsuck! You've successfully authenticated with the key named user@t520 id_ed25519_sk, but Forgejo does not provide shell access. > If this is unexpected, please log in with password and setup Forgejo under another user. > ``` Thanks! However I found what the problem was, and it was human related :/ I miswrote the token generated. Anyway, using ssh instead of https could be interesting.