locked
xxx.homerserver.com domain name not working any more RRS feed

  • Question

  • My xxx.homeserver.com domain name stopped working yesterday. I did an nslookup on it and it said the domain xxx.homerserver.com is unknown although the domain homeserver.com is still found and is mapped to the IP address 52.164.206.56. Did Microsoft stop supporting domain name service for WHS or is the outage temporary?
    Friday, July 24, 2020 6:00 PM

All replies

  • Same for me, my xxx.homeserver.com domain stopped working. Please give an update what happened. Service is needed and CRITICAL !
    Friday, July 24, 2020 9:05 PM
  • Same problem here - grrr
    Friday, July 24, 2020 11:13 PM
  • So it appears that the domain (xxx.homeserver.com) is gone and might not be available because it's an old service? My public domain is also not reachable: TXM-MC.homeserver.com ... But it says in the server settings that it is connected and active but when I click configure it displays an error when the domain name should be configured: "An unknown error occured. Please try again later". It's so sad if it's gone, I should ask the domain issuer what's going on (GoDaddy is the domain service)
    Saturday, July 25, 2020 8:46 AM
  • Same problem here!

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Saturday, July 25, 2020 1:05 PM
  • Hi from the Netherlands; this morning same problem but it now seems to be working again. I can see this because I use my homeserver.com domain name to resolve to my IP camera's so I can see them on the internet.

    However, when trying to acces my domain I get this error in Chrome: NET::ERR_SSL_OBSOLETE_VERSION and a unsecure connection. Something with the SSL certificate I guess...

    Saturday, July 25, 2020 2:37 PM
  • Hi, I am having the same problem and had no success yet to resolve the issue.

    When I try to reconfigure the Domain name via the Windows homeserver console, I get an error after having entered my live id and password; Unknown error (0x80048051) 80048051

    When I look in the logs (using RDP to the homeserver) located at: 

    C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\ddns-072520.log

    the following is listed:

    Main started
    [25-7-2020 22:19:47 1b64] MAIN: COM initialized successfully
    [25-7-2020 22:19:47 1e4c] INIT: Service started.
    [25-7-2020 22:19:47 1950] MAIN: Main service thread started initialization
    [25-7-2020 22:19:47 1950] MAIN: Registering COM object
    [25-7-2020 22:19:47 1950] MAIN: Declaring service as running
    [25-7-2020 22:20:02 1950] Checking validity certificates with the name XXXXXXXXX.homeserver.com in MY
    [25-7-2020 22:20:02 1950] CertOpenStore ok.
    [25-7-2020 22:20:02 1950] Cert XXXXXXXXX.homeserver.com validity for  is 14992564
    [25-7-2020 22:20:02 1950] Checking if certificate with the name XXXXXXXXX.homeserver.com in MY is 1024 bit
    [25-7-2020 22:20:02 1950] CertOpenStore ok.
    [25-7-2020 22:20:02 1950] CertGetPublicKeyLength returned with 2048 
    [25-7-2020 22:20:10 1950] ERROR: Could not open PPEnv key hr = 0x80004005
    [25-7-2020 22:20:16 1950] ERROR: Failed to LogonIdentityEx hr = 0x80048051


    I could not find any info on the ERROR: 'Could not open PPEnv key hr = 0x80004005

    Anyone has an idea and/or suggestions what is going on and how to resolve this?


    Saturday, July 25, 2020 8:51 PM
  • ... and as if by magic, it’s working again!

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    • Proposed as answer by Phil Harrison Thursday, July 30, 2020 10:26 AM
    Sunday, July 26, 2020 8:45 AM