Shouldn't you really do ssh -f [email protected] -L 11300:localhost:11300 - N ?
Or are your beanstalk server listening on 0.0.0.0? Either way, it's probably better to use localhost. Maybe this helps? Regards, Håkon Nessjøen On Sep 6, 10:11 pm, Charlie <[email protected]> wrote: > Hey all, > > I'm running a distributed photo-stitching system. I have a central > server running beanstalkd on the standard port. I'm using beanstalk > to distribute jobs, and beanstalkc in a python script that runs on > nodes to receive and process them. I'm tunnelling the beanstalk > connection over ssh, and this is working fine for machines on my local > network. I use the following command to tunnel the beanstalk port to > localhost, then connect locally and all's well. > > ssh -f [email protected] -L 11300:host.com:11300 -N > > Where I run into problems is trying to do this on a remote host. I > have my ssh port forwarded to external port 33333 on my router, and I > can ssh in from remotely with no trouble. But tunnelling to beanstalk > doesn't work. I tunnel with this command: > > ssh -f [email protected] -L 11300:host.com:11300 -N -p 33333 > > And it's successful. but then if I telnet to port 11300 locally, I > get the following error: > > channel 1: open failed: connect failed: Connection refused > > ^ this is an ssh error, not a telnet one. Somewhere, presumably in > the NAT, i'm unable to connect to the beanstalk server over ssh. I'm > stumped. Any ideas on something i'm missing, or alternatives? I > don't want to just expose beanstalkd to the world without some level > of encryption. > > Thanks all, > Charlie -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
