Verification Files Uploaded to Host, but not Found

My domain is:UXStars.com

I used ZeroSSL.com to create text verification files successfully and uploaded them to my site.
Those files however cannot be detected, so I can’t get my Cert.

I even put a jpg file in the same folder just to be sure I really can access the acme-challenge directory properly.

Do I need to change some setting so that my host returns the files properly, just as it does the jpg test image?

My hosting is with GoDaddy, using Plesk. I contacted GoDaddy, but they could not help me. I’ m sure they’d like to sell me one of their expensive SSL certs.

Why is it that I can see this jpg file:

I can’t see these. It says “Not Found The requested document was not found on this server.”

http://www.uxstars.com/.well-known/acme-challenge/0X3UwkYP2HltHFc_mWWFJ7BD-V1lwgAqBqBSyMsNKfI

http://www.uxstars.com/.well-known/acme-challenge/8JYYRAsiqt6JEy7cezzCBPjrLnsIZcAEZOoyQf-H27Y

thanks, Randy

Hi @randyowl

checking your domain there are different headers - https://check-your-website.server-daten.de/?q=uxstars.com

Your http:

Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
X-Powered-By-Plesk: PleskWin

The not working https (wrong certificate):

Server: Microsoft-HTTPAPI/2.0

/.well-known/acme-challenge

Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
X-Powered-By-Plesk: PleskWin

Your picture looks like a configured rule, such things are easy.

So it's

  • a Plesk function GoDaddy is using (or)
  • an own function of GoDaddy

Result: Your hoster blocks using http validation. Accept it, change your hoster or use dns validation + manual.

Oh, wait: If you have write access to that subdirectory /.well-known/acme-challenge:

There must be a configuration file that allows extensionless files.

Check, if there is a web.config.

If not, create one:

<configuration>
	<system.webServer>
		<staticContent>
			<mimeMap fileExtension="." mimeType="text/plain" />
		</staticContent>
	</system.webServer>
</configuration>

If yes, merge the content.

That’s always required.

2 Likes

Thanks! This advice of adding fileextension handling to my web.config is exactly what I needed! Working great now.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.