I've uploaded my site to my public_html folder, however I'm still getting the default cPanel page.
I've tried using both index.html and index.php files with no success. For some reason it's not realizing that I've got a valid home file in there.
Does anyone have any ideas on how to get this fixed?
Make sure that your domain is configured to point to account IP address. Account IP address you can see in your cPanel user interface in the left info section. Finally, DNS A record of your domain should be equal to it.
Related
I installed CentOS7 on Amazon EC2 instance, I also installed latest version of CWP(CentOS Web Panel). I created a new user 'myuser'. I associated a domain 'myuser.com' with the user. I uploaded the website files into '/home/myuser/public_html/' and I deleted the default HTTP test index.html present in the same directory. Now I can access my website at http://IP_ADDRESS/~myuser
But when I point 'myuser.com' with my server IP - IP_ADDRESS, it shows CWP HTTP test page. I even modified my host file to make 'myuser.com' point to IP_ADDRESS.
It just shows CWP HTTP test page.
Please someone help me in solving this issue.
Thanks in advance.
I got that just googling for "default page cwp"
Take a look here -> http://forum.centos-webpanel.com/apache/default-page-displayed-for-all-domains/
For Google compute engine (Maybe same scenario in Amazon) in CWP Setting don't use the same IP that is being used for cwp admin panel. Use the default IP that will be suggesting just below the field of Shared IP in cwp setting.
In google compute VM Instance you'll find two IP's internal and external
For domain name server setting use external IP while in cwp setting change Shared Ip to your internal IP.
After 10-15 minutes use Kproxy to browse your site again should work then.
Its just temporary issue. Clear browsing data. This mainly happens in Google Chrome. As you didnt open http://IP_ADDRESS/~myuser before creating newuser, you could view uploaded files, as you might have opened myuser.com before uploading and after pointing to server IP, you are still seeing default cwp template.
I am having a hosting server and i want to create a subdomain for apis hosted on same server.What i want is suppose I have my domain name domain.com and want to have sub domain api.domain.com and set a folder path /public_html/api for it to load APIs.What I did is created a sub domain in Domains/subdomains section in cpanel and set folder path there and then created a CNAME pointing to IP of my server. but unfortunately when I open it, it gives me error Internal Server Error.
Please suggest what need to do for configurations ?
Thanks!
Click on the "Subdomain" option in cPanel and create your subdomain, pointing the root document to your desired folder /public_html/api
It might not update right away either. I just did this the other day, then I tried going to the new URL and it wasn't loading, I thought I did it wrong. I checked the subdomain the next day and it was working.
Wait for some specific time period, the domain will automatically be accessible after some time. actually, it needs some time to propagate and resolve IP associated with a particular sub-domain. it takes around 24-48 hours to resolve. To know more about this process, Please refer to the detailed explanation here
I tried to take a Joomla website offline, so I made some changes in .htaccess. I tried this...
order deny,allow
deny from all
...but nothing happened at all.
Then I tried to turn the radio button (site offline) on in Joomla global settings and I put a message saying "the site is under maintenance".
Now the thing is, when users try to access the domain instead of showing my message it says the site is not available. It also happens when I try to access my webmail, cpanel, or administrator. It says "The server at domain.com can't be found, because the DNS lookup failed."
What happened?
There are some other users who need to reach their emails soon and it's a mess. I hope you can help me with this.
Revert the changes in your .htaccess file (and wait a bit), you are essentially denying anyone from accessing the website. They can't access the offline page if they can't access the website.
Note that there are some hosts that delay the loading of the .htaccess file (no idea why) and cache the old version for an hour or so, that's why you probably haven't seen any changes to your website when you made the change to your .htaccess file.
I have cloned my Liferay machine and got another instance with different IP and DNS. Unfortunately, once I visit my new address, server does 301 redirect to old address.
I can visit new site, can't open it's control panel etc, since it's always throws me to old name.
How to overcome?
UPDATE
I have edited my hosts file so that it points myoldname.mydomain.com to new IP. This way I am able to browse new site under old name.
I went to Portal Settings and changed Virtual Host parameter from "localhost" to mynewname.mydomain.com
I was thinking that this parameter controls redirect but was wrong: it still occurs. Any ideas?
The virtual host setting can also be done per site - check if your site has a virtual host configured as well (it's in the site's settings/configuration, should be easy to find)
I'm looking to figure out how to replicate the functionality of GoDaddy's PreviewDNS when I'm moving a site to my own web host based in cpanel.
My setup is this: I have a wordpress multiuser site setup with a subdomain install, and a wildcard redirect.
I can't figure out how I can preview the website for an account before the DNS is switched over to my host from the old host.
I've been able to sorta do this by creating an A record of a subdomain over to my host, but I still have the issue of not being able to test the actual files instead of a copy in a subdomain.
I have two IP addresses attached to the server, one to the server itself and all the shared domains, and the other dedicated to the WP multisite.
When I go to http://ipaddress/~username/, I either get an error, or get redirected to the wordpress multisite's default "this site doesn't exist, sign up now to create it" page. I've tried this with both IP addresses with no avail.
Any ideas?
I think what you're trying to do is ensure that everything is working on the new server before having the DNS globally changed for all users? You could change your local computers hosts file to point the domain (and any subdomains you wish to test) over to the new dedicated IP address, which is essentially moving the DNS over for just yourself.
Here's a pretty good guide on how to do it: http://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/