seeking advice on web hosting company

[satimis]

Hi all,

I'm now subscribing Deluxe plan of Godaddy with unlimited domain hosting. They require installing a copy of WordPress on each domains. I'm encountering following problem running WordPress on hosted domains.

On Hosted Domains panel/page
say,
aaa.com /
bbb.com /
ccc.com /

It is required installing WordPress on a folder/directory of each domain.

say,
/aaa.com/wp-aaa-folder
/bbb.com/wp-bbb-folder
/ccc.com/wp-ccc-folder

However on browsing website I have to run;

http://www.aaa.com/wp-aaa-folder
http://www.bbb.com/wp-bbb-folder
http://www.ccc.com/wp-ccc-folder
respectively.

running;
http://www.aaa.com
http://www.bbb.com
http://www.ccc.com
don't work

I have sent dozens of emails to their Support Team for assistance without a result.

I'm prepared changing the hosting company. On searching I found following link;
Five Best Web Hosting Companies
http://lifehacker.com/5911651/five-b...ting-companies

Have any folks using their service before?

Hostgator offers unlimited domain hosting on "Baby Plan"

Unlimited Web Hosting
http://www.hostgator.com/shared

Application Hosting...
- WordPress Hosting - Host your very own WordPress blog
- Joomla Hosting & Drupal Hosting - Professional CMS Solutions
- Magento Hosting - Free E-commerce platform for your own store
- Wiki Hosting - Start a Wiki web site with MediaWiki

Has any folk on the forum using Hostgator web hosting service? Would the problem mentioned above happen?

OR any other suggestions? TIA

B.R.
satimis

[SeijiSensei]

I just rent virtual machines from Linode myself, so I can configure everything the way I want it to be. The naming problems you have, for instance, would be easily fixable if you could control your web server configuration.

That WordPress requirement is absurd. I run one WP instance where I host my blog. Every other website runs custom-designed PHP and HTML.

[oldos2er]

Moved to Cafe.

[satimis]

I just rent virtual machines from Linode myself, so I can configure everything the way I want it to be.

Thanks for your advice.

I have my own server here running on virtualizer. I'm subscribing Static/Fixed IP at 6M/6M up/down. It would be quite easy for me operating my own server at home. But I couldn't run 7x24. For such a reason I have to hosting website somewhere.

The naming problems you have, for instance, would be easily fixable if you could control your web server configuration.

I could touch .htaccess and index.php on Godaddy website. Any advice on how to modify .htaccess?

That WordPress requirement is absurd. I run one WP instance where I host my blog.

It is easy to build blogs on WP using their themes and plugin

Rgds
satimis

[SeijiSensei]

The naming problems you have, for instance, would be easily fixable if you could control your web server configuration.

I could touch .htaccess and index.php on Godaddy website. Any advice on how to modify .htaccess?

Only some Apache directives can be put in .htaccess. Unfortunately the Alias directive, which might be helpful here, is one of them. But you can only use directives like that in the server configuration file, at which point the easiest solutioin is simply to point the DocumentRoot to the directory of your choosing.

It is easy to build blogs on WP using their themes and plugin

I probably misunderstood your comment. I read it to mean that everyone had to use WP to design and mange their sites on this GoDaddy service. If the service is designed to host blogs, that is a much different matter.

[satimis]

Only some Apache directives can be put in .htaccess.

This is a new site, nothing built yet. I have been playing around on ./htaccess on Godaddy as follow;

Have .htaccess duplicated as .htaccess_copy

WordPress was installed on /WPReynold

./htaccess

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /WPReynold/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /WPReynold/index.php [L]
</IfModule>
....
....

Add following lines to the bottom of the above section

RewriteCond %{HTTP_HOST} ^reynoldstocks\.com$
RewriteRule (.*) http://www.reynoldstocks.com/$1 [R=301,L]
RewriteRule ^$ WPReynold [L]

Reload the webpage

On browser ran;

http://www.reynoldstocks.com

it popup "Future home of something quite cool" page

Ran;

http://www.reynoldstocks.com/WPReynold

It changed back to

http://www.reynoldstocks.com

immediately.

Deleted the tesing .htaccess file and changed the duplicated file back to .htaccess

Restart the browser (this step is important others it won't work)

Then running /reynoldstocks.com/WPReynold works again displaying WordPress front page.

Any advice? TIA

Unfortunately the Alias directive, which might be helpful here, is one of them. But you can only use directives like that in the server configuration file, at which point the easiest solutioin is simply to point the DocumentRoot to the directory of your choosing.

Could you please explain in more detail? Thanks

B.R.
satimis

[CharlesA]

I just rent virtual machines from Linode myself, so I can configure everything the way I want it to be. The naming problems you have, for instance, would be easily fixable if you could control your web server configuration.

I moved from shared hosting to a VPS (serverdragon/securedragon) and I am so much happier with the service and performance of my site. There is no way I would go back to shared hosting again. Granted setting up the server for the first time can be a pain, cuz it's unmanaged, but it isn't too bad.

That WordPress requirement is absurd. I run one WP instance where I host my blog. Every other website runs custom-designed PHP and HTML.

I agree. I haven't really touched WP, but my site is mostly HTML and PHP.. and I would be really annoyed if I had to install wordpress just to host my site there.

As far as Apache goes, I do not use it, so I don't really know much about the configuration. =/

EDIT: If you want to stay with godaddy, just ask them to change your document roots to point to the folder with the wordpress install.

I think they use a .htaccess file to do that on my shared host and it screwed everything up because of the way it was set up.

[satimis]

- snip -
There is no way I would go back to shared hosting again. Granted setting up the server for the first time can be a pain, cuz it's unmanaged, but it isn't too bad.

- snip -

Absolutely agreed. I have been struggling at least 3 weeks. Godaddy Suppot only turned me around. Each time to my request for support they just copied and pasted the online document on their emails as reply.

Now I have sorted out my problem.

To make multi-domains to work on WordPress(WP) perform steps as follow;
(I'm not going to mention "Hosted Domains" setup here)

1) Install WP on a directory/folder of the domain (not root/webroot)
say, aaa.com (directory)

2) Create a directory /aaa.com/wpaaa for WP and install WP on it

3) After installation completed and effective, go to File Manager. Copy both .htaccess and index.php on /aaa.com directory

4) On index.php

change the line - require('./wp-blog-header.php');

to - require('./wpaaa/wp-blog-header.php');

reload the page. That is all, not necessary touching .htaccess


On browser running http://www.aaa.com or /aaa.com displays WP front page. That's it.

However to login WP it still requires full path, /aaa.com/wpaaa/wp-admin. I haven't found a solution yet,.

Edit:

Do serverdragon.com has MediaWiki installed on their site? Hostgator has this application which I expect.

B.R.
satimis

[d4m1r]

No such thing as unlimited bandwidth, storage, etc. All servers including those run by the big guys have limitations. Unlimited is just a marketing gimmick and you are better of just searching for reviews of a host you are interested in

[SeijiSensei]

Even a $20/month virtual server at Linode gets 2 TB of traffic per month. Suffice it to say I don't come close to that figure. The basic server comes with 24 GB of storage. Not enough for large multimedia archives, but certainly enough for ordinary web hosting and email.

 Unfortunately the Alias directive, which might be helpful here, is one of them. But you can only use directives like that in the server configuration file, at which point the easiest solutioin is simply to point the DocumentRoot to the directory of your choosing.

Could you please explain in more detail? Thanks

The Alias directive lets you choose a directory to be represented by a URI. The directory can be anywhere on the operating system where the Apache user ("www-data" in Ubuntu) has read rights. An alias usually looks like this:

Alias /news /path/to/some/directory

then requests for http://www.example.com/news are directed to the specified location.

You cannot issue an Alias request in a .htaccess file, because things like aliasing must take place before the document root is determined. If you follow the link in my earlier posting, you'll see that the Apache documentation gives the locations where each directive may be used.

However if you can manage the server configuration, then the solution to your problem would have been to define the DocumentRoot for each virtual server to point to the directory where the WP site was located. You cannot do this from .htaccess either since the DocumentRoot is already determined to be the directory where the .htaccess would reside.