/wss/p2p protocol not supported?

[xlc]

I would like to verify if a node is configure properly for usages of substrate-connect. I usually starts with a Substrate node to verify it can indeed connect to the new node. However it seems like it just doesn't work with /wss/p2p multi addr at all?

I tried this
docker run --rm parity/polkadot:v0.9.27 --reserved-only --reserved-nodes=/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o -lsub-libp2p=trace

and getting error

2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")) through "/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/34.141.46.208/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })    
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")) through "/dns/polkadot-connect-0.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/35.234.84.149/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })    
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Dial failure for PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")    
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: PSM <= Dropped(12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o, SetId(0))    
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Failed to reach PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o"): An error occurred while negotiating the transport protocol(s) on a connection: [("/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o", Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/34.141.46.208/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })), ("/dns/polkadot-connect-0.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o", Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/35.234.84.149/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) }))].   

[bkchr]

@tomaka can you help here?

[tomaka]

I'm not responsible for anything networking anymore, and haven't been for at least 6 months

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/community-bootnodes-and-snapshot-providers/630/4

[bkchr]

CC @paritytech/networking

[melekes]

Looks like Substrate is just not configured with TLS support (server). It can act as a client however. BUT the problem #12024 (comment) is that we're supplying concrete IP/port when dialing the peer instead of DNS name and libp2p returns an error.

@xlc however, keep in mind that for substrate-connect you'd need to add polkadot-connect-7.parity.io certificate to your browser's trust chain. Otherwise, the TLS handshake will fail. Also, substrate-connect now supports WebRTC and we're close to merging it in Substrate #12529. With WebRTC, you don't need to do any extra configuration work. You can read more about WebRTC here.

[xlc]

This doesn't really have anything to do with substrate-connect. I was trying to use the substrate based polkadot node to connect and it doesn't work.

[Maharacha]

We have updated our nodes with ssl now. paritytech/polkadot#6534
And it seems to work with the polkadot binary.

./polkadot --chain polkadot --reserved-only --reserved-nodes=/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ
./polkadot --chain kusama --reserved-only --reserved-nodes=/dns/kusama-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWFj2ndawdYyk2spc42Y2arYwb2TUoHLHFAsKuHRzWXwoJ

v0.9.36

[melekes]

So I've just checked with latest master both addresses ^:

2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")) through "/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/185.127.231.68/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")))))) })
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Dial failure for PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: PSM <= Dropped(12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ, SetId(0))
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Failed to reach PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): Failed to negotiate transport protocol(s): [(/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ: : Unsupported resolved address: /ip4/185.127.231.68/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ: Unsupported resolved address: /ip4/185.127.231.68/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ)]

both result in error.

[melekes]

with latest release (v0.9.36) it does connect via /ws (NOT /wss) because it discovers the /ws address

2023-01-12 14:56:08.894 TRACE tokio-runtime-worker sub-libp2p: Addresses of PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): ["/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-bootnode.dwellir.com/tcp/30333/ws", "/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-bootnode.dwellir.com/tcp/30333/ws"]

with latest master it only discovers /wss

2023-01-12 14:03:39.599 TRACE tokio-runtime-worker sub-libp2p: Addresses of PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): ["/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-boot.dwellir.com/tcp/443/wss"]

and refuses to connect

[Maharacha]

Interesting. I guess we need to continue using ws for substrate nodes then?