LoginHub Broker Service
Sorry, there was an error

LoginHub setup sometimes has obscure error messages. Why? Because it's a security system, and leaking info about bad setup is not allowed - you let hackers hack much more easily.

So setting LoginHub up, or any security system, requires a lot of care, and messages of errors often won't be clear.

One of the most obscure looking errors in LoginHub is the "Error, Sorry, there was an error". Fairly common when doing initial setup on a machine.

9 times out of 10 this is because the secret was entered incorrectly.

image.png

It means "we tried to contact Azure etc.., and it didn't work. We didn't get an error other than more or less 'there was an error' so that is all the information we have.

It can happen from your computer to the LoginHub server (dup licenses, invalid URLs for example) It can happen server to id provider, or on the way back.

If you get this error. Go back and get create a new secret, even if you are 100% you put the secret in correctly. It is so often the mistake that even if you really are the 1st 'other' reason... this is probably it. Getting a secret is a one time operation and you should not store it anywhere except where it is absolutely necessary - in LoginHub in this case.

The most common mistake - copying the wrong item for the secret. You need to copy the secret value not the secret ID. If what you are copying looks like a GUID/UUID: c9fad520-a7c6-4942-9959-e0713df3c191 almost guaranteed you copied the Secret ID on the Secret value. Noting that circa 2026.03 Microsoft just has 'value' as the column header for the important part of the secret, and 'secret id' for the part that has absolutely no value for LoginHub.

One common mistake - copying random text accidentally like "0 certificate, 1 secret"

image.png

OK, so if you are now sure you have the correct Secret Value. You can look at these possibilities.

  • Same license on 2 servers
  • Tenant or ID value wrong.
  • Many other 'details'. Sorry, but basically 'look at everything else' is the only real answer.

Again, the error is obscure because Azure etc.., refuse to give more info until you are logged in for security reasons.