Search results

don't actually use "name". Replace with something. "????" .x10.mx. name.x10.mx is already used. Do you have any subdomains created?

Add a free domain and make it default, then delete. free domain looks like this name.x10.mx

The Directadmin control panel has a free Certificate in the SSL manager. Many need to be enabled for your account, you have to look and request in new post if not active.

Remove domain name here: https://x10hosting.com/login Just stop logging here: https://x10hosting.com/login and account will be deleted in a couple of months.

You have not installed a SSL certificate, so https (secure) will not work. http is working as expected. http looks for index.html and loads in web browser. As long as it has markup source code. test.html will just show the file in index directory. Unless you add it to the url...

What? You have to let me see this.

Really there is no need to start fresh. You should be able to add a x10 free domain. "something.x10.mx", I had to do the exact same thing. "tbint.x10.mx" I made it default, and I could still add a second TLD. 1 x10 free and 2 TLD. You could delete the x10 free, and save the 2 other domains for...

So everything is going well for you?

archersreference.co.uk SOA 21600 ns1.infinityfree.com

I'm using chrome, everything works. Options -Indexes sends users 403. If you know the file name in the directory it will still process the file. I'm not sure what you're trying to achieve. I thought you wanted to see files in a directory. Then use Options +Indexes.

In the public_html/htaccess file just this "DirectoryIndex disabled". Then the "Options +Indexes" or "Options -Indexes" work in the sub directories. Must have been an Apache server update or something. Your Post brought it to my attention. Had to figure out what was going on.

Try this, htaccess in public_html: DirectoryIndex disabled htaccess in directory allowing indexing Options +Indexes https://tbint.us/public_directory/ Directory denied indexing: Options -Indexes https://tbint.us/assets/

I think it is the proxy status: Proxied and the TTL: auto. It may be the NS records. I would think they would be ns1.x10hosting and ns2. Will have to check.

You can add the correct domain here: https://x10hosting.com/login Then make it default and remove the incorrect domain.

Create a .htaccess file in the directory with "Options +Indexes".

I know you don't want to hear that it is a cloudflare error 522. I am getting the same error from my house. That makes me think you have incorrect DNS settings. https://intodns.com/christurnbullwx.com Check the TTL. [TTL=3600] Second look: 2 different A record IP addresses being reported...

Yea your only allowed three "domains/subdomains" on x10 free hosting. Subdomains count as domains.

Add domains here: https://x10hosting.com/login

Set your certificate to use a wildcard.

How is the certificate set up? (*.domain.co.uk) I never had positive results with IMAP ports 143, 993. The mail clients worked with a certificate wildcard (*.domain.co.uk) and (domain.co.uk) with smtp port 587 (some clients smtp port 465) and pop port 995 with the mail server/host...