Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hosted weblate fails to create pull request on gitlab.com with error 403 Forbidden (-1) #7477

Closed
2 tasks done
1u opened this issue Apr 7, 2022 · 12 comments
Closed
2 tasks done
Labels
question This is more a question for the support than an issue.

Comments

@1u
Copy link

1u commented Apr 7, 2022

Describe the issue

Automatic and manual pushes lead to error 405
"Failed to create pull request: 403 Forbidden (-1)"

We have some memories that it happened before and disappeared again just like this.

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

  1. Go to https://hosted.weblate.org/projects/openki/openki/#repository
  2. Go to "2 Outgoing commits in the Weblate repository"
  3. Click on push
  4. See error above and underneath

Expected behavior

Creating a pull request on https://gitlab.com/Openki/Openki/ branch dev

Screenshots

image

Exception traceback

Error above: "Could not push to remote branch on Openki/Openki."
Underneath: "Failed to create pull request: 403 Forbidden (-1)"

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

nijel added a commit that referenced this issue Apr 8, 2022
nijel added a commit that referenced this issue Apr 8, 2022
This makes it easier to debug issues like #7477
@nijel
Copy link
Member

nijel commented Apr 8, 2022

Most likely, it's caused by the Openki Gitlab repository configuration. I don't see the "New merge request" button at https://gitlab.com/Openki/Openki/-/merge_requests as I see it on other projects ....

@nijel nijel added the question This is more a question for the support than an issue. label Apr 8, 2022
@github-actions
Copy link

github-actions bot commented Apr 8, 2022

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

@1u
Copy link
Author

1u commented Apr 12, 2022

Hi thx for answering! And looking into it a bit.

So no other gitlab.com repositories that are affected by the same problem...

I checked a lot of settings in the repository on GitLab before opening this issue. I didn't find any settings that would forbid to make a merge request. And we don't remember having changed something there. I'm now in contact with GitLabs support. I'll keep you updated here.

@nijel
Copy link
Member

nijel commented Apr 12, 2022

All I can see on this project is "Email a new merge request to this project", on anything else, there is also "New merge request" button, which allows me to create it in the UI.

Openki:

image

osinfo-db-tool:

image

@1u
Copy link
Author

1u commented Apr 13, 2022

@nijel yes exactly, thx for the screenshots. Sorry I didn't confirm this before: I saw the exact same behavior...

I didn't get a helping response from gitlab support yet. I now just added gitlab user "weblate" as role "reporter" to the openki repository and pushed manually here. And it worked. No idea what's going wrong. I'll keep you updated here if I find out more.

@1u
Copy link
Author

1u commented Apr 13, 2022

Removed Weblate as role "reporter" from the repo -> Pushing didn't work again.
Added as "Guest" -> Pushing worked again.

@github-actions
Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Apr 24, 2022
@1u
Copy link
Author

1u commented Apr 26, 2022

Update: Gitlab support is looking into it further. Pointed me to https://gitlab.com/gitlab-org/gitlab/-/issues/358665

@github-actions github-actions bot removed the wontfix Nobody will work on this. label Apr 27, 2022
@github-actions
Copy link

github-actions bot commented May 8, 2022

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label May 8, 2022
@comradekingu
Copy link
Contributor

@1u Got fixed in GitLab upstream. Works now?

@github-actions github-actions bot removed the wontfix Nobody will work on this. label May 11, 2022
@1u
Copy link
Author

1u commented May 12, 2022

Nice! Yes.

I just removed user @weblate as guest from our repo and pushed it manually in the hosted.weblate UI and it worked again. 🎉

@1u 1u closed this as completed May 12, 2022
@github-actions
Copy link

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue.
Projects
None yet
Development

No branches or pull requests

3 participants