3

For my baking operation, I have set up a remote signer and SSH tunneled it to my baking server on port 7878. I have also set up tezos-signer with --require-authentication.

On my baking server, I'm now trying to add it with the recommended command:

./tezos-client import secret key my_signer tcp://localhost:7878/tz1abcdef123456789

tezos-client just hangs and does not give me the prompt back unless I press Ctrl+C. How can I even start debugging this?

2 Answers 2

1

I'm doing the exact same thing successfully.

I have set up a remote signer and SSH tunneled it to my baking server on port 7878.

It sounds from your description, and the symptom you describe, like you might have done your tunnelling backwards. The remote signer shouldn't initiate any tcp connections to your baking node. The remote signer's firewall should however be configured to accept connections from your baker (whitelist the baker's IP address) on the port you've setup your signer to run on, port 7878.

This is to say you need to configure the firewall of your remote signer for this, not the firewall for your baker.

0

It turned out to be a simple mistake; I had already imported another TCP tezos-signer on the same port (7878). Apparently tezos-client does not fail gracefully when trying to import a different address on a port that's already registered with one.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.