Before requesting a new dist-git repository for a new package, you need to generate a pagure.io API token at https://pagure.io/settings/token/new, select the "Create a new ticket" ACL and save it in your local user configuration located at ~/.config/rpkg/fedpkg.conf.

Have you selected the correct ACL mentioned above?

Yes, once I tried it with recommended:
* Create a new project
* Create a new ticket
Then I tried it also with all the ACLs:
* Create a new project
* Fork a project
* Comment on a ticket
* Create a new ticket
* Modify an existing project
It still does not work.

There was a patch[1] from Pagure maintainer for the ACL, currently only Create a new ticket is required.

@pingou any idea?

[1] https://pagure.io/fedpkg/pull-request/259#request_diff

Still the same error, this time I had only ACL:
* Create a new ticket
I do not think fedpkg should fail if the API key has more ACLs than needed, right?

I do not think fedpkg should fail if the API key has more ACLs than needed, right?

It should no, I'm going to look more into it

@jankratochvil afaics your token are valid and should work.

Do you mind if I try running: fedpkg request-branch --repo libipt --namespace rpms --no-auto-module epel7 using your token to try to replicate this issue?

I really do not mind anything, I could even send you my account password but it would probably violate some policy.

Resolved as:
Anonymous ~/.netrc breaks fedpkg request-branch
https://bugzilla.redhat.com/show_bug.cgi?id=1620586
I do not see why fedpkg has both Pagure Issues and Bugzilla Bugs...

Actually you can just report bugs here.

Unfortunately this problem still exists. Bugzilla issue 1620586 was simply discarded without solution due to Fedora 28 EOL.