At which point it would get retried again, fail, repeat, etc. SSH would, of course, fail and exit unsuccessfully. I don't fully understand why, but my best guess is that supervisord tried to launch the job before the network came online. The supervisor program I setup would get stuck in a backoff state that would eventually fail after a number of retries and end up as fatal. I'll just say that after an hour of hitting my head on the desk, I was never able to get the tunnel to connect when my Mac restarted. Without giving it much thought I did a quick search to see if it's available on macOS and - yep! - got it installed a minute later with Homebrew.įor reasons you'll read about in a minute, I won't go into the boring details of getting supervisord to launch automatically when macOS boots, or how to configure the program to launch and keep my SSH tunnel open. It's easy to install, flexible, and mostly straight-forward. ![]() The only issue is that if the SSH connection from my Mac at home to my web server is interrupted, the internet flakes out, or I restart that Mac, I'll need a way of automatically reconnecting.įor the last few years, whenever I've needed to keep a job running on one of my web servers, I've used supervisord. Further, I can then open up macOS's Screen Sharing.app and connect to localhost:5901 to access my Mac's desktop. This means when I'm working remotely I can run ssh home on my laptop (or phone if I've got something like Prompt installed) and I'll be SSH'd into my Mac at home. It will then forward ports 59 on the remote host back to my local Mac's VNC and SSH daemons. With that in place, I can run ssh vpn, and a reverse SSH tunnel will be established between my Mac inside my network's firewall and my remote web server. So, I added this to my ~/.ssh/config file: ![]() And I happen to have a few web servers on the public internet with bandwidth to spare. Luckily, from my time spent working remotely for Yahoo!, I got pretty good at the ins-and-outs of setting up SSH tunnels. Opening up a hole in my gateway's firewall and forwarding a port or two would work, but that has always felt a bit icky to me - I don't like the idea of some automated bot on the internet finding an open port on my network and just hammering away at it. So, this holiday weekend I decided it would be fun to finally get around to setting up some sort of permanent connection that would allow me to log in remotely.įor various boring reasons all the devices on my home network are behind two layers of NAT. And it looks like that may continue for the foreseeable future - at least for a day or two a week. And for the last few weeks I've been spending more time working outside the comforts of my home office. I do still find the need to occasionally SSH into my LAN or screen share, though. And besides, with all my data now in the cloud it's become less of an issue since there's rarely ever a file that's "only on my Mac" back at the house. (So useful, in fact, that I even built an app to extend the service's functionality.) But Apple shut down the service in Mojave. I found it incredibly useful to be able to screen share with my Mac at home and access its files. I was always a big fan of Apple's Back to My Mac service. You need the following information.Today's post is a bit more technical than what I've been writing about lately, but it's also partly for my own reference to save me some googling when I forget everything again in the future. It doesn’t shake Docks icon but menu bar and growl on top. UPDATE Oct 29, 2014: Meekat which used to be shareware is now free but no longer maintained.Īfter a few days of the research, I’ve finally able to find the best and simple SSH tunnel app called Coccinellida! Meekat is great Free app, but it’s no longer maintained… It may not work in the future. ![]() But they all DID NOT support RSA public key authentification. I’ve tried Fugu, SSHTunnel, and SSH Tunnel Manager. But it’s troublesome to command each time on the Terminal. You can use Terminal to port forward to your localhost, and access. ![]() It’s fantastic software, but it doesn’t really allow you to access via SSH Tunnel. Recently my main coding application has been Coda 2. However, none of famous Mac OS X FTP clients offer SSH Tunnel function as WinSCP does. You can directly access the SFTP server via SSH Tunnel as a built-in function using RCA secret key authorization method. Whereas Windows has WinSCP, the free and easy FTP client. In addition, the authentification required RSA key authorization for the project. I’ve had an opportunity to work on a very tight security Internet server that was blocking the external SFTP access but only allowed us to access via the SSH Tunnel of the different server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |