Mainnet Verifier is still processing after 2 days

[engineeringadmin]

I created a personal verifier on mainnet, and it is still processing 2 days later.

[shahbaz]

Hey @engineeringadmin

Please share the name of your verifier.

[engineeringadmin]

firebase-testnet-1 is the name of the verifier

[shahbaz]

Hey @engineeringadmin

I can see on our end that it is live! Please hard refresh the dashboard page if it’s still pending.

[engineeringadmin]

The testnet version is live, however the mainnet version still says processing. And when I try to connect, it says “Could not get result from torus nodes”

[shahbaz]

@engineeringadmin

the mainnet version still says processing

Can you share the screenshot of your dashboard?

@engineeringadmin

And when I try to connect, it says “Could not get result from torus nodes”

Please share the browser console logs

[engineeringadmin]

Okay, now it says it is deployed. But I am getting the following error:

Error: Could not get result from torus nodes 
 Error occurred while verifying paramscould not validate field iss, 
token https://securetoken.google.com/lobus-io, 
expected iss : https://securetoken.google.com/lobus-io
    at D (callback.93ad5442.js:1:5625)
    at s.mounted (callback.93ad5442.js:1:25481) {c

[engineeringadmin]

Here are some of the other errors, too:

[shahbaz]

@engineeringadmin

token https://securetoken.google.com/lobus-io, 
expected iss : https://securetoken.google.com/lobus-io

I’ve identified the issue. When configuring the verifier, you mistakenly entered the wrong value for the iss field as iss: https://securetoken.google.com/lobus-io, whereas it should have simply been https://securetoken.google.com/lobus-io.

Regrettably, it’s not possible to modify a mainnet verifier. My suggestion is to generate a new one with the correct information.