Unable to get initial credential for sandbox QVI agent

[rowanshedden]

I have followed the instructions for running up the sandbox demo applications. All docker images are running and accessible via localhost ports, however, when I click the "Get Started" button on the QVI agent the web page displays "Get Started" popup but the wallet does not get a credential.

Please advise next steps, in order to get the credential issued.

I have run this on 2 different OS (Linux & Windows) and have the same issue on both.

The docker images ...

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 155f5537c5c3 gleif/qvi:latest "./bin/start-qvi.sh" 43 hours ago Up 37 hours 0.0.0.0:5621->5621/tcp, :::5621->5621/tcp, 0.0.0.0:5623->5623/tcp, :::5623->5623/tcp qvi 195fe03eb5fc gleif/john-doe:latest "./bin/start-john-do…" 43 hours ago Up 37 hours 0.0.0.0:5021->5021/tcp, :::5021->5021/tcp, 0.0.0.0:5023->5023/tcp, :::5023->5023/tcp john-doe b1940a560e88 gleif/jane-smith:latest "./bin/start-jane-sm…" 43 hours ago Up 37 hours 0.0.0.0:5821->5821/tcp, :::5821->5821/tcp, 0.0.0.0:5823->5823/tcp, :::5823->5823/tcp jane-smith eb129ad37fb2 gleif/legal-entity:latest "./bin/start-legal-e…" 43 hours ago Up 37 hours 0.0.0.0:5221->5221/tcp, :::5221->5221/tcp, 0.0.0.0:5223->5223/tcp, :::5223->5223/tcp legal-entity 815c7b1f4016 gleif/data-user:latest "./bin/start-data-us…" 43 hours ago Up 37 hours 0.0.0.0:5121->5121/tcp, :::5121->5121/tcp, 0.0.0.0:5123->5123/tcp, :::5123->5123/tcp data-user

The docker log ...

[~]$ docker logs -f qvi Identifier prefix does not exist, running incept Prefix ERtGhvgVMavmf7GmfsdAD1herg4QVxiANMWVH5xhNNAg Public key 1: DFvsHyoCzbLkBTQA5acuIZCttPNRvXxGXPnodYDE4IVI

Regsitry: qvi(E3L1yEiCNJBCYj34z7ag9IKUf7ZvWl30GDch0RYloP1s) created for Identifier Prefix: ERtGhvgVMavmf7GmfsdAD1herg4QVxiANMWVH5xhNNAg Launching Qualified vLEI Issuer Agent Identifier prefix exists. Launching Qualified vLEI Issuer Agent

Attached screen shots

[m00sey]

@rowanshedden within the last hour we have deployed a new set of infrastructure. With enhancements based off of what we were seeing from people running through the functional scenarios.

If you could go ahead and stop, delete and pull the containers again and restart the functional scenarios we'll be monitoring things on our end.

We appreciate the you taking the time to work through these issues with us! Feel free to close this issue if you have a successful test :)

[rowanshedden]

Thank you for the prompt response. I can now issue the credential successfully.

[mloepfe]

I have the same issue as described above.

[m00sey]

We will be looking into this.

[m00sey]

@mloepfe we let things sit over the holidays so we have redeployed the infrastructure and successfully tested the workflows.

If you stop/delete/pull (just to get a fresh start after we redeployed) the containers you should be fine.

[mloepfe]

@m00sey thanks a lot, now I could get the initial credential

[mloepfe]

@m00sey Sorry, next problem. I now issued the credential to ACME. I see the issued cred on the qvi GUI but it does NOT appear on the legal-entity (ACME) GUI. What's wrong?