On kube forwarder, I have the same setup but its not forwarding correctly, I get a connect event but then the handshake fails.
I am also connecting via HTTP on another port 18332 - and kube forwarder works for this.
I was wondering what the highlighted part means on the UI i.e.
Is it saying that's the only one that's being registered ? I can confirm the 18332 does work - but its just a standard HTTP server - the other ports don't work. Am I doing something wrong ?
Its probably not needed but for clarity, I am pasting my k8s service here - I know the forwarding works on the command line for the port 28899 and I also know the forwarding works within kube-forwarder for a standard HTTP call using port 18332 - which from above is being highlighted for some reason in the kube-forwarder UI.
Hi,
I have some forwarding setup - manually, and it works as expected - I am basically listening to a TCP port (its zeromq queue)
On kube forwarder, I have the same setup but its not forwarding correctly, I get a connect event but then the handshake fails.
I am also connecting via HTTP on another port 18332 - and kube forwarder works for this.
I was wondering what the highlighted part means on the UI i.e.
Is it saying that's the only one that's being registered ? I can confirm the 18332 does work - but its just a standard HTTP server - the other ports don't work. Am I doing something wrong ?
Its probably not needed but for clarity, I am pasting my k8s service here - I know the forwarding works on the command line for the port 28899 and I also know the forwarding works within kube-forwarder for a standard HTTP call using port 18332 - which from above is being highlighted for some reason in the kube-forwarder UI.
Any ideas what could be wrong ?