Search results

Be lucky it was even there to begin with in cPanel as it was a mistake that it was there. Through I could’ve swore at minimal, they’ve given us a self-signed cert for the domain. This way the traffic between you, Cloudflare, and the server were encrypted.

Just found out some information from Cloudflare. For people who have not set up the integration before migration from cPanel to DirectAdmin, it will no longer be possible to integrate with Cloudflare and add the domain successfully anymore. Putting the name servers in through DA will not serve...

I actually get a connection not private error from the certificate for x13.x10hosting.com. You may need to get rid of the .htaccess file and create a new one.

Even if we can at least get a self-signed cert for the domains themselves. At least it’ll allow Cloudflare to encrypt end to end. Changing to flexible will at least allow your site to return information but it won’t work until Cloudflare can issue a SSL. not sure about the email issue though.

I agree with you. Especially since Let’s Encrypt is free, at the same point the cPanel certs were free as well at the time that it should just be allowed. However, at the end of the day, they still need to make profit from premium users and SSL offerings for them. I would even think if they did...

They are not removing it anytime soon. The whole reason they are moving to DirectAdmin is so that we can keep our free hosting. cPanel changed their licensing costs and policies where they are by Account along with upping their prices. Even though DirectAdmin uses a similar model, many more...

The subdomains did not migrate for me. The records and files were still there for it, but it did not reflect in DirecrAdmin nor did it actually display content. It just displayed the apache message. I re-added one to see if it works. However, after doing so messed up the pull with Cloudflare...

I allow for showing the website statistics publicly currently at the moment. What I was wanting to do was optimize the html files generated to allow them to support dark mode. I was able to change two of the files over to dark mode. The issue is, whenever Webalizer goes to update those files the...

SSL is not included for free accounts officially confirmed by an email I just got back from support 2 days ago. "No, using SSL certificates is not supported on our free hosting service. To use this you would need to upgrade to our premium hosting service. Please visit x10premium.com to view all...

It seems it happens with all x10 domains when using their stuff. Then whenever using Google, O365 its all fine. I'm about to switch to Zoho mail since that's the only free option.

^ +1

Did you try xo15 or x15? It is x15, not xo15.

1. Contact Cloudflare, it seems all of x10Hosting's .x10.mx domains come back as malicious according to one test from one of Cloudflare Universal SSL issuers. https://www.virustotal.com/gui/url/4459796048e74f1023ca363339bdf8cfcbff107b703e5cdf13bd0ff73d4bc94e/detection You can appeal here...

I would email that over to either support or directly to Corey. That would be a security flaw. Especially the password, ideally, both should be hidden. Do you mean the account username as in to login to the servers or to log into SSO? Even though it probably is not much as a security issue...

It's literally the same as yours except for minor things like where emails would go. What do you mean by renaming the domain? If I try to do it, it'll say I don't own x10host.com to be do that. I know originally, I believe the box through DirectAdmin while SSL was enabled on the accounts, was...

Same result.

Yes. No dice.

I already did. It proves what I already knew that it is happening on x10 side.

http://mycoolweb.x10host.com. It will keep redirecting to https:// regardless. My http://www.mycoolweb.x10host.com is using Cloudflare Edge which only redirects to https:// at the Cloudflare edge only and works perfectly fine, other than Apache, as long as you’re in the US. I’ve even went as...

Your redirect is coming from Cloudflare as you have their Universal SSL. Your case seems to be fine other than the Apache message.