[MU4 Issue] MuseHub is having trouble connecting, when I'm connected.

[scannerbrightly]

Describe the bug
Install MuseHub, open it. It displays the following:

To Reproduce
Steps to reproduce the behavior:

1. Install MuseHub
2. Open MuseHub
3. It shows that it can't connect.

Expected behavior
That MuseHub would find my Ethernet connection, which is connected via a Dell D3100 USB3 dock, as are my screens, keyboard, and mouse.

There are no ways to edit any connection settings in the Settings area. I tried to turn off 'Community Acceleration' but it didn't change anything. I've rebooted. I've also connected to my Wi-Fi while still connected to my dock and pressed the 'round arrow', but it still didn't find a connection. I've tried to 'repair' the install. No joy.

Screenshots

MuseScore3 was able to find my connection:

Platform information

• OS: Windows 10, 22H2, build 19045.2364
• Lenovo T460s, 12 GB RAM, i5-6300U

Additional context
I might be able to try to capture network traffic, if somebody pointed me to what I might be looking for. What address is it trying to connect to? Is it trying to resolve that address using a DNS?

[jtackaberry]

AFAICT their backend is not sized to meet the demand. Muse Hub tries to query https://muse-webservice.azurewebsites.net/graphql but it's frequently timing out.

[jtackaberry]

Related to #15275

[arhadthedev]

AFAICT their backend is not sized to meet the demand

Would total replacement of the Azure-hosted GraphQL API with GitHub in-repo manifests increase reliability? I believe that GitHub imposes no quota or bandwidth limitation on GET queries like https://github.com/musescore/MuseScore/blob/master/musehub-manifest.json or https://github.com/musescore/MuseScore/releases/download/v4.0/MuseScore-4.0.0-x86_64.msi.

Edit: to not cause an avalanche of PRs touching the manifest file on any minor update of any program or library, the manifect can be stored in a separate repo (like https://github.com/musescore/musehub-data/blob/master/manifest.json) and automatically updated by direct commits created and force-pushed in a privileged GitHub Action workflow triggered by on.schedule daily or weekly.

[cbjeukendrup]

Closing, since this is a Muse Hub issue and not a MuseScore issue, and it seems like this was a one-time server issue.