OSX Lion, WiFi, & Https

So I upgraded the MBP to Lion last night. Overall this was a sweet upgrade, as things should be. Open the App Store, Click the Install Button, enter your Apple ID to consent payment, and let it do it’s thang.

The download too about 30 mins, and the install about 28. The configuration to make it useable has taken the best part of a day. Mainly trying to find fixes online, rather than implementing the actual fix itself.

I found three main issues:

1. Natural Scrolling

This may be natural for Steve Jobs, but imho this was as counter-intuitive as it’s possible to be. When I slide my fingers up, I expect the page to scroll down. This was a quick fix. Head into System Preferences > Trackpad > Scroll & Zoom, and uncheck “Scroll Direction: Natural”


2. Getting to https sites on WiFi

This was the most frustrating error. Mostly because I can’t be the only person experiencing the issue (hence this blog post), yet there was a dearth of support or information on the web.

The frustration was exacerbated because I couldn’t access my email (both personal and business run on domains pointed at gmail, which uses https) and even the discussion forums on Apple’s site used https. (doh!)

Also to say that this affected both Safari and Chrome (my browser of choice) on OSX, but neither Chrome, or IE on the Parallels Windows 7 VM. Once I got that working (see below)

So this wasn’t a layer 1 (physical), 2 (logical), or 3 (Transport) issue. Neither was it an issue that affected the Wireless Router, or any of the other computers on the network.

The fix is relatively simple. On Lion you have to check both Auto Discover, and Auto Configure for your Internet Proxy. Why? No idea. But there you go…

To do this Network Preferences > Advanced > Proxies > Check the top two items


3. Parallels

In my hunt to fix the https issue, I fired up Parallels to search on Windows 7, as well as to diagnose the problem at a network layer. Imagine my frustration when I couldn’t actually get to the Windows 7 VM.

It was running, and I could see it in Expose. Just couldn’t actually get to the window.

Fortunately Parallels has a far better support site than Apple, and the fix was simple. The issue was having the Parallels session in another desktop using Spaces before the upgrade. The solution was to delete all of the extra Spaces Desktops. This put the vm on the primary desktop.

It’s a simple matter to create new spaces and pop the VM back into one of these again.


My 24 hour review is that Lion is good. Support is limited. I hope this blog helps you resolve some of the small niggles you may experience working with OSX Lion

8 thoughts on “OSX Lion, WiFi, & Https”

  1. Lion gave me no problem reaching https sites on WiFi without proxy, but at work I got into the trouble you can read about here:

    I am not going to experiment by trying to install Lion again in order to try the solution given on this very page because at work I cannot use automatic proxy recovery or configuration, as the proxy server must be manually configured in the browser.

    Nevertheless, I’d like to learn about a solution to this problem. I wouldn’t even mind it if that solution came from Apple 😉

  2. I’ve been experiencing the same problem with Wi-Fi and https.
    You’re not the only one.
    Works fine with iPhone, iPad and WinXP via vmware but not on OSX Lion.
    Hope your tips help me out.


    A. Souza

  3. Sadly, this seemed not to work for me. What has been most frustrating during this never-ending upgrade fiasco is that at times everything works normally and fast; at other times, unpredictably, according to no rhyme or reason that I can discern, everything goes pear-shaped: pages take anywhere from 5 to 20 minutes to load, if they load at all; timeout errors; ssl errors, etc.

    My specs: two-year-old 17-inch MPB 2.6 GHz Intel Core 2 Duo with 4 GB ram and 145 GB free on the hard drive. 10.7.1. Latest version of Safari. Connectivity problems are equally bad if not worse in the other major browsers.

    I did try checking auto proxy discovery and automatic proxy configuration (also, following your screenshot, I checked exclude simple hostnames); I would then save and apply settings, but when I went back into this tab, I noticed that automatic proxy configuration had somehow gotten unchecked (it wouldn’t stick). Not sure why, or what that means.

    I have been to Apple several times over the past week and they have been just about as stumped as I am. At one point we thought it was a corrupt systemconfig file, so we trashed it and rebooted (and I have since repeated that out of desperation a couple of times); I have reinstalled Lion from a thumb drive a few times now. We always seem to get it working and I feel hopeful and then it gets all gummed up again. The guys at the genius bar noticed that I had entered google’s DNS servers and recommended against doing that because google’s servers could be redirecting to distant servers that would only slow down the process, so I re-entered local ISP server info, and that sucked, too. So now I’m using OpenDNS’ servers; that seemed to improve things at first but, as usual, everything has gotten bogged down and paralyzed again.

    Also, I had read about IPv6 posing problems, so I switched to Link-local only, which the guys at the genius bar confirmed was probably the way to go. As usual: helped at first, but before too long the system bugged out again.

    I have gotten two new routers (first a Buffalo n router, now an Airport Express) in a desperate attempt simply to get things to work again. Seemed to help at first, then bugged out. I am absolutely at the end of my rope.

  4. Thanks for the WiFi tip – my computer had become nearly useless because many applications use secure web connections (Evernote, etc.) and those were broken too. Your suggestion to turn on the proxy settings fixed tons of problems I was having.

  5. Not sure if this will help anyone else but I was having problems with Lion when trying to connect to an office Wifi. Somehow it was refusing to connect to the authentication webpage which was a HTTPS address, I removed the S from the HTTPS address in Safari and was then able to authenticate and get online.

  6. I’m figuring out (on a friend’s mac Air, I still have to upgrade) that this is an issue with keychain and the way it handles certificates, though I cannot be more specific.

    The solution found here:
    forced chrome and safari to accept the certificate of the login page, so I was able to login, but other https sites (although I have yet to do extended teste) apparently not.

    I really don’t know what to do exactly to solve this, but I think that at least this is a step ahead…


  7. I have the same problem with https, it works most of the time but now and then it stops working and checking the proxy settings is not working. Any other suggestions? I have to reboot the computer. I never had this problem with Snow Leopard om my MBA.

  8. Same problem here. Proxy settings don’t fix it for me though. I have to specify a configuration URL or file for the setting to save.

Leave a Reply

Your email address will not be published. Required fields are marked *