Unable to open Safari on Yosemite behind proxy

Question

fluxzzz Author

Level 1

0 points

Unable to open Safari on Yosemite behind proxy

Guys,

I am on a corporate network, and i am having issues with a new MBP 12,1 on Yosemite.

I am not able to open safari, and my system proxy does not seem to be picked up, globally.

- I did set the proxy in the network preferences.

- I exported the http_proxy and https_proxy in my .profile

- I have copied the login certificates from local to system

All to no avail.

When i open safari i get a lot of messages like these:

The first is only once, and perhaps the most important.

Apr 2 08:04:21 xxx com.apple.WebKit.WebContent[1932]: *** WARNING: CFMachPortSetInvalidationCallBack() called on a CFMachPort with a Mach port (0xcc17) which does not have any send rights. This is not going to work. Callback function: 0x7fff90c51a34

Apr 2 08:04:21 xxx com.apple.WebKit.WebContent[1932]: Stream 0x7fafe04572a0 is sending an event before being opened

I am also seeing these sometimes

The operation couldn’t be completed. (com.apple.security.xpc error 3 - <connection: 0x7fdb09f16fb0> { name = com.apple.securityd.xpc, listener = false, pid = 0, euid = 4294967295, egid = 4294967295, asid = 4294967295 }: Connection invalid)

Any help plz?

Posted on Apr 1, 2015 11:26 PM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Apr 2, 2015 9:56 AM in response to fluxzzz

Uncheck Secure Web Proxy and apply the change. Any difference?

Reply

Answer 2

fluxzzz Author

Level 1

0 points

Apr 12, 2015 11:07 PM in response to Linc Davis

Hi Linc,

Thanks for your reply, and sorry for the late response, i was out of office last week.

So I unchecked the https proxy, and now i am able to access NON https urls via safari.

As to be expected though, https urls do not work.

Furthermore if i disable https, chrome is not able to resolve https urls neither. Previously it was though, so i reenabled the https proxy.

So, i think you are definetly on the right track with the https proxy, but it appears as if osx (safari) is having troubles with one proxy address for multiple protocols.

Any more thoughts on resolving this?

Reply