#9860 403 error on a git push and a feature request.
Closed: Insufficient data a month ago by kevin. Opened 5 months ago by jatin1812.

I was writing a fedora quick docs about OpenCL on AMD hardware along with mesa. I have made my changes on local branch with adoc file but I am unable to git push due to a 403 error. I also generated API token. But it is not giving me option to type credentials and just throws a 403.

fatal: unable to access 'https://pagure.io/forks/jatin1812/fedora-docs/quick-docs.git/': The requested URL returned error: 403

Also as a feature request I want a functionality to simply be able to add files on my pagure fork. So that I can just click add file, put my adoc file or other changes in.


Is this now solved with the ssh push?

Metadata Update from @mobrien:
- Issue tagged with: low-gain, low-trouble, ops

5 months ago

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

5 months ago

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.

Metadata Update from @pingou:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

4 months ago

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.

Metadata Update from @asaleh:
- Issue status updated to: Open (was: Closed)

2 months ago

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...

Metadata Update from @kevin:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done