cannot get sish to work, connection refused or hangs
spetca opened this issue · 1 comments
spetca commented
I'm using the gcloud setup. I've followed the instructions to a tee
i open google shell and start off with this
gcloud compute instances create-with-container sish \
--zone="us-central1-a" \
--tags="sish" \
--container-mount-host-path="host-path=/mnt/stateful_partition/sish/ssl,mount-path=/ssl" \
--container-mount-host-path="host-path=/mnt/stateful_partition/sish/keys,mount-path=/keys" \
--container-mount-host-path="host-path=/mnt/stateful_partition/sish/pubkeys,mount-path=/pubkeys" \
--container-image="antoniomika/sish:latest" \
--machine-type="e2-micro" \
--container-arg="--domain=proxme.xyz” \
--container-arg="--authentication=false" \
--container-arg="--ssh-address=:2222" \
--container-arg="--http-address=:80" \
--container-arg="--https-address=:443" \
--container-arg="--https=true" \
--container-arg="--https-certificate-directory=/ssl" \
--container-arg="--authentication-keys-directory=/pubkeys" \
--container-arg="--private-keys-directory=/keys" \
--container-arg="--bind-random-ports=false" \
--container-arg="--bind-random-subdomains=false" \
--container-arg="--bind-random-aliases=false" \
--container-arg="--tcp-aliases=true" \
--container-arg="--service-console=true" \
--container-arg="--log-to-client=true" \
--container-arg="--admin-console=true" \
--container-arg="--verify-ssl=false" \
--container-arg="--https-ondemand-certificate=false" \
--container-arg="--https-ondemand-certificate-accept-terms=false" \
--container-arg="--https-ondemand-certificate-email=certs@proxme.xyz \
--container-arg="--idle-connection=false" \
--container-arg="--ping-client-timeout=2m"
i follow the firewall instructions
i add the dns A records
and then go to ssh with IP or with domain name
ssh -p 2222 -R 80:localhost:3000 xx.xxxx.xx.xx
ssh: connect to host xx.xxxx.xx.xx port 2222: Connection refused
ssh -p 2222 -R foo:80:localhost:3000 proxme.xyz
ssh: Could not resolve hostname proxme.xyz: nodename nor servname provided, or not known
am i missing a secret step? authentication is off so i dont need to add keys or password under this setting correct? i should simply be able to create a tunnel straight away?
antoniomika commented
Hey @spetca,
Sorry for the delay here. The domain issue would be you needing to properly setup the A records for the instance. Are you able to provide any logs or output from the VM or containers?