Root domain still not fixed. Forced redirect to https with invalid certificate.
- Thread starter rontek
- Start date
- Status
- Messages
- 2,199
- Reaction score
- 195
- Points
- 63
i tried http://blitzcoder.x10host.com/ and http://a12luismc.x10host.com/
both give me a 403 forbidden error page.
https is only available to paid accounts, free accounts do not support it.
you need to remove any references to https.
you also need to set your cloudflare to accept http not https.
if you use wordpress or similar, its the same, change it to use http.
both give me a 403 forbidden error page.
https is only available to paid accounts, free accounts do not support it.
you need to remove any references to https.
you also need to set your cloudflare to accept http not https.
if you use wordpress or similar, its the same, change it to use http.
- Messages
- 11,752
- Reaction score
- 581
- Points
- 113
I have reminded admins once again about the root issue that someone elses content is shown.
As for cloudflare and SSL on your root domain, appears you don't use our name servers so we could not possibly change anything.
That being said, on the records we do have there is a cloudflare notation for the root domain, I'm not using cloudflare myself though so not sure that is the missing link in its own, they are just not queried when someone visits your domain.
As for cloudflare and SSL on your root domain, appears you don't use our name servers so we could not possibly change anything.
That being said, on the records we do have there is a cloudflare notation for the root domain, I'm not using cloudflare myself though so not sure that is the missing link in its own, they are just not queried when someone visits your domain.
I was using CloudFlare+CPanel before and it was running perfectly since I have set it up back then.
not sure if this would help with my case that someone else successfully re-entered my domain even without a ssl certficate as @Anna mentioned on my previous thread.
Thanks. Looking forward to finally having the root domain issue fixed without someone elses using my root domain with a broken or missing certificate.
There were no ssl or cloudflare issues until the DirectAdmin switch as it was working before until this another account using my domain thing happened.
It seems we cannot push through the validation as it is still pending with that someone else account using my domain with the same server and ip.
Last edited:
- Messages
- 2,199
- Reaction score
- 195
- Points
- 63
that was of course before directadmin and a lot has changed since then.
i was also using cpanel and ssl then too but since the change have had to stop using ssl.
many others also had stopped using ssl when their ssl certificates ran out.
it has been posted in many posts about the ssl not being supported anymore.
here is just 1 for example that Anna Replied to, my site is down
cjptomas80
Member
- Messages
- 266
- Reaction score
- 6
- Points
- 18
Maybe he wants the same functionality of Cpanel Cloudflare module into DirectAdmin for subdomain.
- Messages
- 11,752
- Reaction score
- 581
- Points
- 113
There is no cloudflare plugin for DirectAdmin, so the same functionality can not be achieved. For those that had it working since before it should have stayed working provided no changes was made. We can however not guarantee that at this point.
Of course, there shouln't be someone elses content showing either, and that part is definitely on us to sort out.
I understand that it is a frustrating problem, but the reality is that if we hadn't made the change to DirectAdmin, it would likely have been the end of free hosting as cPanel licenses would be to expensive to keep providing free hosting, they charge a base price for the server plus an additional fee for every single account on that server.
Of course, there shouln't be someone elses content showing either, and that part is definitely on us to sort out.
I understand that it is a frustrating problem, but the reality is that if we hadn't made the change to DirectAdmin, it would likely have been the end of free hosting as cPanel licenses would be to expensive to keep providing free hosting, they charge a base price for the server plus an additional fee for every single account on that server.
Thanks guys for the input and feedback.
Thanks @Anna. Yes, I would just like to have this fixed and not showing someone elses content on my root domain just like the way it was and we can move forward from there. I hope this will be sorted out as soon as possible.
Thanks @Anna. Yes, I would just like to have this fixed and not showing someone elses content on my root domain just like the way it was and we can move forward from there. I hope this will be sorted out as soon as possible.
- Messages
- 11,752
- Reaction score
- 581
- Points
- 113
We just noticed one thing, the domain doesn't point to the correct IP, and since you don't use our nameservers that would be something you need to update. The IP of your server is: 198.91.81.11
Can't say for sure that will solve the issue, but it would definitely be needed as the old server will eventually go offline.
In any case, as long as it points towards the wrong IP we are unable to troubleshoot further.
Can't say for sure that will solve the issue, but it would definitely be needed as the old server will eventually go offline.
In any case, as long as it points towards the wrong IP we are unable to troubleshoot further.
Hey @Anna finally, I can see some update and now that someone else's account is no longer showing up when browsing my root domain https, though there's this ssl error which is normal, thanks for this. I'm glad that this is out of the way and certainly a big step on this issue.
I did some browsing for related topics and found this, perhaps you can confirm if this similarly applies to this server.
https://x10hosting.com/community/threads/newly-uploaded-content-404.206941/#post-973896
My question now is what would be the new setup for the root ssl + directadmin?
Related to that, my directadmin is also not accessible, but noticed this already a day before the IP update notice.
I did some browsing for related topics and found this, perhaps you can confirm if this similarly applies to this server.
https://x10hosting.com/community/threads/newly-uploaded-content-404.206941/#post-973896
My question now is what would be the new setup for the root ssl + directadmin?
Related to that, my directadmin is also not accessible, but noticed this already a day before the IP update notice.
Last edited:
- Messages
- 11,752
- Reaction score
- 581
- Points
- 113
Free hosting does not officially support SSL at this time. Though on our servers there is a cname DNS entry that has the following name: cloudflare-resolve-to, with the root domain as value, do you have that one in your name server as well? I think that may be related to getting the root domain to work with cloudflare when not using their name servers.
As for the login issues, I did see an oddity in the logs, are you by any chance using some kind of proxy? The IP is part of the redirect from SSO page and server logs indicate that the IP sent does not match what is expected (there could be some error our side and I have forwarded this up to the coder as well).
You should however be able to login if you go to the DA login page directly: https://x11.x10hosting.com:2222
Note though that doing so does not log the account as active so you would still need to login to the main site once in a while to keep the account as active. Username would be the same as you see under Quick FTP at the SSO page, password should be same as you use to login there.
As for the login issues, I did see an oddity in the logs, are you by any chance using some kind of proxy? The IP is part of the redirect from SSO page and server logs indicate that the IP sent does not match what is expected (there could be some error our side and I have forwarded this up to the coder as well).
You should however be able to login if you go to the DA login page directly: https://x11.x10hosting.com:2222
Note though that doing so does not log the account as active so you would still need to login to the main site once in a while to keep the account as active. Username would be the same as you see under Quick FTP at the SSO page, password should be same as you use to login there.
Thanks @Anna. I can now login again via directadmin with the link you provided. Yes, I do have cloudflare entries and values on both root domain and www subdomain as this was not touched and working before the switch.
Having checked my settings again and what I am curious about is there is also a check mark on Secure SSL option on my domain configuration. I would like to get some information and confirmation about this before changing anything. It seems this is only for installed certificates and does not apply to cloudflare and might be related to the cloudflare root domain pending certificate issuing problem?
browsing to my https root this is now the error (related to above?)
Edit: I went ahead and unchecked the secure ssl option, I guess I have to wait for this to update and report back again.
Having checked my settings again and what I am curious about is there is also a check mark on Secure SSL option on my domain configuration. I would like to get some information and confirmation about this before changing anything. It seems this is only for installed certificates and does not apply to cloudflare and might be related to the cloudflare root domain pending certificate issuing problem?
browsing to my https root this is now the error (related to above?)
Edit: I went ahead and unchecked the secure ssl option, I guess I have to wait for this to update and report back again.
Last edited:
- Messages
- 11,752
- Reaction score
- 581
- Points
- 113
That would indeed be for installed SSL certificates, we're running some tests currently regarding that option (apache basically doubles the information on each domain with it turned on so we want to see how it would impact the servers), but we will currently not officially support installation of certificates on the server.
That error would likely be related to the fact that the certificate is only valid for the root domain (though i may actually help with cloudflare to have it enabled as that would allow for some level of encryption between cloudflare and our servers if I'm not entirely mistaken, with cloudflare flexible that is).
That error would likely be related to the fact that the certificate is only valid for the root domain (though i may actually help with cloudflare to have it enabled as that would allow for some level of encryption between cloudflare and our servers if I'm not entirely mistaken, with cloudflare flexible that is).
Thanks and I see. Yes, I am currently using CloudFlare flexible. Looking forward to this and if there's anything that I have missed let me know since the root domain now points directly to the right ip now.
- Status