Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517443 - Captive portal detector opened wrong URL
Summary: Captive portal detector opened wrong URL
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-25 12:01 UTC by fednuc
Modified: 2018-06-28 11:50 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description fednuc 2017-11-25 12:01:37 UTC
I was greeted this morning with a (GNOME?) portal login window that had opened

I'm not sure if there was a network blip or not (though my ISP's stats graph doesn't show any outages overnight), but that URL is wrong in two ways:

* GNOME's commectivity checker endpoint is (not the domain root).
* Fedora AFAIK is supposed to be using , according to /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf

I'm guessing the window *stayed* open because the expected response wasn't received, since it was a directory index instead of "NetworkManager is online" (GNOME config.) or "OK" (Fedora config.), so the checker assumed it was a portal login page.

I don't know if this is a Fedora-specific, GNOME or NetworkManager bug then TBH.

Anecdotally, someone on #fedora on IRC said they saw exactly the same thing on F27 yesterday.

Comment 1 Thomas Haller 2017-11-27 09:39:54 UTC
Looks also like

Comment 2 fednuc 2018-06-28 11:50:52 UTC
This happened again today on Fedora 28 Workstation, on 2 different machines, 3 separate accounts, exactly as described above.

Note You need to log in before you can comment on or make changes to this bug.