Resolved Domain showing apache msg but able to access when I use x10 URL

[eanetx10]

I was getting the Cloudflare 522 error, so per https://x10hosting.com/community/th...site-loading-errors.207926/page-2#post-979712, I went to the Cloudflare control panel, and made sure my DNS A record was pointing to 198.98.81.13.

Now, instead of getting the 522 error when I try to hit my site's domain, I'm getting a message that says "Apache is functioning normally."

If I try to hit eanet.x10host.com, my content loads, but it doesn't look like the CSS for my Wordpress is loading correctly - I see the content, but it looks awful.

I'm guessing (hoping?) that this is a DNS issue somewhere, but I'm not sure whether it's on the Cloudflare side or the X10 side, and I'm not sure what I need to change to fix it.

 

[garrettroyce]

All of your CSS and JS files seem to come from er***ms.net, which is managed by CloudFlare. I'm wondering if your domain is not set up correctly in DirectAdmin. Try logging in and then

-> Account Management
-> Domains

Make sure it's set up as a domain. A pointer would be ok to use for this purpose, but I think you want this to be your "real" domain so you wouldn't point to it.

 

[eanetx10]

Thanks Garret. It was setup as a pointer. I got rid of the pointer, and renamed the domain to be my domain name. I'm still seeing the Apache message.

Looking at the DNS settings on Cloudflare, I have
A - er***ms.net - 198.91.81.13
A - www - 198.91.81.13
and all the MX records to point to Google's mail servers.

I don't think I need a CNAME record there, but I'm not sure.

Do I just need to wait longer for the changes I made in DirectAdmin to propogate? (It's been about half an hour) Or am I missing something else?

 

[Anna]

DirectAdmin has its quirks, this is related to one of them.

With DirectAdmin you can actually have two separate sites for https and http, now free hosting does not fully support SSL as you can not install and utilize a personal certificate, but this leads to the noted message (which is the default webpage when the server don't understand what is expected to be shown) when attempting to pull content on https without it being enabled for the domain.

Despite having SSL through cloudflare (maybe depending on your settings there) the server would attempt to pull https from us, but since it was not turned on for your account and thus not for the domain either, the server could only respond with the default message.

I have enabled SSL on your account (as it should have been due to the above mentioned quirk), and when turning it on for the domain it appears to work properly, at least from my end. Note though that without cloudlfare you will get an error as the domain would attempt to use the server certificate which does not match your domain.

 

[eanetx10]

Hi Anna,

That seems to have done the trick, thank you!

(Just for my own knowledge, was this:
A. Something that is documented and I should have found myself, in which case I feel bad for bothering you
B. Something that is a setting I could have changed but isn't well documented, in which case I feel less bad
C. Something that I couldn't have fixed myself anyways, so no sense feeling bad about it
?)

 

[Anna]

The only place you *might* have been able to change anything yourself as it was now would be if cloudflare have something you could have changed so it would not require the https access on our server.

I don't know enough about cloudflare to confidentially say you could have though, but I believe using their flexible for SSL may allow them to connect to our server on http