Domain validation error. Not sure what is causing this. Can you advise?
2024-01-10 10:10:56.949 -08:00 [INF] Checking URL is accessible: http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ [proxyAPI: True, timeout: 5000ms]
2024-01-10 10:12:37.006 -08:00 [WRN] Problem checking URL is accessible : http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ The remote server returned an error: (404) Not Found.
2024-01-10 10:12:37.006 -08:00 [INF] Checking URL is accessible: http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ [proxyAPI: False, timeout: 5000ms]
2024-01-10 10:12:37.008 -08:00 [ERR] Failed to confirm URL is accessible : http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ
System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certify.Management.NetworkUtils.<CheckURL>d__4.MoveNext() in D:\a\certify-service\certify-service\src\certify-build\certify\src\Certify.Shared\Management\NetworkUtils.cs:line 153
2024-01-10 10:12:37.008 -08:00 [INF] Requesting Validation: fs.mocse.org
2024-01-10 10:12:37.012 -08:00 [INF] Attempting Challenge Response Validation for Domain: fs.mocse.org
2024-01-10 10:12:37.013 -08:00 [INF] Registering and Validating fs.mocse.org
2024-01-10 10:12:37.036 -08:00 [INF] Checking automated challenge response for Domain: fs.mocse.org
2024-01-10 10:12:58.964 -08:00 [INF] Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
I ran this command: none (ran gui to create certificate) - did not create
It produced this output:
2024-01-10 10:10:56.949 -08:00 [INF] Checking URL is accessible: http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ [proxyAPI: True, timeout: 5000ms]
2024-01-10 10:12:37.006 -08:00 [WRN] Problem checking URL is accessible : http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ The remote server returned an error: (404) Not Found.
2024-01-10 10:12:37.006 -08:00 [INF] Checking URL is accessible: http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ [proxyAPI: False, timeout: 5000ms]
2024-01-10 10:12:37.008 -08:00 [ERR] Failed to confirm URL is accessible : http://fs.mocse.org/.well-known/acme-challenge/1LgU1qh78bCFZyU-8-_NbMRg_8hJjOIQUKGrSwM6dZQ
System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certify.Management.NetworkUtils.<CheckURL>d__4.MoveNext() in D:\a\certify-service\certify-service\src\certify-build\certify\src\Certify.Shared\Management\NetworkUtils.cs:line 153
2024-01-10 10:12:37.008 -08:00 [INF] Requesting Validation: fs.mocse.org
2024-01-10 10:12:37.012 -08:00 [INF] Attempting Challenge Response Validation for Domain: fs.mocse.org
2024-01-10 10:12:37.013 -08:00 [INF] Registering and Validating fs.mocse.org
2024-01-10 10:12:37.036 -08:00 [INF] Checking automated challenge response for Domain: fs.mocse.org
2024-01-10 10:12:58.964 -08:00 [INF] Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
2024-01-10 10:13:00.929 -08:00 [INF] Validation of the required challenges did not complete successfully. Domain validation failed: fs.mocse.org
My web server is (include version): IIS Windows on Server 2016
The operating system my web server runs on is (include version): Windows Server 2016 standard
My hosting provider, if applicable, is:CloudFlare for the domain
I can login to a root shell on my machine (yes or no, or I don't know): i don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
IIS
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): not using Certbot
I'm unable to connect to your site via either HTTP and HTTPS.
Are you able to reach your site from the Internet [not from a local network]?
Is there a firewall/security device inline? If so, are they working correctly?
Still no luck. If Certify is starting its own listener for the challenge it will only work when it is running. This is one reason it is best to post on their forum. They know their product best and are experts at Let's Encrypt too.
Hi, I'm the developer of Certify The Web. Please update to the latest version, as old versions are not supported.
It looks like you currently have port 80 open but the response is 404 (not found) which is actually a good start because that means your firewall is open it's just not getting the response it expected.
Update the app to the latest version and if you can perform a server reboot then try that as well - processes can sometime get stuck and your webserver doesn't seem to be responding particularly well currently.
You have truncated your log file so I can't see whether the HTTP Challenge Server is managing to start OK, this is the process that answers http challenges so that IIS doesn't have to (and therefore doesn't need special configuration). Some anti-virus apps have been known to interfere with this process and that's gotten worse recently - they may be using a general heuristic that a process shouldn't be allowed to start an http listener and you may need to add an exception.
If the app is being forced to fallback to IIS for http challenges it should still work though, try deleting the web.config file from /.well-known/acme-challenge and the app will recreate the file when you next click Test, this cycles through various configurations to find the one that works for your version/configuration of IIS.
I updated the application to the latest version. I restarted the server and applied the webserver AV policy to the server. I get the following logs below. It is still not communicating correctly.
