- Messages
- 2,199
- Reaction score
- 195
- Points
- 63
Website Error
- Thread starter bigbro16
- Start date
- Status
@spacresx
It was because they accidentally enabled AutoSSL for some servers, xo2 was also one of them, through cPanel/WHM before and shut it off. It would let you keep it until it expires, where it would depend if they left it on or not. Going to DirectAdmin once its set up, will remove that SSL on the spot, unless they wait a little bit to disable it after the server is set up which is how they did it for all servers.
Let's explain the problem, because I think there are people who do not understand what is happening, when we were with Cpanel we had the SSL certification, they migrated to DirecAdmin on another new server and everything worked OK, therefore we had a server with cpanel + ssl and the new direct server Admin, the dns updated to point to the new ip of the directAdmin but when being configured the dns in the server1 pointed to the server2
it obtained its certificate, but delete the server1 that had cpanel + ssl, then the server2 remains configured with DirecAdmin without SSL and here the problems. Solution on the 1 page of this thread I put the solution.
it obtained its certificate, but delete the server1 that had cpanel + ssl, then the server2 remains configured with DirecAdmin without SSL and here the problems. Solution on the 1 page of this thread I put the solution.
The solution does not work for me at all. Free accounts are not allowed SSL and for those who have received it, it was a configuration mistake. Yes I do think however, when they stepped in and disabled SSL on all the free users, caused the issue, the thing is, were not supposed to have it.
What is your website?
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 far as pausing Cloudflare and same result.
Give me a moment to pull that part of the firewall down.
EDIT: Took that part of the firewall temporarily down.
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 far as pausing Cloudflare and same result.
Give me a moment to pull that part of the firewall down.
EDIT: Took that part of the firewall temporarily down.
I already did. It proves what I already knew that it is happening on x10 side.
Yes. No dice.
When you make changes in cloudfare, dns or redirection you have to clean the dns of your pc if you use windows use the command:
ipconfig / flushdns
If you do not clear your browser cache so that it does not continue using the same dns as before.
Same result.
How do you have this set up? you have the problem on the server, I have accessed your ip directly and the same problem
, which is not setting my IP either since the alias will be configured in Apache as www. somehow.
Another fact that I have not said, also change the name of the domain and then rename the old one again, and also redirect the requests to www.xx.xx.xx this made the browser to be blocked by multiple requests but to try .. .xD
, which is not setting my IP either since the alias will be configured in Apache as www. somehow.
Another fact that I have not said, also change the name of the domain and then rename the old one again, and also redirect the requests to www.xx.xx.xx this made the browser to be blocked by multiple requests but to try .. .xD
Last edited:
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 checked for performing a forced https redirect. That never even showed in .htaccess but I still had it removed and started fresh with none and tried adding a redirect to go back to http but it doesnt seem to budge, after clearing everything. I'm thinking something in DA is still upholding a https redirect when it shouldn't be. I tried adding the redirect to www. but it does the same thing because it seems that it stops at that error before handling anything else.
- Status