near--user-service--indexer-node 8332 port is not connected.

[WindowsHyun]

I can't find any error logs in docker, logs, etc. However, when creating an actual account or executing the "local_near state test.near" command, a timeout occurs.

[gbouv]

Hey @WindowsHyun ! Can you elaborate on the actual workflow you're doing to see this error? I just went through the full usecase of creating an account, doing a transaction, visualizing the transaction in the explorer, and everything was working just fine.

[WindowsHyun]

@gbouv

When I uninstalled everything and installed it, the 8332 error disappeared. Now I get an error like the image above. Near--user-service--explorer-frontend Docker logs.

Another problem is the picture above.

1. Create an account.
2. Log in with the generated password in incognito mode.

When I log in, the chrome console shows something like this: Could you please let me know how I can handle it?

[gbouv]

Hey @WindowsHyun ! Yes I see the same, and to add a bit more colour the network request failing is this one:

http://127.0.0.1:8330/account/recoveryMethods

with the error message:

blockNumberSignature did not match a signature of blockNumber=2750 from accountId=ad33af196d33cdc77918f6e2e94f59960ac2ef88ec6324bbec9b71f631518251

I am under the impression the contract-helper service is fialing us on this one, and it is likely that it's because it doesn't store the data to the DB. I'll need a bit of help from the NEAR folks to help me understand how this is supposed to be working in the real world before repro-ing it in Kurtosis. I'll keep you posted on my investigation here

[WindowsHyun]

@gbouv
I would appreciate it if the facts I learned after the investigation are uploaded. First, let's reset it and reinstall it.