![]() * Fixed a bug that prevented Net Disks from appearing in the Interarchy menu. * Improved the behaviour of the "Open In New Tab" and "Open In New Window" menu items. * Fixed a bug that prevented the Interarchy command line tool from being installed. * Fixed a bug that prevented multiple bookmarks from being dragged-and-dropped. * Net Disks buttons (Mount, Unmount and Sync) should now update correctly. * Fixed a bug that prevented bookmarks from the Bookmarks menu opening Changes * Fixed a bug that made it difficult to edit bookmarks. Added a hidden pref key (SSHControlMaster) to turn it back on. It was causing performance and compatibility issues. * Improved the handling of Amazon S3 keychain items. * Fixed a bug that caused a Amazon S3 folder listing to contain the parent folder. * Removed the old Spotlight importer which was spewing messages to the console. 10.0.2 performs a more robust search for detached Net Disks. * Some people have reported missing Net Disks after switching between Interarchy 9 and Interarchy 10. * Changed the Amazon S3 "Access Key" label back to "Secret". The Interarchy menu, Net Disks and Scheduled Bookmarks rely on InterarchyHelper. * InterarchyHelper will now run only if it is needed. ![]() The latter doesn't mention Extended Passive Mode anywhere that I can find in the documentation (neither does Interarchy or Fetch that we can find).* Net Disks buttons (Mount, Unmount and Sync) should now update correctly. My web host says that Transmit and Cyberduck both work fine. But if your web host doesn't offer SSH, or you feel uncomfortable about the security risk, you can still change FTP clients (while you bug the Interarchy people to get with the program). Since SFTP tunnels through SSH, it doesn't get hung on the Extended Passive Mode nail. My solution-you knew I was going to tell you-is to use SFTP. Change FTP clients to one which supports Extended Passive Mode-not something I wanted to do. Open a range of ports on my firewall-IKES! No way. I took the problem to Google to see if there were any solutions. ![]() The command line FTP program can handle the 229 Extended Passive Mode request and knows what to do with the port number. Current restricted directory is /ĭrwx-x-x 12 32496 figure 4096 Nov 22 18:17. Here's what the command line app had to say:Ģ30-User figure has group access to: figureĢ30 OK. Maybe there was something Interarchy hid from me-or couldn't tell me. So, having dutifully notified the host and having been told that they had no problem logging in-oh lovely-there's a problem caused by something they changed, but apparently, now it's my problem! So I did what any self-respecting Machack would do: I retreated to my trusty command line FTP utility. There's no indication of anything wonky-not a whole lot of help, there. Here's the last few lines of the Interarchy Transcript from an unsuccessful FTP session: AdvertisementĢ20- Welcome to Pure-FTPd -Ģ27 Entering Passive Mode (66,225,221,43,46,222) Even checking the transcript doesn't help. Interarchy can log in successfully, but it won't list and the connection times out with a very misleading and unhelpful error (connection timeout -999960). Unfortunately, my FTP client of choice Interarchy 8.2.2, does not do Extended Passive Mode. If your FTP client can't understand that request, it chokes just after login. The basic difference is that Extended Passive Mode sets a random port for the connections to "listen" on so that it can work around a firewall (either yours or the host's). For "security reasons," web hosts are moving from using Passive Mode FTP connections to using Extended Passive Mode FTP connections. I'm sure you'll appreciate a solution that doesn't involve using Windows. It's well documented here and here, without resolution. The problem seems to be mostly Mac-specific. What exactly does this have to do with Macs? And then, when they tell me they can't fix it because it's a "feature," figuring out my own work-around. What annoys me most is having to spoon feed their tech support, figuring out exactly what the problem they caused is. Due to "hardware problems," they migrated hundreds of accounts, 26 of which belonged to me and my clients, to a new server with lots of different (and wonky) settings. Why is it that your (my, everyone's) web host always chooses major holidays to migrate to new servers? Oh yes, I spent most of yesterday troubleshooting, because my web host, with no warning at all, can-ex-ed my old server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |