Safari connectivity issues: InputManager folder fix; cache fix

We've been periodically covering issues where Safari cannot connect to some websites on the first one or two tries, often requiring multiple attempts (after which it appears to connect properly). Readers have suggested a number of potential fixes, none of which have helped all users. On Monday we covered a fix provided by reader David Oshel which involved deleting the /Library/InputManagers folder. A number of MacFixIt readers have reported success using this technique. For example, Thomas Ferrell writes:

"Trashing the Input Managers folder in my Users/myshortname/Library folder did the job for me with Safari 1.2.2 under Panther on a Dual G4/1.25GHz behind a cable modem & router. None of the other solutions helped."

Unfortunately, this fix doesn't seem to help all users; some MacFixIt readers are still having Safari connectivity issues, even after trying all of the fixes we've covered over the past month. We will continue to follow this story and cover any new fixes we find or receive from readers.

In terms of the effectiveness of deleting the /Library/InputManagers folder, a few caveats are in order. First, if you can't find this folder on your Mac, there's nothing wrong with your installation of Mac OS X. The folder is generally only created when an application requiring an InputManager plugin creates it. If you don't have it, you aren't using any software that requires such a plugin. Second, and more importantly, throwing away the entire folder may not be the best approach, as the InputManagers folder many contain useful and/or necessary files unrelated to Safari. For example, StuffIt Deluxe's MagicMenuEnabler Input Manager, which shouldn't affect Safari, is found in this folder if StuffIt Deluxe is installed. Likewise, Now Up-To-Date and Now Contact install plugins here to enable menu bar menus. A better approach is to figure out which of your InputManager plugins might be causing the problem.

In David's Oshel's case, what most likely fixed the problem was deleting the file called SIMBL. SIMBL is an Input Manager plugin used by a number of third-party software titles, the most relevant in this situation being PithHelmet, the Safari content filter. PithHelmet is a very popular utility that functions without problem for many users, but because it actively filters the content Safari receives, it's also a product that has frequently been reported as the source of Safari connection issues. By disabling/trashing the SIMBL file, PithHelmet was consequently disabled, and, in this case, Safari's connectivity was restored.

Cache fix? Another potential fix was submitted by MacFixIt reader Mark Hamilton, who found that emptying Safari's cache solved his connectivity issues:

"I was being plagued with Safari connection errors (mostly 'Web site could not be found'). I have a couple of Bookmarks that open multiple Web sites in tabbed windows and it was getting to the point where more than half of the sites wouldn't open on the first (and sometimes second or third) attempt. All the connection problems went away after I emptied my Safari cache."

Safari's cache is located at ~/Library/Caches/Safari.

Resources