Error: Failed to construct ‘URL’: Invalid URL

  • Resolved Weston Ruter

    (@westonruter)


    3 years, 8 months ago

    I just tried accessing the Site Kit dashboard after updating to WordPress 5.8 and I was presented with the “Site Kit encountered an error” screen.

    Error:

    Failed to construct 'URL': Invalid URL

    in DetailsPermaLinks
    in Component
    in div
    in td
    in tr
    in tbody
    in table
    in div
    in ReportTable
    in div
    in div
    in TableOverflowContainer
    in div
    in div
    in Widget
    in WithWidgetSlug(Widget)
    in DashboardPopularPagesWidget
    in WhenAnalyticsActive(DashboardPopularPagesWidget)
    in WidgetRenderer
    in div
    in Cell
    in WidgetCellWrapper
    in div
    in Row
    in div
    in div
    in Grid
    in WidgetAreaRenderer
    in div
    in WidgetContextRenderer
    in DashboardApp
    in GoogleSitekitDashboard
    in RestoreSnapshots
    in ErrorHandler
    in Root

    This error also shows up in the Site Kit Summary dashboard widget.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter Weston Ruter

    (@westonruter)

    I also enabled Troubleshooting mode and enabled only Site Kit and I still got the error.

    I’m using the Twenty Twenty theme.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi Weston,

    As we only encountered this particular notice in the support forums on one occasion previously any additional information would be useful. You can share your Site Health information here or using this form if you prefer to share privately. I’m particularly curious to know if the same occurs with only the Search Console module active.

    Thread Starter Weston Ruter

    (@westonruter)

    Site Health info submitted via form.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing. As nothing obvious stands out can you share does the same occur when you deactivate the PageSpeed Insights module? While there’s no such error in the Site Kit codebase I can see some older GitHub issues on the Lighthouse repository.

    Before deactivating the PageSpeed Insights module please share any console errors. If you can consistently reproduce this on each page reload please also share any invalid XHR response.

    Thread Starter Weston Ruter

    (@westonruter)

    How do I deactivate the PageSpeed Insights module?

    Nevertheless, in the stack trace there is this reference: DashboardPopularPagesWidget and WhenAnalyticsActive. So it seems to be a problem with the Analytics module.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update. I’ve created a GitHub issue to keep track of progress on this which you can find below:
    https://github.com/google/site-kit-wp/issues/3752

    You can disconnect the PageSpeed Insights or Analytics modules via “Site Kit > Settings > **module** > Edit > Disconnect **module** from Site Kit”.

    If the same occurs the Health Check & Troubleshooting plugin is great for ruling out any third party plugin conflicts, with similar Analytics stack trace references encountered by users of plugins that also use the Google Charts Library.

    Thread Starter Weston Ruter

    (@westonruter)

    Disconnecting Analytics did stop the error from happening.

    However, once I reconnected Analytics then the error returned.

    Also, I did try using Health Check & Troubleshooting to isolate Site Kit as the only active plugin, but the error persisted.

    I tried clearing the persistent object cache but the issue still occurs.

    I’ll copy this onto the issue.

    Plugin Author Felix Arntz

    (@flixos90)

    @westonruter Are there any odd-looking URL values in your Analytics top pages when checking your Analytics data? Maybe we are missing a scenario there and need more “forgiving” logic.

    Thread Starter Weston Ruter

    (@westonruter)

    Yes: https://github.com/google/site-kit-wp/issues/3752#issuecomment-887685802

    (I won’t add further replies to the forum topic to avoid duplication.)

    @westonruter @flixos90 Since we have an active conversation going on in the GitHub issue here, I’m going to mark this topic as resolved.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error: Failed to construct ‘URL’: Invalid URL’ is closed to new replies.