Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • von 61 posts 123 karma points
    Jun 21, 2018 @ 07:49
    von
    0

    Error could not load url

    Hello,

    We encountered the error could not load url when saving a content without publishing it. Previewing the content also throws the same error. I read in another posted question that we need SEOChecker.DisablePreviewValidation to be set to true. We did that but we are still encountering the error. We have encountered this in both V1.x and V2. Is there another configuration that we should set?

    Here's the entire error message:

    SEOChecker: SEOChecker: Error could not load url https://.../4435.aspx 
    System.Net.WebException: The remote server returned an error: (404) Not Found.
       at System.Net.HttpWebRequest.GetResponse()
       at SEOChecker.Core.Helpers.Request.GetStream(String url, HttpCookieCollection cookies, String userAgent)
    
  • Richard Soeteman 4046 posts 12899 karma points MVP 2x
    Jun 21, 2018 @ 09:49
    Richard Soeteman
    0

    Hi in v2 there is no preview option anymore so you can't disable it. Does the normal page also throws a 404?

  • von 61 posts 123 karma points
    Jun 27, 2018 @ 08:36
    von
    0

    Hi Richard, what do you mean by "normal page"? If you are referring to a published page then no we do not get the error from a published page.

  • Arjan Woldring 124 posts 231 karma points
    Jun 21, 2018 @ 10:24
    Arjan Woldring
    0

    Hi,

    I do have the same error a lot. Just on the root-node it seems. Using v2 and U7.10.4

    Cheers, Arjan

    edit: Normal page is working fine. Preview is giving an error. It seems that is has nothing to do with Seochecker as it is just loading the preview umbraco functionality. Looking into the error now.

  • Richard Soeteman 4046 posts 12899 karma points MVP 2x
    Jun 21, 2018 @ 10:39
    Richard Soeteman
    0

    Hi Arjan,

    V2 is not using the preview version anymore, so that error is strange..

  • Arjan Woldring 124 posts 231 karma points
    Jun 21, 2018 @ 10:55
    Arjan Woldring
    0

    Hi Richard,

    I found the issue. It has nothing to do with Seochecker. For some reason there is a difference between frontend rendering and preview rendering. The frontend was working fine. But previewing gave an error like this:

    System.InvalidOperationException: ContentTypeService failed to find a content type with alias "wijzigWachtwoord".. This usually indicates that the content cache is corrupt; the content cache has been rebuilt in an attempt to self-fix the issue.
    

    Republishing the node(s) with this doctype fixed the error.

    All good :)

  • von 61 posts 123 karma points
    Jun 27, 2018 @ 08:39
    von
    0

    Republishing won't work in our case as the content needs to be previewed first and will probably sit in the back-end for a while and will be edited a lot before being published.

  • Richard Soeteman 4046 posts 12899 karma points MVP 2x
    Jun 27, 2018 @ 08:42
    Richard Soeteman
    0

    Hi Von,

    Building the preview version of the page took way to long in most cases and sometimes caused huge performance issues. So I decided to not use this anymore, think in V8 it will return. But what you can do is set umbraconavihide to true so it will not end up in navigation

    Best, Richard

  • Richard Soeteman 4046 posts 12899 karma points MVP 2x
    Jun 27, 2018 @ 08:44
    Richard Soeteman
    1

    Hi Von,

    I've also changed the way the url renders. Since it's only using the published page I am using Niceurl now.

    You can find the hotfix on my dropbox https://www.dropbox.com/s/e4v823o9yuhfpcf/seo-checker20_1.zip?dl=0

  • Thomas 319 posts 606 karma points c-trib
    Dec 01, 2019 @ 10:25
    Thomas
    0

    Hey,

    I'm getting the same error right now..

    On a Umbraco Cloud 7.15.3

    SEOChecker: SEOChecker: Error could not load url https://www.xxx.dk/page-not-found/ System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at SEO
    
  • Richard Soeteman 4046 posts 12899 karma points MVP 2x
    Dec 02, 2019 @ 07:40
    Richard Soeteman
    0

    Timout could mean 2 things:

    1. The page takes too long to load?
    2. The page can't be accessed at all..

    Best,

    Richard

Please Sign in or register to post replies

Write your reply to:

Draft