• Resolved anchoredmeditation

    (@shorelarkbythesea)


    OMGF encountered an error while fetching this site’s frontend HTML: 401 – Unauthorized

    I know this error message was responded to in another question, but those were for sites that are live and visible. I’m using the latest free version of OMGF on a staging site and getting this error message. My theme is Hello, I have no plug-ins that are on the conflicting plugins list, and my staging site is https and I’ve attached a screenshot of the OMGF panel. Any ideas why I’m getting this message? Is it because it’s a staging site? Thank you in advance. https://imgur.com/QNSAKqv

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Do you have basic authentication, or something? Because, if so, OMGF can’t deal with that (yet). It’s a feature that’s on my todo list, though.

    Thread Starter anchoredmeditation

    (@shorelarkbythesea)

    That was quick, thanks!! I’m not sure what you mean by ‘basic authentication’? You mean when logging into my WP dashboard?

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    This image is an example of what Basic Authentication looks like:

    Ring a bell? ??

    Thread Starter anchoredmeditation

    (@shorelarkbythesea)

    Uh, no, sorry…I don’t even know where I would go to get to that screen…I just log into WP…

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Ah, okay. The reason I asked is, because you said this:

    live and visible

    So, you are indeed locking the frontend visibility of the site, correct?

    The thing is that OMGF can’t “act” like an admin, because it runs on your server. So, if your site is locked to the outside world, OMGF won’t be able to parse the HTML for Google Fonts.

    One way to work around this, is by appending ?omgf_optimize=1 to the URL when logged in as an admin and viewing the frontend. Once you press enter, you’ll force to run OMGF on that page.

    Let me know if that worked for you!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘“OMGF encountered an error while…”’ is closed to new replies.