#Mac OS Mojave. A Problem Occurred. The web page couldn’t be loaded when connecting to Wifi

This is a non virtualization based topic, but since I know many in the VMware community are working with a MacBook I just wanted to share this quick workaround about a malfunction I have when connecting to a public wifi since upgrading to Mac OS Mojave.

Once you connect to the public wifi instead of a captive window the following error shows up.

A Problem Occurred. The web page couldn’t be loaded

There seems to be an issue with displaying the captive screen within the integrated browser. What is the workaround? Open up another browser, like safari and bookmark/open the following page

http://captive.apple.com

It might be necessary to refresh this page multiple times until the correct captive screen will be shown. But after a few retries you should be able to authenticate.

Update [October 2019]

After the update to Mac OS Catalina I was faced with another issue. While connecting to a public wifi no captive screen has been shown. This time even above mentioned workaround was not properly working.

After doing some research I found a workaround, to make it functional again.

Open the terminal remove the content of the following folders

> rm -f /Library/LaunchAgents/*

> rm -f /Library/LaunchDaemons/*

Make sure to copy the folders up front to make sure that in a case of problems afterwards, you are able to restore them.

13 thoughts on “#Mac OS Mojave. A Problem Occurred. The web page couldn’t be loaded when connecting to Wifi

  • 9. March 2019 at 16:30
    Permalink

    Wow, this really works! Thanks you for your help!

    Reply
  • 18. March 2019 at 5:30
    Permalink

    Thank you this worked great!!

    Reply
  • 10. April 2019 at 18:08
    Permalink

    Thank you!!!!!!!!

    Reply
  • 16. April 2019 at 6:32
    Permalink

    Is there no permanent solution to this?

    Reply
    • 27. May 2019 at 12:24
      Permalink

      After the last Mac OS update the issue was resolved on my macbook.

      Reply
  • 30. May 2019 at 19:21
    Permalink

    This worked!!! Awesome ! This was vexing me to no end. Thank you!!

    Reply
  • 2. July 2019 at 22:43
    Permalink

    This is great nice simply fix for this annoying issue. Thanks

    Reply
  • 24. October 2019 at 19:20
    Permalink

    Thank you thank you. I’ve had this problem since upgrading to Catalina (10.15) as well. Weeks of pain of not being able to login to any wifi hotspot that was unsecured, but used a captive portal page. Always connected, always got an IP address, but no portal page.

    Tried all the stuff that’s out there, including checking / resetting DNS. Network profiles, etc. “captive.apple.com” as a thing… none of this worked (like the frustration of this older thread, which means for some this was before Catalina: https://discussions.apple.com/thread/7588901?answerId=7588901021#7588901021)

    Anyway, clearing LaunchAgents and LaunhDaemons (plus a restart) was the first thing that ‘s worked. Much relieved. Thanks. @ridgewaychris

    Reply
    • 6. November 2019 at 22:50
      Permalink

      Update to my comment earlier. This fix removing LaunchAgents folders worked. But now the status quo is that public capture screens still refuse to display unless just after a clean reboot. Weird. So when I arrive at a public hotspot, it connects to the network but refuses to display the capture. Upon reboot it works.

      If at any point I disconnect from the public wifi and it loses the session, I cannot reconnect unless I reboot again to get the capture screen to appear.

      This workaround is working but is still broken. Any thoughts?

      Reply
  • 3. November 2019 at 0:44
    Permalink

    Hi. This started with Catalina for me. Never had this error before. I have tried the solution posted on this website but it is still not working. Was there a special terminal command that I am supposed to use? All I did was use finder and deleted all the files inside those two folders, typing my admin pw to confirm its deletion.

    Did I miss something?

    Thanks!

    Reply
  • 20. December 2019 at 21:45
    Permalink

    This fix didn’t work for me. But, something else did. I had set the DNS server to 8.8.8.8 (google’s) and that was the problem with 1 out of 10 libraries I’ve been to. Clearing DNS cache also didn’t work.

    The fix: removing the 8.8.8.8 entry in the DNS settings. This is in Network Preferences and Advanced.

    Reply

Leave a Reply to ASLANIAN, SEBOUH Cancel reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.