Error displayed for js-peer example

[jjhbk]

[2color]

Thanks for opening this issue.

This is basically due to the browser failing to get a circuit relay reservation. The reason this happens is that we only connect to a single app specific bootstrap node (12D3KooWFhXabKDwALpzqMbto94sB7rvmZ6M28hs9Y9xSopDKwQr) which is running the go-peer code.

We could fix this a number of ways:

• Connect to DHT from the browser and do a random walk to find a random circuit relay. This will add a lot of noise, but reduce the risk of not finding a circuit relay reservation.
• Increase the limits on the Go peer. This will likely just kick the can down the road. Provisioned resources tend to get quickly exhausted.

I recently increased the limits

universal-connectivity/go-peer/main.go

Lines 190 to 195 in d28e52c

	resources := relayv2.DefaultResources()
	resources.MaxReservations = 256
	_, err = relayv2.New(h, relayv2.WithResources(resources))
	if err != nil {
	panic(err)
	}

but since the go-peer joins the DHT, circuit relay reservations are reserved by random peers

[nopedawn]

I had a same issue, but using cargo run how do i fix this on rust ?