@jankratochvil Probably you are creating the token without right acls. When you created the ticket, did you select Create a new ticket acl?

Please try it with the right acl and it should work.

Still the same problem:
[fedpkg.pagure]
token = HS...02

Created only with ACL "Create a new ticket".
fedpkg-1.37-7.fc30.noarch

@jankratochvil It seems to be working for me with a new token with just Create a new ticket token:

https://pagure.io/releng/fedora-scm-requests/issue/16639
https://pagure.io/releng/fedora-scm-requests/issue/16638

Not sure whats going on your end.

It looks correct with some debug output but the request is still rejected:

headers={'Authorization': 'token M1N3TXZSIN2SWBHGOJQLT11A45DQJR292ZGTKE9I7KL2OCKPRO8O6K32VWVXN6A0', 'Accept': 'application/json', 'Content-Type': 'application/json'}
payload={"title": "New Branch \"epel8-playground\" for \"rpms/inotify-tools\"", "issue_content": "```\n{\n \"action\": \"new_branch\",\n \"branch\": \"epel8-playground\",\n \"namespace\": \"rpms\",\n \"repo\": \"inotify-tools\",\n \"create_git_branch\": true\n}\n```"}

I have created the request by hand. :^)
https://pagure.io/releng/fedora-scm-requests/issue/17447

Odd. Are you still seeing this issue?

Still the same problem - freshly created token with all the possible rights enabled.
libipt/master$ cat ~/.config/rpkg/fedpkg.conf
[fedpkg.pagure]
token = 4FRG...M4EK
libipt/master$ fedpkg --user jankratochvil request-branch epel8
Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token.
For invalid or expired token refer to "fedpkg request-repo -h" to set a token in your user configuration.

So I've just tried using your API token, to see if I could reproduce the problem and:

$ fedpkg --user jankratochvil request-branch epel8       
https://pagure.io/releng/fedora-scm-requests/issue/24467 
https://pagure.io/releng/fedora-scm-requests/issue/24468 

(I have deleted the issues then they were bogus)

Would you have a proxy or something that could interfere with the request?

@jankratochvil So, we were able to test your token and it seemed to work fine on our end. But we created https://pagure.io/fedpkg/issue/396 to provide more info.

It breaks due to ~/.netrc:

$ wget -O ~/.netrc 'https://git.jankratochvil.net/?p=nethome.git;a=blob_plain;f=.netrc'

Sorry I apparently did not try it with a clean user with no $HOME files before. I expected I did.

I have found I already debugged it once in the past but the Bug got EOLed:
Anonymous ~/.netrc breaks fedpkg request-branch

The linked Fedpkg issue (https://pagure.io/fedpkg/issue/396) was fixed. Not yet released.

Thanks everyone. No further action needed here that I can see.