Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forwarding not working but works manually - can you help ? #86

Open
iangregsondev opened this issue Jun 10, 2021 · 0 comments
Open

Forwarding not working but works manually - can you help ? #86

iangregsondev opened this issue Jun 10, 2021 · 0 comments

Comments

@iangregsondev
Copy link

Hi,

I have some forwarding setup - manually, and it works as expected - I am basically listening to a TCP port (its zeromq queue)

kubectl port-forward pod/bitcoind-0 --namespace bsv-private-stn 28899:28890

On kube forwarder, I have the same setup but its not forwarding correctly, I get a connect event but then the handshake fails.

image

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.

image

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.

apiVersion: v1
kind: Service
metadata:
  name: bitcoind-0
spec:
  selector:
    statefulset.kubernetes.io/pod-name: bitcoind-0
  ports:
    - name: other
      port: 9333
      protocol: TCP
    - name: rpc
      port: 18332
      protocol: TCP
    - name: zmqpubhashblock
      port: 28890
      protocol: TCP
    - name: zmqpubhashtx
      port: 28891
      protocol: TCP
    - name: zmqpubrawblock
      port: 28892
      protocol: TCP
    - name: zmqpubrawtx
      port: 28893
      protocol: TCP
    - name: pubdiscardedfrommempool
      port: 28894
      protocol: TCP
    - name: pubinvalidtx
      port: 28895
      protocol: TCP

Any ideas what could be wrong ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant