This also happens on our new Lenovo N23 Yoga's. So might be all devices. At the login screen - you can click "Sign in if you have signed in before" and then click back and then it lets you sign in. Nasty little bug!

Tested on some Acer Chromeboxes and LG Chromebases and they were fine - so only some devices.

Video of issue: https://drive.google.com/file/d/0B0vcQ-UNCMvIU29iQVdrOVNxbmM/view?usp=sharing
This is on an Asus Chromebox. So you can click "Sign in if you have signed in before" and then click back and its OK.

Also having issues with Acer C720P Chromebooks. Only seems to affect on first boot after update.

I have same issue with Asus Flip C100 in Beta channel.  Has been happening for the past couple releases.  I just updated to v62.0.3202.43 and still occurs.

In testing, I notice that if you toggle off wifi and toggle it back on from the system tray it seems to "find" the network and shows the login page.

Seeing the same issue, pressing back allows me to log in.

Model: Acer C720 Chromebook
Google Chrome Version: 61.0.3163.120
Platform Version: 9765.81.0 (Official Build) stable-channel peppy
Firmware Version: Google_Peppy.4389.117.0

Model: Samsung Chromebook
Google Chrome Version: 61.0.3163.120
Platform Version: 9765.81.0 (Official Build) stable-channel daisy
Firmware Version: Google_Snow.2695.117.0

alemate@ can you PTAL? This is a pretty bad bug.
rkc@ is this RBS?

There is a workaround or this, right? If so, this can't be RBS for 62. Maybe for 63.

We are having the same issue with a Lenovo N23.  I have moved one to the developer channel (63.0.3239.7) and it has not had a problem since.  There are 2 options here.  After the Developer channel it will more to the beta channel and from there to the stable channel.  One: Wait for this process to complete (I have no Idea how long that will take). Two: Move the Chromebooks that have the problem to the developer channel.  sidenote: A Chromebook will always upgrade on its own (if allowed) but, it will never downgrade on its own.  This means if you update them to 63.0.3239.7 them move them back to the stale channel it will not upgrade again until the stable channel version is higher than the installed version.

We are having this same issue with Acer C710s and C740s.  We were able to disable auto-updates before this hit more devices.  Currently have 6 out of about 2100 Chromebooks experiencing this.

This issue seems to be intermittent and currently we can either disable then enable wifi to get to the sign in page, or click on "sign in as an existing user", clicking back then signing in. 

Same here w/a few Samsung 2's and Cisco AP's. I've noticed switching wifi networks will get to the login sometimes as well. Also played with putting them in different org's and noticed those with "Always show usernames and pictures." got the newer login w/no network screen.

Can confirm same issue at home.  User data must be set to erase as well to replicate.  Turning off auto updates for a bit.

Same issue in our district using Dell Chromebook 11; Cisco AP's. Only CBooks running version 61.

Marking this as RBS for M-63 so we are sure not to miss it. alemate@, let me know if anything we can do to help.

Sounds like b/66923649 .
Assigning to Andrew.

After offline discussion this sounds like a different issue.
(taking this issue back).

This needs to be re-checked on M62 after https://chromium-review.googlesource.com/c/chromium/src/+/734122 (landed today, so no builds with it exists).

M63 should not be affected by this if the Cl above fixed the issue.

Could someone verify this issue on the dev channel (which should be M63) ?

As comment #11 says, this issue might have been fixed in M63.

Could someone else verify this?
It likely means that next M62 build should be fixed.

This is definitely an issue.  We have standardized on Dell and I can reproduce the issue on original Dell Chromebook 11 units, Chromebook 3120 units, and Chromebook 3180 units...so across 3 different hardware revisions.  I actually see the issue on 2 versions of ChromeOS:  Stable Channel 63.0.3163.120 64-bit and Stable Channel 61.0.3163.123.  Boot them up and odds are you're going to get the "Network not available" message even though it shows as being connected to the correct SSID.  Toggle wifi off and back on, and it connects right up.  We're a school district with over 7300 Chromebooks in student hands, so it's going to be a big deal for us.  I've restricted our version to 60.* in the management console, but I know the genie is already out of the bottle to some extent.

Same issue at my school on 4 separate models so definitely pointing to OS as cause. Also capped our versions at 60 through the GMC, however, issue was discovered after many auto-updated so going to have to roll back a lot unless a patch come out soon.

Yes this issue runs the gambit on all versions of Dell Chromebooks and is increasingly frustrating.

Could you send a feedback report when this happened?
1) Go through OOBE.
2) Try to add new user (fail)
3) Sigh in as Guest, Press Alt+Shift+I , fill up e-mail field so that we could find your feedback report, send.

Feedback report will send system logs.

Please, add a note here after your report, so that I could start looking for it.

Sent a report. Did not see email field, so I added the issue number, as well as my email address in the main box.

Could you also check DNS of your access point?

Basically, when you connect to WiFi, you usually get DNS IPs via DHCP.
If you open status tray and click on the active connection, you'll see parameters. There is a list of Name servers. What is in it? Does that IP belong to your WiFi Access Point, or it is a name server somewhere beyond the WiFi Access Point?

Basically, some access point have proxy DNS in them, which may be buggy.

If you have a non-ChromeOS machine, could you check that different DNS requests work through the DNS supplied by the AP:

(replace X.X.X.X by the DNS IP from your WiFi connection status)
host -t A google.com X.X.X.X 
host -t MX google.com X.X.X.X
host -t AAAA google.com X.X.X.X
host -t PTR <your_IP_here> X.X.X.X

These are Linux commands, but you should be able to find equivalents for your OS.
Basically, we need to check that DNS returns a reasonable answer in reasonable time. I may return NOT_FOUND for any of them (except the first one), but it should not wait long.

alemate@

It is a name server somewhere beyond the access point. It is our standard for our network. I checked with our network admin and we do not have any proxy DNS on the APs.

I ran all those commands on my Macbook and it returned the results instantly. Did not get any NOT_FOUND for the results.

Thank you for testing DNS.

I found your report, thank you.

Re# 28 - you are using R61, which does not have the changes.
You need DEV channel and M63.
(The fix will get into M62, but I don't think there is a new build with the fix yet).

alemate@ I am unable to get it to fail while on M63. I sent the report regardless.

I've also verified that this does not reproduce in M63. I will check on M62 once a new build completes.

Looking at the report so far, it doesn't look like it is related to Sign In. You probably don't need anything from the Sign In team, but do let us know if we need to help with anything.

Let's wait for another M62 build.

I could not reproduce this issue on any device, so I probably cannot test the fix myself.

Re#31: this probably tells us that the issue is fixed. We are waiting for the fix to appear in M62.

We are having the same issue at our school district.  The one in my hand now is an older HP Chromebook 14 running v61.0.3163.123.  We are also having it on brand new Lenovo N42s.  Pressing back button for us does nothing.  Have to either turn it off and back on multiple times or turn wifi off and on multiple times.  Very frustrating for users with over 2,000 chromebooks out there.

The newest stable channel update (M62 (62.0.3202.74)) seems to have fixed this.

Currently testing two Acer C710 Chromebooks on 62.0.3202.74 and after about 20 power cycles each, I have not seen the issue at all.  I will continue testing and report back if the issue still persists.

How can we get this update onto our chromebooks?  We need to move them all into the dev channel?

M62 has the fix and should be rolling out to stable channel now.

Any idea when this is going to be available on the Acer C731 and C731t models? I've seen notes that devices that currently run the play store are having their update delayed.

I think that M62 should be out for now, and the problem is fixed.