• Resolved ohgoodiee

    (@ohgoodiee)


    After step one of signing into google and allowing access to everything, the setup process came back to my dashboard and displayed the following error.

    Oops! There was a problem during set up. Please try again.

    Unknown Error (code: http_request_failed).

Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter ohgoodiee

    (@ohgoodiee)

    The way my setup works is…

    If I punch a hole in the firewall for you, it doesn’t matter what port you want/need, it’s open.

    Basically, Site kit has full access to whatever it wants (within reason of course).

    For visitors, everything is funneled through Cloudflare. Again though, Site kit has access through there too, even though it’s not needed as Site kit has direct access.

    Last, but not least, Site kit has full access to reverse DNS, there shouldn’t be a problem there either. dig l34.ns.rocklobster.network = 162.208.8.222 – dig -x 162.208.8.222 = l34.ns.rocklobster.network

    As of about an hour ago, it’s still working, but it takes a long time (hanging the system) for it to populate information on the dashboard or the admin dashboard.

    • This reply was modified 4 years, 6 months ago by ohgoodiee.
    • This reply was modified 4 years, 6 months ago by ohgoodiee.
    Plugin Support James Osborne

    (@jamesosborne)

    @ohgoodiee Very useful insights, many thanks for sharing. Glad to hear it’s now working with your firewall modifications. If you encounter anymore issues feel free to get in touch.

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Not able to connect to whatever it’s looking for’ is closed to new replies.