Unable to reach to https://code.qt.io

Axel Spoerl

Up again

VogelPapaFinn

@Axel-Spoerl Same, thank you!

Washman

Thank you! Now our workflows can work again. But what was the issue?

Axel Spoerl

@Washman
We got swamped, issue still under investigation.

laucarlier

I wanted to share this info should that be useful to someone in the future.

In my case I also workarounded this problem by using the copy of the repository on github.

I adapted my qmlcomponent file like so

FetchContent_Declare(
    ds
    GIT_TAG qds-4.4
    GIT_REPOSITORY https://github.com/qt-labs/qtquickdesigner-components.git
)

But now that the server are up again I can also use the code.qt.io version.

Kind regards,

Laurent

jetxeberria

Is it down again? I'm having the same issue

forca

yes, for me too, down again :(

Axel Spoerl

It's down at the moment, I'll keep you posted.

Axel Spoerl

Should be working again.

jetairfly737

It appears to be down again?

alm_parrylabs

Its down, unable to reach https://code.qt.io/yocto/meta-qt6

SGaist

@alm_parrylabs hi, it's online and working however your URL is wrong, it's https://code.qt.io/cgit/yocto/meta-qt6.git/

Axel Spoerl

It’s online and working from Oslo.

Navya

Hello,

Can you please check if the server is down ?
We are trying to access: "https://code.qt.io/qt" But it shows not able to access.

Axel Spoerl

The server is up and running. Why do you want to access a directory, instead of a valid repository?

Navya

Actually "git://code.qt.io/qt/qtquicktimeline.git;name=qtquicktimeline;branch=6.8" this is exact branch i want to access.
Since I was not able to access, I tried the actual website.

Still i am not able to clone the source. Below is the error.
iwave@iwave:~$ git clone https://code.qt.io/qt/qtquicktimeline
Cloning into 'qtquicktimeline'...
fatal: unable to access 'https://code.qt.io/qt/qtquicktimeline/': Failed to connect to code.qt.io port 443 after 135883 ms: Connection timed out

Is there any restriction on the access or clone? Does it depend on the region or the country?
I thought maybe my company firewall is giving the issue. So i tried in my home network and phone- below is the screenshot in phone

shared image (1).jpeg