New Mac OS X Client v.47 Released

SupportSupport
in Software and System Updates
Hey all!

We've just released an updated version of our Mac OS X VPN application, which you can find here: https://www.privateinternetaccess.com/installer/download_installer_osx

SHA-256 Checksum: 65fc7a1111b2850b3f35ecd4bcb53601f96a781d0fbc275c6ae0b17b27a53525

This new version (v47) introduces a number of new enhancements to our already very solid Mac application. The new changes are as follows:

1) Added a slow speed report submission form to the application's menu bar context menu
2) Updated OpenSSL to version 1.0.1p
3) Automatically create an exception in the Mac firewall to allow pia_openvpn, to correct connectivity issues when using UDP (the default protocol)
4) Updated menu bar icons to make it easier to distinguish between "Connecting" and "Connected" states

Comments

  • nezzznezzz
    Still doesn't work on El Capitan.
  • secure4mesecure4me
    You have to manually set the PIA DNS servers, to get the client to work. Not sure why this problem is occurring.
  • nezzznezzz
    Yes I know the workaround but this is ridiculous man, El Capitan has been out for 3 months now in beta and its probably going to be released in the next week or so. Its pretty ridiculous by my standards. If we were going to be kept waiting, at least release a proper working version for El Capitan where we don't need to do these unnecessary things.
  • secure4mesecure4me
    This client does not reconnect very good after Macbook wakes from hibernation, just sits there trying to connect.  Last version would connect after hibernation without issue.
  • miguelfp1miguelfp1
    El Capitan Gold Master was also just released, Final version should be coming very soon.
  • nightshrillnightshrill
    edited September 2015
    Yes I know the workaround but this is ridiculous man, El Capitan has been out for 3 months now in beta and its probably going to be released in the next week or so. Its pretty ridiculous by my standards. If we were going to be kept waiting, at least release a proper working version for El Capitan where we don't need to do these unnecessary things.
    Yes, PIA has been out in BETA for 3 months, where code is volatile and can change, and like all betas it is not recommended to use on your main system because of that (despite the fact that many of us do just that). PIA, like many developers does not develop based on the betas, they've outright stated this in other threads, if you need PIA to work with El Capitan then maybe yous hould wait until the actual release date and use yosemite in the mean time. 

    All that being said I just updated to the GM Candidate, reset the DNS servers to the default PIA ones and it is working perfectly with no workarounds on a late 2014 retina imac.

    EDIT: So for some reason its working fine with the default DNS servers on Chrome, but not with Safari or Firefox... so see the workaround referred to by secure4me
  • nezzznezzz
    No, in a public beta phase code does not change so much, only bug fixes and slight improvements. In 3 months, it could not have been changed so much until it was broken. It's still ridiculous that PIA can't get an app out which will work.
  • xaanderxaander
    You have to manually set the PIA DNS servers, to get the client to work. Not sure why this problem is occurring.
    Can someone explain how to do this? I updated to El Capitan GM today and neither Safari nor App Store work when PIA is turned on.

  • nightshrillnightshrill
    No, in a public beta phase code does not change so much, only bug fixes and slight improvements. In 3 months, it could not have been changed so much until it was broken. It's still ridiculous that PIA can't get an app out which will work.
    You intentinoally ignored the parts where I stated explicitly PIA does not develop for beta applications, as most developers do not (at least for public release). Unless you somehow secretly have all the code changes apple has made (which they do not even release to developers who pay $100 a year for their development releases, trust me - i know) then you have no idea what the heck you are talking about and should just stop trolling the board. 


    You have to manually set the PIA DNS servers, to get the client to work. Not sure why this problem is occurring.
    Can someone explain how to do this? I updated to El Capitan GM today and neither Safari nor App Store work when PIA is turned on.

    In response to xaander you would go into first connect to PIA (any server will do, however given my location I went with US East) system preferences -> network -> (whatever you're active internet connection is, wi-fi, ethernet, etc) -> advanced -> DNS | then under "DNS Servers:" you would manually enter the PIA DNS Servers and select one of the sets of #'s and manually enter in both DNS servers for PIA which are:

    209.222.18.222
    209.222.18.218

    that should allow you to connect via Safari & App Store (which I was able to do after this workaround as well running the GM)
  • xaanderxaander
    No, in a public beta phase code does not change so much, only bug fixes and slight improvements. In 3 months, it could not have been changed so much until it was broken. It's still ridiculous that PIA can't get an app out which will work.
    You intentinoally ignored the parts where I stated explicitly PIA does not develop for beta applications, as most developers do not (at least for public release). Unless you somehow secretly have all the code changes apple has made (which they do not even release to developers who pay $100 a year for their development releases, trust me - i know) then you have no idea what the heck you are talking about and should just stop trolling the board. 


    You have to manually set the PIA DNS servers, to get the client to work. Not sure why this problem is occurring.
    Can someone explain how to do this? I updated to El Capitan GM today and neither Safari nor App Store work when PIA is turned on.

    In response to xaander you would go into first connect to PIA (any server will do, however given my location I went with US East) system preferences -> network -> (whatever you're active internet connection is, wi-fi, ethernet, etc) -> advanced -> DNS | then under "DNS Servers:" you would manually enter the PIA DNS Servers and select one of the sets of #'s and manually enter in both DNS servers for PIA which are:

    209.222.18.222
    209.222.18.218

    that should allow you to connect via Safari & App Store (which I was able to do after this workaround as well running the GM)
    Thanks for this.
    I already have both of the numbers above listed as DNS servers. Safari still isn't working :/


  • secure4mesecure4me
    Xander, you still need to enter the DNS server address manually. You see it there already because the OS "thinks" it is assigned. When you go to enter it, the current assigned IP will zero out.
  • xaanderxaander
    Xander, you still need to enter the DNS server address manually. You see it there already because the OS "thinks" it is assigned. When you go to enter it, the current assigned IP will zero out.
    That did the trick!  Thanks!
  • secure4mesecure4me
    I'm giving viscosity client a try. It's $9 to buy, after 30 day trail, but you can set which DNS servers to use in viscosity without editing OS X networking and so far no issues with reconnecting automatically from hibernation.
  • anon666anon666
    I'm giving viscosity client a try. It's $9 to buy, after 30 day trail, but you can set which DNS servers to use in viscosity without editing OS X networking and so far no issues with reconnecting automatically from hibernation.
    Viscosity you say? I just now checked them out as a possible solution to this problem. Here's a cut and paste from their site,

    "The Mac's keychain and Windows's credential system are used to make sure your details are kept safe and secure."

    Yeah, great. Lol. So my password info is "protected" by microsoft or apple. Two of Prism's top collaborators. Obviously,. I use apple products, but I prefer to sandbox as much as possible. And I would think not sandboxing your VPN credentials would be a major oversight of security.
  • Osborne_CoxOsborne_Cox
    Thanks for the new client, and for updating the icons. ^^

    These last few days I've had problems connecting with v46, with the client crashing, and wondered if a new version was available. :P
  • Osborne_CoxOsborne_Cox
    Anyone else have problems with v47? When PIA crashes (trying to quit the app when it gets stuck in "connecting"), now I have multiple instances of Ruby to force quit as well as reportcrash. :(

    I have gone back to v46 and switched to TCP. Starting to wonder about alternative VPNs...




    :(
  • dfritter4dfritter4
    edited September 2015
    s
  • dfritter4dfritter4
    edited September 2015
    can't get the quote function to work correctly so just ignore this comment since I can't delete it now :/
Sign In or Register to comment.