Arch Linux

linerman

Member

Registered: 2021-02-16

Posts: 90

[Solved] Gitlab https issue

Hi,

Lately, I'm observing an issue with GitLab https connection.
I have never had that issue before.
I've tried to update my proton from AUR, but cloning from GitLab takes hours (about 40 minutes) and in the end gives an error "504".
eg.

 git clone https://gitlab.freedesktop.org/gstreamer/gst-plugins-base.git/ 

I modified PKGBUILD to use SSH instead of https, but that did not help a lot.
It is because during making that particular package there is a process out of PKGBUILD:

 Updating git repository `https://gitlab.freedesktop.org/gstreamer/gstreamer-rs 

so in the end building is aborted

warning: spurious network error (2 tries remaining): unexpected http status code: 504; class=Http (34) 

So Is this https error occurs because of my network configuration or is it something else?
I built proton two weeks ago and all went smooth.

PS. Connecting to GitHub via https is working flawlessly.

Last edited by linerman (2021-12-29 17:43:58)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,493

Website

Re: [Solved] Gitlab https issue

PS. Connecting to GitHub via https is working flawlessly.

What does github have to do with any of this?

A 504 is a problem on the server - and I can confirm a timeout trying to clone that freedesktop.org repository over either https or http.  Other gstreamer repos on freedesktop.org seem similarly affected (I just tested gst-libav.git).  EDIT: as are other non-gstreamer repos (tested wlroots/wlroots.git).

Last edited by Trilby (2021-12-27 18:44:38)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

linerman

Member

Registered: 2021-02-16

Posts: 90

Re: [Solved] Gitlab https issue

Thanks for info.

What does github have to do with any of this?

Well if github works with https, it means that my network configuration is sane - that was my an exaggerated conclusion.

fedev

Member

Registered: 2017-09-21

Posts: 15

Re: [Solved] Gitlab https issue

GitLab has a banner on their site with the following announcement:

"There is an ongoing issue causing HTTP clones of some repositories to time out. If this is affecting you, please try cloning via SSH instead. This is currently being investigated and hoped to be resolved 29th Dec."

So I'm guessing that's the reason for it. You could reconfigure the PKGBUILD file or you could wait to see if this is resolved as they mentioned.

linerman

Member

Registered: 2021-02-16

Posts: 90

Re: [Solved] Gitlab https issue

Yes. The issue was caused by GitLab servers. Now it is fine. Thanks for the info.