I have submitted the PR using SSH tho,

https://pagure.io/fedora-docs/quick-docs/pull-request/356

Is this now solved with the ssh push?

I've the same issue over HTTPS. I can't push any code.

Can one or both of you please provide the full output of your 'git push' that failed and the exact time you tried so we can match it up with logs?

@jatin1812 @simonmanning did you see Kevin's question above?

I'm going to close this ticket as "Insufficient Data".

Please re-open if you run again into this, I hope it was just a fluke and that things are working fine now.

Hello, it seems it's happening again.

The full output of my 'git push' after I tried pushing to my fork over HTTPS was:

fatal: unable to access 'https://pagure.io/forks/patrikp/mirrors-countme.git/': The requested URL returned error: 403

The exact time was 10:02:33 UTC+02:00 (I've tried several other times over the previous ~45min from the same IP address).

As a workaround for now, everything works fine over ssh, though that won't help people behind a HTTP proxy much.

Best of luck.

Whats in your .git/config for that fork? Is this still happening?

If you see this again, please do attach .git/config and the time...

This happened again to me:

[lorbus@fedora fedora-module-defaults]$ git push --set-upstream origin add-cri-o
fatal: unable to access 'https://pagure.io/forks/lorbus/releng/fedora-module-defaults.git/': The requested URL returned error: 403
[lorbus@fedora fedora-module-defaults]$ date -u
Wed Dec 22 05:12:54 PM UTC 2021
[lorbus@fedora fedora-module-defaults]$ cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://pagure.io/forks/lorbus/releng/fedora-module-defaults.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "main"]
        remote = origin
        merge = refs/heads/main
[credential]
        helper = store

The line in ~/.git-credentials looks like this:

https://lorbus:<APITOKEN>@pagure.io

git also won't ask me for creds if I unset the credential helper:

[lorbus@fedora fedora-module-defaults]$ git config --local --unset credential.helper
[lorbus@fedora fedora-module-defaults]$ git push origin add-cri-o 
fatal: unable to access 'https://pagure.io/forks/lorbus/releng/fedora-module-defaults.git/': The requested URL returned error: 403
[lorbus@fedora fedora-module-defaults]$ git --version
git version 2.33.1

(pushing via ssh works fine, just not via https)

You cannot use pagure api tokens for src.fedoraproject.org.

You must get a OIDC token for that. The easiest way would be to use 'fedpkg clone -a' or 'fedpkg push' and it will set it up in your config and have a browser run to get the token.
it's:

[credential]
helper = /usr/bin/fedpkg gitcred
useHttpPath = true

if you want to manually add it.

@kevin this is for pagure.io, not src.fedoraproject.org

Ah, right you are. Sorry for misreading it. ;(

I think I've found it: https://pagure.io/fedora-infra/ansible/blob/eb2dac57e1c3c78c21b708740b0a7de81c6b4cb4/f/roles/pagure/templates/pagure.cfg#_425

It's simply not enabled in production :)

Please reopen this ticket. I am getting this error when trying to push to my fork of a Pagure project over https:

% git push --set-upstream origin python                                       
fatal: unable to access 'https://pagure.io/forks/ryandesign/newt.git/': The requested URL returned error: 403

The Pagure documentation says it should prompt me for a username and password (or API key) but it does not.

It has never worked for me; this is the first time I've tried to contribute to a project hosted at Pagure. I have never had such problems contributing to projects on GitHub or GitLab.

I tried, as suggested on Stack Overflow, to change my remote's URL to include the username:

git remote set-url origin https://ryandesign@pagure.io/forks/ryandesign/newt.git

This didn't change the error.

I'm not uploading my .git/config because it's whatever git created by default.

Can you please open a new ticket?

You can't use username/password (as noted in the docs, this only works if pagure is in 'local' mode, which pagure.io is not), but I am not sure why it's not prompting you for username/api key.

Anyhow, please open a new ticket and we can try and get it figured out. Thanks