Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iOS 6 update - cannot connect to wifi with proxy

We have 300 IPad 2's to configure and they cant connect to our wifi. Since the upgrade we can no longer connect our proxy network as we did before. We use an explicit proxy where we manually enter the proxy address. WPA2 Security. We contacted Apple support and after an hour they said they didn’t know how to resolve the issue and needed to research. This was 5 days ago so im reaching out to the Apple community. We contacted our proxy support BlueCoat and they have escalated the issue to their top level support. After the iOS 6 update we are basically dead in the water.


We select DHCP under our network settings and select Manual under the http Proxy settings. After filling in the Server, port, authentication info and try to connect, it immediately brings up a safari page that states "Error Opening Page - Hotspot login cannot open the page because it could not connect to the server".


The other issue we have even with iOS 5 is we could not connect to https sites.

iPad 2, iOS 6

Posted on Sep 26, 2012 6:14 AM

Reply
21 replies

Oct 1, 2012 12:20 AM in response to SJ_School

Hi,


I work at a College in Australia and saw this post. We haven't had the same problems.. iOS 6 seems to be working without issue. However I note you mention:


SJ_School wrote:


The other issue we have even with iOS 5 is we could not connect to https sites.


This measns that your proxy is not working appropriately. You see we found out, (by accidently typing our proxy address incorrectly) that we could still visit all http sites, but could not see our https sites.


Have you tried entering in your Proxies address into safari, and seeing if you can see the text file? It would seem to me at least, that for some reason your iPads are not able to read the file. This may be due to permissions on the file. Check this out if it is being run on a Linux based OS.

Oct 1, 2012 6:51 AM in response to SJ_School

HI


I'm an engineer at a Hospital looking after BYOD.

We've just had the same as above, users bring in ipdas and phone upgraded to IOS6.

We're using a Cisco wireless nework and bluecoat SG in trnasparent mode.

If I put a static bypas in the ipad connects to the web page "sucsesfull", soon as I take the by pass out, this no longer works.

Had no problems with IOS 5.

Do have the same kind of problem with Android, but in a call with supplier regarding this.


Will be interested to see the out come as we've tried all these hard resets.


Luckly non of coporate devices have been upgraded yet.


cheers

Oct 1, 2012 8:47 AM in response to SJ_School

Our school is having a similar problem with the iPads that were updated to iOS6. We don't use a proxy but we have a Sonicwall and the user has to login to the Sonicwall before the device can have Internet access.


Here is what I have found and maybe it will help you. The problem (for us) is that immediately after the iPad is connected to our Wifi it tries to contact the Apple servers in California. This connection is blocked by the firewall because the user has not had the opportunity to login to the firewall. The iPad opens a screen that is not part of Safari to allow the user to log into the firewall but they can't because a pop-up window is needed and this application has no settings to allow pop-ups. Under normal circumstances the user would open Safari and login but if we try to switch to Safari it cancels the connection attempt and disconnects from the Wifi. Obviously, this means we no longer have a connection to our Sonicwall.


The trick I am using to make it work is this. (Keep in mind, we don't normally use proxy settings). I set the http proxy setting for the particular network to AUTO. This causes enough confusion in the iPad that, if I am quick enough, I can open Safari and log into the firewall real quick. Once that is done it will work fine....until the user goes to a different access point.

Oct 12, 2012 6:39 AM in response to MrUs

Actually what I was wondering is if you could tell me what gsp1.apple.com is actually used for. Since upgrading our iPads to iOS 6 we cannot get an IP until our iPads connect to that address. We use an appliance called Websence which requires authentication before accessing the internet, as soon as you connect to an SSID you get a Websence prompt, after authentication you get a blank page with only the word success on it. After tracking the location we found that it is going to gsp1.apple.com and just wondered if there was a way areound this, and why this stops our iPads from getting an IP if they done connect to it.

Oct 12, 2012 2:41 PM in response to SJ_School

Hi


I tried the 2 urls in blue coat, put them to not authenticate, so should be no problem. Didn't work, then just put a wild card in for apple.com, this still doesn't work.

Think may have to do with session cookies, every time a new browser page is opened you need to reauthnticate or or will loose the wifi settings.


if I put the iPad in a static bypass there is no problem. So seems to be the way it handles cookies.

Somehow I did get it to access a website but then it failed again.


We're are just using wpa2psk for the WLAN for iPad, but the blue coat require windows authentication via Iwa.


Hope this helps

Jan 9, 2013 6:47 AM in response to SJ_School

Hello,


Just found following On the Blue Coat support site


Problem Description

ITunes application on the Apple phones uses different headers than the standard HTTP headers to represent the expired objects time.
These headers are not recognized by the proxy since they are not standard HTTP, and hence the proxy may server expired objects that can lead to terminating the application.
Please see both the request and respond below ( the application is using x-apple-lok-expire-date header


Resolution


Apply the policy below to your local policy file to bypass cache for the traffic coming from itunes.apple.com and any request using it as referer

<Proxy>

request.header.Referer="itunes.apple.com" bypass_cache(yes)

url.domain="itunes.apple.com" bypass_cache(yes)




Hope this helps

iOS 6 update - cannot connect to wifi with proxy

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.