Concerning issues of domain location and SSL

I previously had major issues with CloudFlare. Resolved the issue by deleting my domain and entering domain again. I was told to use subdomain…my site is not a subdomain.

Problem one:
Before doing this, my domain was under htdocs. After doing this my domain is now under mysite.com - htdocs

Problem two:
I have gone another route for the free SSL certificate which I desperately need for my online store. SSLforFree.com instead of CloudFlare. Because of the above issue, I keep getting errors when I try to verify my website via FTP, directories with their files, and DNS. Two of these have “Unauthorized” and can’t verify my website. The DNS verification I can’t figure how to use because it asks for a text file. FTP verification was simple to do but again…failed to authorize.

Problem three:
They require using Port 80 for “Manually Verify Domain (HTTP Server)” By creating 2 directories and placing 2 of their files in one of the directories…very easy. I have no idea how to change over to use Port 80 for this verification.

“If you do not have your FTP information then follow the following steps to verify domain ownership manually. The server will need to be on port 80 if HTTP (or port 80 open and forwarding to 443 if HTTPS). If your web server is not listening on port 80 then you will need to temporarily listen on port 80 or forward port 80 to the port for the web server.”

Below is the error:

Domain “mysite.com” challenge3 failed. Response from “https://acme-v01.api.letsencrypt.org/acme/challenge/{special code here]/[special code here]” was: { “type”: “http-01”, “status”: “invalid”, “error”: { “type”: “urn:acme:error:unauthorized”, “detail”: “Invalid response from http://mysite.com/.well-known/acme-challenge/[special code here]: “\u003chtml\u003e\u003cbody\u003e\u003cscript type=“text/javascript” src=”/aes.js” \u003e\u003c/script\u003e\u003cscript\u003efunction toNumbers(d){var e=[];d.replace(/(…)/g,func"", “status”: 403 }, “uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/[special code here]/[special code here]”, “token”: “[special code here]”, “keyAuthorization”: “[special code here]”, “validationRecord”: [ { “url”: “http://mysite.com/.well-known/acme-challenge/[special code here]”, “hostname”: “mysite.com”, “port”: “80”, “addressesResolved”: [ “special url number” ], “addressUsed”: “special url number”, “addressesTried”: [] } ] }

This method was for me to setup 2 directories and place 2 files in one of the directories, very simple. They have links to test, so I tested it and it worked. When I click to get the SSL certificate the above error displays and I do not receive my SLL certificate.

Sorry for the long message, I made it shorter… :slight_smile:
Any and all helpful information would be appreciated.

Overall:

  1. How to use Port 80
  2. How to place my domain back under htdocs instead of mysite.com/htdocs currently.
  3. Adding TXT record to DNS server
  4. I believe no verification can work unless #2 is fixed first.

Kindly,
Essence

Ps. My site is working fine on my end even though it’s located at #2.

@Essence said:
Problem one:
Before doing this, my domain was under htdocs. After doing this my domain is now under mysite.com - htdocs

The only way to get your domain back under an htdocs directory is by creating a new account for it. Domains assigned when an account is created are slightly different from domains added to accounts later on.

We don’t like this either, but it’s a technical limitation outside of our control.

Problem two:
I have gone another route for the free SSL certificate which I desperately need for my online store. SSLforFree.com instead of CloudFlare. Because of the above issue, I keep getting errors when I try to verify my website via FTP, directories with their files, and DNS. Two of these have “Unauthorized” and can’t verify my website. The DNS verification I can’t figure how to use because it asks for a text file. FTP verification was simple to do but again…failed to authorize.

Simply put: you can’t use sslforfree.com on InfinityFree. It’s a known issue..

Problem three:
They require using Port 80 for “Manually Verify Domain (HTTP Server)” By creating 2 directories and placing 2 of their files in one of the directories…very easy. I have no idea how to change over to use Port 80 for this verification.

Port 80 is the default port for http. If you can type your website address in your browser with http (not https) and don’t enter a custom port number, it means you’re using port 80. You are already using port 80.

awesome! thank you.

The other issues?

@Essence said:
awesome! thank you.

The other issues?

What other issues?

OMG! Are you kidding me? Another SSL company with issues. RRRRRR!
Does anyone know of free SSL certificates that work with InfinityFree? Exclude CloudFlare please.
This is horrible news. All my time working on the site and come to find out I can’t use the site without an SSL certificate.

Cloudflare is not an SSL company. And the only SSL company in the world you can’t use on InfinityFree is Let’s Encrypt. Literally every other SSL company out there can be used.

You saved my life Admin, I love you and thank you