Closed alrevuelta closed 1 month ago
Two additional endpoint/services needed to be exposed to allow the waku-simulator web
service to access the api
service externally:
API_URL=http://localhost:8090
WS_API_URL=ws://localhost:8090
see https://github.com/status-im/infra-misc/commit/3276499a for details
The remote waku-simulator deployment has an issue where each nwaku node has intermittent connectivity to only one peer.
I didn't see this issue locally because I had not pulled the latest docker image for nwaku in a while, so I was running v0.25.0-rc.0-64-g3c8237
instead of the latest v0.25.0-rc.0-87-g2aa835
.
When running the actual latest locally I saw the same connectivity issue.
I removed all changes for onchain RLN locally to ensure that this was not what was causing the issue (it was not).
I have notified the nwaku team about this issue and they will investigate.
This should fix that https://github.com/waku-org/waku-simulator/pull/37 Also when https://github.com/waku-org/nwaku/pull/2562 is merged we no longer need that config (but doesn't harm)
The waku-simulator deployment on the remote host is still not working.
Locally I have installed the same docker and docker-compose versions as the remote host and it still works locally.
The remote host deploys the simulator without the --compatibility
mode but this is only applicable if the docker-compose version is v2 and newer.
The next step is to pull from an old commit, prior to the onchain additions, to see if that still works on the remote host. If it does work then I will try running the onchain commits to see which change breaks things.
The remote host specific issue of peer connectivity was fixed, see https://github.com/status-im/infra-misc/issues/268 for details. The firewall rules needed to be updated for the block explorer to work.
With the latest changes, now we have onchain RLN working with a private network. This issue tracks:
deploy-wakusim
branch)So we have: