[v0.9.43] Expose both 9933 and 9944 ports

[yli-onf]

I'm upgrading nodes to v0.9.43. I removed --rpc-port=9933 and replaced --ws-port=9944 with --rpc-port=9944, but an external call to port 9933 was not available (screenshot):

Is there a way to expose both 9933 and 9944 for backward compatibility reason? If so, which parameter can I use?

[hugh-onf]

Thanks @yli-onf, in short, can we expose the RPC for more than one port? Thanks

[niklasad1]

No, it's not possible unfortunately.

You could launch a load balancer that redirections 9944/9933 to 9944 as a workaround I guess...

[hugh-onf]

Thanks @niklasad1 we just try to learn if we can resolve this without code change on our end.
Btw, the node itself still support HTTP:9933 with 100 max connections limit right? I would suggest we keep it for backward compatibility as older version (yes we still have to support many networks with older versions) they don't have HTTP on 9944

[niklasad1]

We have kept this a backward compatible option for a long time after we introduced the functionality to support both HTTP and WS on the same socket/port, see paritytech/substrate#13049 for more information. Perhaps should have a more verbose warning about it...

Sorry about this change but you can't really solve this without code change to support both 9933 and 9944 on a single polkadot node anymore, thus to workaround that temporary you would need to put behind a load balancer or something.

Btw, the node itself still support HTTP:9933 with 100 max connections limit right?

I don't understand this question, the number connection to RPC server (both the WS/HTTP) are managed by --rpc-max-connections. That is 100 by-default.

[Szymongib]

Hey, a piece of feedback from my side: for the future it would be good if changes like that could be highlighted in release notes.

[chevdor]

@Szymongib The fix was mentioned in this releasenotes.
The PR was breaking but mentioned as low prio so indeed not easy to spot.
FYI we are working on a better way to provide more accurate descriptions of changes, stay tuned,

[niklasad1]

yeah, it was my fault I should have added a warning when starting up the node thatport 9944 will be removed soon....

It wasn't the intention for the beginning but was the only reasonable way forward.