Connecting to Liahona WiFi

I've been having trouble connecting to Liahona almost from the beginning. When connecting, the page where you would click 'Accept' to continue to the internet never comes up. A couple of pages are spawned automatically in my browser (chrome) like it's trying to find the acceptance page, but they just show the spinning wheel forever, never resolving. What I have found can get past this is to get it in this state and then connect to my cell phone as a hotspot. Usually, (not every time) this allows the acceptance page(s) (sometimes there ends up two of them) to resolve so I can click the acceptance button. once this is done I can reconnect to Liahona and now use it.

I've been using this process for months now, but it's getting annoying that I have to do a 10 minute dance to connect to the Wifi every week before I can get the Zoom meeting going. I have to do this process with either of the laptops that I typically bring to church. One is my work laptop that could easily have security software and settings that could be blamed for this, but the other is my own person laptop that has nothing more than an anti virus for security. Both are windows 10 pro, and both are Lenovo ThinkPads, though different series models.

My wife has complained similarly about connecting from her phone (Android, not sure what version), finding that she must turn on the wireless data (she typically keeps it off) before the acceptance page will come up on her phone. I've personally given up connecting to the Liahona network with my phone. It's just too much of a pain to put up with for a phone that has another option.

Does anyone have any ideas what the problem could be? I know it's not the DNS settings in my computers. That is set to obtain automatically through the DHCP service along with the IP addresses. I tend to think it's a problem with the router not letting the request for the acceptance page through. Like I'm stuck behind a wall asking to come in, but I can't ask without being allowed on the other side of the wall.

What happens if the first site you try to go to is a church site, like the main page churchofjesuschrist.org?

I've given up trying to connect my laptop to Liahona, the splash page never comes up, and I've tried a myriad of suggestions I've seen shared here on the Forum ever since the authentication was first implemented. Nobody else in our unit seems to have issues connecting their laptops, and since I am lucky enough to have a cellphone wifi hotspot, I simply use that. But I remain hopeful that eventually somebody's solution will also work for me!

BrianEdwards wrote:I've given up trying to connect my laptop to Liahona, the splash page never comes up,

Your laptop wouldn't be a Mac, would it? Those seem to have troubles for some reason.

Dell 7530. It does have VPN and other things installed, nothing out of the ordinary, but one of which is likely the culprit.

BrianEdwards wrote:Dell 7530. It does have VPN and other things installed, nothing out of the ordinary, but one of which is likely the culprit.

Try turning the VPN off. It is most likely interfering with you getting the splash screen. Your VPN server is getting the splash screen but it is not being passed on to you. With the VPN off you can receive and acknowledge the splash screen. Then if your VPN service supports it and plays well with the church firewall you can turn it back on to continue your Internet connection. Otherwise you will have to leave the VPN off when using the Liahona network.

jdlessley wrote:Try turning the VPN off.

Agreed.

It's possible that VPNs are filtered out, since they bypass any restrictions.

I tried the VPN approach again on Sunday, no luck. Might be a 'user issue', but I believe I successfully turned off the VPN and then tried a variety of ways to get the Liahona splash screen.

Note: I've even tried using "Lehi", but I can't get an internet connection (although it does successfully connect using the password the Stake supplied). Again, I'm thinking it's just not liking my laptop...

BrianEdwards wrote:Note: I've even tried using "Lehi", but I can't get an internet connection (although it does successfully connect using the password the Stake supplied). Again, I'm thinking it's just not liking my laptop...

Is the DNS set to "automatic" or something else? The church only supports the DNS they supply.

russellhltn wrote:What happens if the first site you try to go to is a church site, like the main page churchofjesuschrist.org?

I've tried visiting church websites while waiting for the "agree to terms" page, and they don't resolve either.

I also have this issue currently. I'm using a Ubuntu 18 laptop. I never get the splash "continue to internet" page. I have not had this kind of issue at hotels which share a similar method.

I'd make sure you're using the DNS provided by the network and not some other - perhaps as some kind of performance improvement or filtering. It's possible the hotel systems are intercepting DNS calls instead of blocking them.

Were you able to get the captive portal detection to work? If not try resetting the NIC

I had this same issue today and was able to finally connect by allowing pop ups. Because they were disabled they page that opens up where you connect to the internet was never opening. Once I went into my settings in Chrome and did that I was able to connect. There is also a way you can block all pop up except from approved sites. You should see it in the settings when you go to enable pop ups. Hope this helps

For those on Mac, this worked for me:

• Click the Apple icon in top left

• Select System Preferences

• Select Network

• Select Wi-Fi

• Click "Advanced"

• Select the "DNS" tab

• Make sure there is no entry there that is not greyed out; the font will look white if there is an existing entry. The church configures their own DNS addresses when you connect to their network. If it is working properly you should probably see two greyed out IP addresses. In my case they were 8.34.34.101 and 8.35.35.101. What I found was that I had a permanent DNS entry that I had previously setup.

• To delete the address simply click on the entry and click the "-" (minus) button.

• Click OK

Once I did all of that it popped up the splash screen. Hopefully this helps someone.

I have an older Mac (2011), and have the symptom where the authentication screen never appears after the WiFi connects. The following works for me:

- Open Safari.
- Open an incognito window.
- Browse to captive.apple.com.

This loads the elusive, “Continue to the Internet” screen.

Hopefully this can be useful to someone.

milnerm1 wrote: Sun Nov 21, 2021 3:28 pm I have an older Mac (2011), and have the symptom where the authentication screen never appears after the WiFi connects. The following works for me:

- Open Safari.
- Open an incognito window.
- Browse to captive.apple.com.

This loads the elusive, “Continue to the Internet” screen.

Hopefully this can be useful to someone.

This did the trick for me (I did it on Chrome instead though). Was previously restarting my Macbook Pro every time in order to properly have the TOU page appear. Thanks for posting, cheers

The DNS trick worked for me. Previously had 8.8.8.8 and 8.8.4.4 in place, but removing those helped

BrianEdwards wrote: Fri Jan 22, 2021 8:20 pm I've given up trying to connect my laptop to Liahona, the splash page never comes up, and I've tried a myriad of suggestions I've seen shared here on the Forum ever since the authentication was first implemented. Nobody else in our unit seems to have issues connecting their laptops, and since I am lucky enough to have a cellphone wifi hotspot, I simply use that. But I remain hopeful that eventually somebody's solution will also work for me!

The easiest solution is to have 2 internet browsers in your computer. When Chrome doesn't pop up the sign in WiFi website, then Mozilla Firefox does work.
Try it I promise it will give you result

Just to tie up my loose ends, my laptop hard drive crashed a while ago, and after installing a new hard drive, the problem went away. I didn't do the task myself (my IT skills are woefully lacking), but something in the changeover caused my laptop to now connect flawlessly to Liahona. So unfortunately although I had tried Chrome, IE, and Edge, I cannot verify if the Firefox suggestion would have been the magic bullet!

BrianEdwards wrote: Tue Aug 30, 2022 11:57 am Just to tie up my loose ends, my laptop hard drive crashed a while ago, and after installing a new hard drive, the problem went away.

The ultimate clearing of cache and cookies sure did the trick, although I admit that even that does not always work.

lajackson wrote: Tue Aug 30, 2022 3:08 pm The ultimate clearing of cache and cookies sure did the trick, although I admit that even that does not always work.

More then that. Just to recap the solutions found in this thread:

• riffr49 reported enabling popups worked
• jcluff47 with KyleHar9 confirming - making sure there wasn't anything in DNS
• milnerm1 with jmalmber@ualberta.ca confirming - Use incognito mode to browse to captive.apple.com

I have guestwirelesstermsofuse.churchofjesuschrist.org (the url for the splashscreen) bookmarked and browse directly to that if mine won't open automatically.

caillines wrote: Tue Aug 30, 2022 11:38 pm I have guestwirelesstermsofuse.churchofjesuschrist.org (the url for the splashscreen) bookmarked and browse directly to that if mine won't open automatically.

Love it. Thanks for sharing the link! For others reading along, here's the link in an easier to use format:

https://guestwirelesstermsofuse.churchofjesuschrist.org

Clicking the above link while not on the Liahona WiFi will simply forward you to the church's home page.

So I am having the same issue. DNS is all set to default, manually putting in the splash page URL gives me a DNS failure page, and Incognito doesn't fix the issue. I'm on Windows 11.

garrettharmer wrote: Sun Dec 18, 2022 1:14 pm So I am having the same issue. DNS is all set to default, manually putting in the splash page URL gives me a DNS failure page, and Incognito doesn't fix the issue. I'm on Windows 11.

After you connect to the Liahona network and get the "no internet" message...
Open a command prompt (windows+R, then cmd.exe) and type "ipconfig /all" (no quotes).
In the section that has something like wifi or wireless in its name, look in the IPv4 Address line. Does it have a 192.X.X.X or a 169.254.X.X email address, or something else?

caillines wrote: Sun Dec 18, 2022 5:53 pm In the section that has something like wifi or wireless in its name, look in the IPv4 Address line. Does it have a 192.X.X.X or a 169.254.X.X email address, or something else?

And what is the DNS (s) listed?

A buddy fixed it for me! After all the settings and such, what fixed it for me was going to a site I've never been to before like ibm.com to force the splash page.

garrettharmer wrote: Wed Dec 28, 2022 6:07 pm A buddy fixed it for me! After all the settings and such, what fixed it for me was going to a site I've never been to before like ibm.com to force the splash page.

Another option that might work would be to clear your browser's cache. Then, all sites would be in the same state as if you had never visited them before.

iPhone 13 absolutely won’t connect to Liahona!

Not I n my CA ward, my stake, and today in Herriman UT.

Tried everything!

Help!

Orion Wood
orionw@pacbell.net

Shows “connected” but only spins without connecting.

Orion Wood

orionw wrote: Sun Jan 22, 2023 11:20 am iPhone 13 absolutely won’t connect to Liahona!

I'd suggest informing your Stake Technology Specialist. As a user-to-user support forum, we're not in a position to do anything about it.

If it was widly spread, we'd have a flood of messages reporting the same thing.

orionw wrote: Sun Jan 22, 2023 11:20 am iPhone 13 absolutely won’t connect to Liahona!

Are you ever seeing the Terms of Use splash page?

If not, you can go to it manually, using the URL mentioned in post 24 of this thread.

Type 192.168.1.1

That worked for me! (I'm on a Chromebook - today was the first time I had issues. Found this forum and the only thing that worked was 192.168.1.1)

When I try to connect it woks without issue sometimes you just need to disconnect and reconnect a lot so you'll get that web page

What I've found is that you need to try going to a webpage you rarely visit. It has to be one you haven't visited in a day or more. (Or one that is open in a tab somewhere.) It has to be one that isn't filtered.

That will trigger a DNS lookup since it's not in the device's cache. That will trigger the splash screen.

Here's a new trick: Go to http://neverssl.com

You may need to close any existing tabs first.

Here's why it works: By default, web browsers will connect via https. The browser views the splash screen as a man-in-the-middle attack (which, technically it is) and won't display it.

Since neverssl always stays at just "http", the splash page is allowed to appear.

Other issues still apply: you must use the church supplied DNS.

Another site is http://httpforever.com

i would like to connect to the liahona internet it does not connect

shephardbwanali wrote: Sun Jul 06, 2025 4:13 am i would like to connect to the liahona internet it does not connect

Are any of the earlier posts in this thread relevant or helpful?

What device are you using? What OS? What version(s)?

What exactly happens when you try to connect?

I hope it is alright to post in this thread for help.
I have 2 cellphones I use to "Zoom" sacrament meeting. These phones are only used for this purpose. They do not have SIM cards, they only use the churches WiFi. They have worked for 2 years without issues. They worked last week, December 21, 2025. Today when I tried to connect to Liahona I get this error:

Timed out while joining "Liahona". Please try again later.

I rebooted, attempted to connect, got the same error. I forgot the network and powered off/on, attempted to connect, got the same error.
I am able to connect on my personal cellphone (Andriod Oneplus 8T), my daughter's cellphone (Pixel 7 Pro), and a random member's cell phone. No one else has this issue. Is there a chance my two cell phones got profiled and blocked on Liahona? That is the only thing I can think happened.

Both blocked phones are:
OnePlus 7T
Android Version 12
Cellphone 1 MAC: 48:01:c5:b4:26:57
Cellphone 2 MAC: c0:ee:fb:2b:3c:91

Is there a way to submit a support ticket? Or is this the best way to resolve this?

By "use to zoom sacrament meeting" do you mean you use the phones to broadcast the meeting via Zoom?
If so, try using the Lehi network.

Lehi isn't always enabled, and even if it is, you'd have to find out the current password as it change every few weeks months.

Since it used to work, I'd suggest power cycling the buildings network some time when it's empty.

russellhltn wrote: Sat Feb 21, 2026 11:48 pm Lehi isn't always enabled, and even if it is, you'd have to find out the current password as it change every few weeks.

In fact it automatically expires after 90 days.

dmburl wrote: Sun Dec 28, 2025 9:30 am I hope it is alright to post in this thread for help.
I have 2 cellphones I use to "Zoom" sacrament meeting. These phones are only used for this purpose. They do not have SIM cards, they only use the churches WiFi. They have worked for 2 years without issues. They worked last week, December 21, 2025. Today when I tried to connect to Liahona I get this error:

Timed out while joining "Liahona". Please try again later.

I rebooted, attempted to connect, got the same error. I forgot the network and powered off/on, attempted to connect, got the same error.
I am able to connect on my personal cellphone (Andriod Oneplus 8T), my daughter's cellphone (Pixel 7 Pro), and a random member's cell phone. No one else has this issue. Is there a chance my two cell phones got profiled and blocked on Liahona? That is the only thing I can think happened.

Both blocked phones are:
OnePlus 7T
Android Version 12
Cellphone 1 MAC: 48:01:c5:b4:26:57
Cellphone 2 MAC: c0:ee:fb:2b:3c:91

Is there a way to submit a support ticket? Or is this the best way to resolve this?

To follow up on this topic. In my instance this is how it was resolved:
I contacted the stake clerk, he and I did troubleshooting of all the basics. We ended up calling the church support line, they couldn't detect any reason why it wasn't working. My cellphone would not connect to the Wi-Fi nor show any logs it was trying.

The stake clerk had a local contact that worked with the church on the Cisco Meraki support contract. I was able to leave my phone with him for the weekend. (This was an old phone I only used for zoom at church.) They found the church rolled out a WPA3 policy to some churches and in that set of policies there was a setting requiring an obscure configuration that was once part of the WPA3 protocol but was either not used by most manufacturers or was abandoned. I wish I could remember what it was, but I wasn't familiar with it and couldn't spell it if I did remember it. The Meraki team removed that one setting from the policy and my phones were able to connect just fine.

In troubleshooting we found could connect to some buildings Wi-Fi and some I could not, even within the same stake. What I found is the church's building networks are grouped randomly and policy and settings are applied in a rolled out fashion. This is why it would work in our stake center, but not in the building I attend, but would also not work at a random church I tested one day. There is not rhyme or reason other than networking why buildings are grouped the way they are. Although I surmise it makes sense in a network spreadsheet somewhere.

Either way it is resolved UT honestly if we didn't have a local Meraki contact nothing would be fixed today.