iOS 11 can't connected to unsecured network??

I had the same issues but one thing worked for me. Follow the below steps and try:

Go to settings, then click on safari. After that enable the option that says "ask websites not to track me" under the privacy & security tab. Then try to connect the public wifi you want.

Worked for me.

I had the same issue with university network. Go to wi-fi settings and forget the uni network. Then conect to it (inputting all required data), submit that you trust this network and it should work. For me, that works with eduroam-networks in Uni.

I hope that help you.

We had the same issue at a couple school districts. It would connect and immediately disconnect before you could get the authentication pages.

The issue was that the device is trying to get to Captive.apple.com but the connection was being blocked because you are not authenticated yet and it would disconnect. We added a filter bypass for captive.apple.com and it works now.

We also contacted the web content appliance manufacturer who said they had dozens of pending support tickets due to this issue. They added it to a couple of their clients and it fixed them.

I was referring to authenticated web content filters, such as CIPAfilter or iBoss. The wireless would not stay connected long enough to display the authentication page. This was also an issue with another districts PFSense firewall captive portal. Allowing the filter/firewall bypass for captive.apple.com fixed the issue in our situations.

Does it frustrate anyone else that this is marked as solved, yet it's still a clunky and time-consuming solution? Having to help others at work with tech stuff, I know that I will be repeating this over and over again, and although I'm tech-savvy enough to know how to do this, the majority of my colleagues are not.

Why should it frustrate anyone? There is only one person who can mark post as solved, and that is the person who asked the question. As far as that person is concerned the problem is solved from their point of view, so presumably it solved their problem. If it did not solve yours, perhaps you have a different problem; instead of tagging on to a Solved problem, start your own thread by asking a NEW question.

We just had to deal with this issue where I work. I had to come up with some detailed instructions for the "technologically challenged" to be able to follow, so I figured I would shared them here, since we followed TakKunz and Xcamr's instructions to get iPhones to connect to an "unsecure" Aruba network too:

• Go to Settings

• Go to Wifi

• Find the network you want to connect to

• Tap on the small, blue "i" to the very right of it

• Scroll down to "Configure DNS"

• Tap Manual

• Under DNS SERVERS, enter this number: 192.1.1.1

• Tap Save on the top-right corner

• Wait a 2-3 minutes for the Wifi icon to appear at the top-left of the phone (next to the cellular "bars")

• Once the wifi icon appears, go back to the same place where you entered 192.1.1.1, delete it, tap "Automatic", then tap "Save" again on the top-right corner

• Go to browser (usually Safari), then try to go to any website

• If the browser complains about "unsafe connection" or "invalid certificate" or something like that, just tap on advanced and browse anyway

• Hit accept at the bottom of the acknowledgement page

TakKunz and Xcamr, thank you for your help.

In my testing, I found that when iOS11 trying to connect WiFi, will attempt to go the URL http://captive.apple.com automatically, but some companies will have proxy authentication or web authentication in their network and enforce to authenticate before access to the internet that causing the iOS11 drop the connection itself.

If you are IT administrator in your company, there are two ways to solve the problem.

Solution 1. Bypass captive.apple.com without any authentication on your proxy server or web authentication server and allow captive.apple.com traffic go through internet firewall.

Solution 2. On your internal dns server, create a new Forward Lookup Zones. The name must be "captive.apple.com". Do not need to create any dns records in this zone. How it works? When iOS11 trying to resolves name captive.apple.com, they will get an ip address of your dns server instead of real public ip. So, that the traffic will run in your network internally, not pass through the proxy or web authentication server.

If you are connecting to public WiFi and facing this problem. There is only one way to solve the problem that is manual fix an invalid dns server ip address on your iOS11 as Xcamr, higado2 provided in this post.

Hope this help

The whole point of captive.apple.com is to determine if the iOS device has a connection to the Internet. If it does not connect to captive.apple.com iOS displays whatever page the local network uses to capture login information. So if the network has HTTP login as a requirement the connection to captive.apple.com should not be allowed.

Thank you so much for this! It was the only suggestion on this thread that worked for me. I reset network settings a few times. Forgot networks and tried to log in again to no avail.

I even contacted Apple Support with disastrous results. They had me run through the same steps despite me telling them I already did myself. The agent even had me reset network settings while on the phone with him which of course disconnected me from the call. He never called me back despite asking for a callback number in the event we get disconnected.

So I complained via Twitter which usually gets me a quick response from most companies. They asked me a bunch of repetitive questions and I reiterated that this problem is with ALL public unsecured networks and the log in page no longer loads on Safari. I even listed all of the places I’ve gone to where it won’t connect (Starbucks, Coffee Bean, Target, a couple of malls, etc). They determined that the problem lies with all the individual networks I was trying to access and that I needed to contact all of them. Really??? Even after I insisted this was working fine on iOS 11 public beta and stopped working after I updated to the official iOS 11 and this it is too much of a coincidence that all of these networks decided to stop working at the same time, they stopped responding to me.

So aggravating that you get stupid solutions from their support staff.

iOS has displayed "unsecured network" on networks that do not enable at least WPA encryption since iOS 9. It was just informative; it did not prevent you from connecting to the network. And on iOS 11 it still doesn't prevent you from connecting. If you can't connect there is some other issue involved.

Unfortunately, I’m the having the same problem, with the same unsecured networks, in OS X High Sierra too...never had this issue with previous releases of OS X. Nonetheless, the same fix works for High Sierra...enter a dummy DNS entry, connect and then remove the dummy DNS entry.

In my case, the solution was easy: making sure I was trying to get to an HTTP site (e.g. http://www.google.com) rather than an HTTPS site to get a redirection to the network login page. With an https URL, Safari complained about not being able to set up a secured connection, which didn't happen with an http URL.

Thank you!!! This actually works! 100% on my iphone 7 ios11.03

just follow EACH AND EVERY step:

Much more detailed!

1. go to Settings

2. Wi-fi

3. Click on the “i” next to the network you’re about to join

4. then FORGET THIS NETWORK

5. click the “i” again on the same network

6. Configure DNS

7. Click manual -> Add Server “192.1.1.1” then SAVE

8. Join network and wait for the wifi logo to appear on the top left corner of your screen.

9. Once it appears click the “i” again then Configure DNS

10. delete the Manual Server you added then click Automatic then SAVE

11. Go to Safari and open any website

12. Welcome back to reality!!

Hope this works! I’ve been struggling for about a month then I found the solution here.

No, it is NOT a big bug. If you don't see the login page either forget the network or open Safari and go to google.com. This is nothing new; if you connect to a network that you have previously connected to iOS doesn't check again to see if you need to log in; it assumes you are already logged in. Nothing new here.