locked
Certificate error when browsing the local Vail server RRS feed

  • Question

  • Hi!

    When I access http://vail/ from my local client (vail is the name of the vail server) I get an error as below. WHen accessing from internet using https://xxx.homeserver.com it works fine.

     

    There is a problem with this website's security certificate.

     
     

    The security certificate presented by this website was issued for a different website's address.
    <noscript id="securityCert1"></noscript>
    Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.

     

    We recommend that you close this webpage and do not continue to this website.

     

    Recommended iconClick here to close this webpage.

     

    Not recommended iconContinue to this website (not recommended).

     

    More information More information<noscript></noscript>

     

  • If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting.
  • When going to a website with an address such as https://example.com, try adding the 'www' to the address, https://www.example.com.
  • If you choose to ignore this error and continue, do not enter private information into the website.

     

    For more information, see "Certificate Errors" in Internet Explorer Help.


  • Henrik
    Monday, June 21, 2010 8:33 PM

Answers

  • This is normal. The certificate that Vail receives for the homeserver.com vanity URL isn't valid for the unadorned server name.
    I'm not on the WHS team, I just post a lot. :)
    Monday, June 21, 2010 10:45 PM
    Moderator

All replies

  • This is normal. The certificate that Vail receives for the homeserver.com vanity URL isn't valid for the unadorned server name.
    I'm not on the WHS team, I just post a lot. :)
    Monday, June 21, 2010 10:45 PM
    Moderator
  • So I see... thanks for clarifying that.

    So even when acessing Vail from the intranet, I should use the https://xxx.homeserver.com

    Thanks


    Henrik
    Tuesday, June 22, 2010 8:22 AM