Jump to content

Recommended Posts

Posted

The IP: 66.220.18.190 when entered into safari etc. redirects to wiki-Dev.bailey.cf. I understand this isnt normal behaviour because when I tested your dedicated heliohost IP for the forum the IP was shown within the search bar.

Posted

The wiki software is causing that redirect most likely. Try moving the index and htaccess out of the wiki folder and see if it continues. The site shown by the ip is not always the one on your main domain.

 

Mine is http://66.220.18.187/ and it gives me the content of https://si3.raxsoft.com/ Thats a subdomain of an alias that I have (though oddly that happens to be the most used thing on my account, Im fine with it).

 

Also, your dedicated ip can be used for FTP as well. I had to use mine for this during the outage on Friday. If you had it enabled beforehand (cP wont work to enable it) remote MySQL can be used over it too I believe (I didnt, so I used ssh and command line tools though that wont apply for non-admins).

Posted

Im not sure honestly since I never looked into it. I imagine the default site for a dedicated IP would be related to something like the order of stuff in the Apache config though. Krydos would know.

Posted

Ive fixed it now so it shows what I want it too but only over SSL: https://66.220.18.190 this is the same on my heliohost domain aswell.

 

The IP and Bailey.heliohost.org both only work over SSL? Any reason why this may be?

Posted

Cpanel domains aren't designed to be access by IP alone. Doing so is going to result in fairly random results. I'm not sure why you would need to access it by IP anyways. Probably the reason wiki.dev.bailey.cf comes up when you go to that IP is because apache gets a request for 66.220.18.190:80 and that is quite ambiguous because there's like a dozen different virtualhosts that match that IP and port. wiki.dev.bailey.cf is currently the last virtualhost that matches so maybe that's why it goes to that one. There is really no way to control what order the virtualhosts are listed in httpd.conf either. If you really need to access your domains by IP alone you would have to remove the ambiguity by having each domain and sub domain on it's own IP.

Guest
This topic is now closed to further replies.
×
×
  • Create New...