I am planning for an architecture for the cluster of shared hosting servers. I intend to run around 10000 websites initially on Linux as well as Windows servers. I am planning for a load balanced setup and failover cluster with SAN or a similar storage solution where all the data will be stored. I am looking for suggestions on the best possible architecture which can accomodate all the above things. Also I need to know what are the best options available for load balancers and clusters.
I own a social network generating over 50 million page views a month. Currently, I use only one massive server. I want to add in a new server just for image serving, as my current server is killing me with high bandwidth costs.
Server A runs the website and the logic Server B runs runs the images
What would be a good architecture between the two servers, given that they ARE NOT IN THE SAME hosting infrastructure (SoftLayer is not a great option if you want alot of bandwidth)
If a user changes his photo on Server A which runs the site, somehow Server B must be notified and gets a hold of the new image..... what would be the most technically feasible and optimum way to achieve this?
Sorry to be always posting these "Anyone use such and such on shared hosting servers?" But it's pretty much the best thing I can think of instead of experimenting and going through all problems myself first. I guess all of us likes to see someone else try something out first and give feedback on it before attempting to implement himself.
I want to try this GreenSql as a way to help prevent user's web apps from being hacked using sql injection. Ive tried suhosin sql protections in the past but they simply don't work, but there is no kind of docs or even simple explanation anywhere about it on hardened-php site so that's probably why.
If anyone here uses this, has used it and knows anything about using this on a shared server please share your experiences. I am going to implement it on a test server no matter what but would be nice to know that this isnt one of those things with insane default rulesets.
It looks real cool and I will be giving it a try myself probably tonight and tomorrow. If anyone is interested I will post my findings.
As the rest of you hosts know we cannot guarantee 100% security or any kind of hack proofness. But in my time I have found out taking some steps to help preventing weak and outdated php apps can help in preventing disgruntled wep-app-hacked clients from making a crusade on the web saying you servers are insecure, crappy and all that. Isn't a sure fire way but I think it helps.
A nehalem with 12 GBs of RAM. It would have 10 TBs of bandwidth. Just wondering how much stress does it use on the CPU/RAM? How many accounts should I put on it? Lets say each account is 1 GB of space and 10 GBs of bandwidth.
I use shared web hosting service to get my website online. I'm wondering how many people use dedicated servers or virtual private servers instead and pay from $20 to several hundreds of dollars? Will I face any big problem with shared web hosting package which makes me choose dedicated servers?
obviously a (relatively successful) shared host would have multiple servers hosting their different clients. But they'd usually have all their client's setting their domain's nameservers to just one set of DNS (i.e. ns1/2.hostsdomain.tld)
Would you set this up via a DNS cluster? I.e. on a cPanel/WHM following these sorts of instructions?
For some reason I never can fully get my head around DNSes, so apologies if I ask any silly questions thusly.
With the above in mind, say your billing system sets up a new client - say it sets them up on SERVER2 (the host's second server for hosting clients). The DNS records would automatically be synced to the name server, right? And then, when someone visits the client's website/domain (with nameservers ns1/2.hostsdomain.tld) the 'hops' would roughly go:
Client's domain >> Host's name server >> This 'forwards' the 'connection'/request to the client's website files on SERVER2
Is that about right? And if the name server and SERVER2 are hosted in physically different parts of the US (say), would this make each request slower since it involves hops to two different servers before the client's files are shown?
Our website is based around a customer based chat system. Customers are only on the system during a particular day and time range. So for parts of the week the server gets almost no traffic. When then time for a chat comes up we get hundreds of people on the site all doing page requests every few seconds.
So as you might imagine we are bringing the server to it's knees with heavy CPU and memory loads. Plus bandwidth usage is really high. We are currently on the biggest box that Rackspace has to offer. The site runs ok on it during these times. It's a little slow but not unbearable.
But we have not hit our max customer base. In fact if all goes well we will double our customer base next month. So I know when we do we will bring that box down totally.
I was thinking about possibly trying a cloud/cluster based approach but after some research on this site I have found that is probably not the best option.
So I am looking for advice on what to do? Is there a better host? Different technology?
Servers are not my thing really so I could really use some help.
No we can't change the way customers access the site or when they access. There is nothing that can be done in that regard so don't suggest it.
I'm looking for a reliable hosting provider with a well-connected network and a responsive customer support team. I like my current provider, but they can't handle DB clustering, SANs, etc.
Details are below. I would provide all of my own OS and DB software. Suggestions based on first-hand experience would be appreciated ......
we have 5 Rack with about 110 servers and 200mbit of connection, every rack use 1 cisco catalyst 2950 without any hw firewall (we use iptables) now we want organize all with a cisco pix 535 firewall and a traffic shaping solution, what do u think of this configuration?
Ethernet connection from datacenter | | 1 Gigabit swith with the 200mbit connection | | 2 Cisco Pix 535 in fail over | | Traffic shaping server | | | | | | | switch1 switch2 switch3 switch4 switch5
if there was a way of remotely verifying my dedicated server architecture.
The hosting is done through our design company who then use a 3rd party for hosting a number of sites, and as such I don't have direct access to server control panels etc.
Short of just taking their word for the fact that we have the servers we're supposed to, I was wondering if there's any way I can be sure. We're supposed to have dual web servers plus a database server.
If I have 'mydomain.url' registered with company A, and that points to a shared web server with company B, how does the web server know which of the pages it hosts to serve to the visitors, since they are all on the same IP?
I was wondering what is actually the best service to offer? Shared , Reseller or servers. Im currently looking into shared and resellers but what is the market like for actual dedicated servers?
I was wondering what are typical configurations of Dreamhost servers used for their shared hosting. I guess they probably have something like 4x 500GB HDDs just for the few customers they have and who host their music collections on their account ....
Is it normal practice to have shared filespace that multiple web servers can access? Then I just provide my developers access to that filespace (one server, instead of multiple users on multiple servers) to manage files for different sites easily... right? (also meaning multiple servers can serve the same content)
So.. what would be the best way to do this? We're talking Linux systems here by the way. What sort of specs would such a server need?
I *think* it's NAS that I'm trying to get at.. unsure though if that's correct or not!
My friend asked me earlier if I knew any places in EU that allow IRC, have Unmetered 100Mbit (SHARED, not Dedicated), and allow torrents. I didn't know so I come to WHT for help.
The host must have:
Unmetered 100Mbit Shared IRC Allow Allow Torrents DDoS Protection (not required, but is a bonus) Must be in Europe
I'm unsure if asking this is allowed (since the host must allow torrents), if it isn't allowed please lock the thread.
I'm trying to find at least three web hosting companies to choose from to host a Joomla websites on a shared server. Would consider dedicated if the deal was right. I have a friend of mine who wants to create a church website, and is looking for the best deal. I use Netfirms which I have never had an issue with, but I didn't want to be bias, and would like give him other options to choose from.
Is there a good WebHosting Review site, I could check out, or maybe someone could recommend their top three. I reading threw the forums here and I noticed there are not that many complaints with Hostgator. Again, I just want to see if there was anything out there better.
This question gets asked a lot in our Helpdesk and I figured I would post our knowledgebase article here to help anyone else wondering the Pros and Cons of Unlimited Domain Shared Hosting vs. Reseller Hosting. If anyone has anything else to add, I appreciate any feedback on how we can improve our KB article.
---------------------------------------------------------------------- Given the present state of shared hosting, many clients may ask "Why would I need a Reseller account if I can host unlimited Addon and Parked domains within a single shared hosting account?". There is certainly enough Disk Space and Bandwidth provided in many of today's hosting packages, so why bother to purchase a Reseller account?
Many don't realize the drawbacks of hosting large numbers of domains within a single hosting account until they've already packed tens of them onto a single package.
So how do you know whether a Reseller account or Shared Hosting account is right for you? The answer is in how you plan to provide access to others and how "mission-critical" the sites are. You should consider the following factors when deciding on hosting a large number of domains:
1. Who will be managing these sites?
2. How important is site security between sites?
3. Will these domains need dedicated SSLs?
4. How resource intensive will these sites be (RAM, CPU, MySQL)?
In a nutshell, Reseller plans are for those who wish to host websites for other sub-clients and a shared hosting package is for a single individual managing multiple personal domains. We'll go over the 4 points above in greater detail.
1. Who will be managing these site?
If you personally own multiple domains and wish to host them within the same hosting space, you can easily do so with an Addon or Parked domain. An addon domain will allow you to host a new domain within a subdirectory of your hosting space. A parked domain will allow you to have multiple domain names point to the same content. Since addon domains reside within the same user space as your main domain, you can manage all of your domains with a single login. You can see the problem if you want to provide another user with access. Since all accounts are managed with a single set of login credentials, if you give another user access to their addon domain you are also giving them access to your main domain. If you have vital information stored on your main domain and you are hosting another domain as an addon domain for someone else, you cannot provide them access to their hosting without compromising the integrity of your main domain.
When hosting sites as a Reseller, your clients in turn will want access to their account and will want exclusive rights to their disk space and server resources. With a Reseller account, each sub-account you create gets its own username, password, and isolated user space on the server. Individual clients of yours have access to their user space and their user space alone. In addition to the isolation with regards to access concerns, each account also gets their own cPanel access. All of the same great features that you use to manage your sites can also be given to your clients. Next time client Y wants to add an email account, you don't have to do it for them for fear of giving them access to your cPanel, you can simply give them their login details and they can manage their own email accounts.
2. How important is site security between sites?
This is along the same lines as point 1. This is not necessarily related to who you are hosting for, but what content you are hosting. Imagine that you are a webmaster and you are hosting your own personal site-in-a-box community forums (such as PHPBB or vBulliten) on your main domain and a company website for a paying client on an addon domain. It is not uncommon for popular scripts to have security flaws in older versions. Script authors will often update security flaws in later versions of their software. For this reason, it is very important to keep scripts up to date on your site. But let's assume you forget to update your scripts for a couple of months and an unscrupulous individual takes advantage of a well known security hole. Using this exploit, they gain access to your forums and any subdirectories. Since you are hosting another domain as an addon, they now have access to this domain's content as well. A site defacement on this company's site may not bode well for you when they are considering you for web master services in the future.
If these two domains had been separate into two individual users (i.e. two subaccounts created through a Reseller), their content would've been inherently isolated server side by Linux's user management. Sure, your forums still would've been affected by the security hole, but the break-in would've been isolated to your site alone.
Going back to our example, let's say that instead of a corporate website as an addon domain you are hosting an image gallery site for all of your cats. In this case, it may not be a big deal if a compromise in your main domain spreads to your addon domain. After all, they are both owned by you and you're only losing some time and effort to restore these sites from your local backups (which I'm sure you've actively maintained ). But then again, you are losing time and time is money. If these sites had been separated into individual users, again, you'd only have to restore one site's content.
The idea here is isolation. Reseller plans provide you with the peace of mind to know that if one of your users doesn't keep up with their site's content as actively as they should, their actions won't negatively impact the content hosted on other domains. If you and those you host in your addons are diligent webmasters, maybe this point won't have much bearing on your decision. Only you can say for sure.
3. Will these domains need SSLs?
As of this writing, SSL certificates must have a dedicated IP address to be installed. If you are hosting multiple domains on the same shared hosting package, you can still install an SSL (or purchase a dedicated IP address and install one) but you are limited to exactly one SSL on your account. If you are hosting multiple domains on the same package (and consequently the same IP), you must choose which domains gets to have the dedicated SSL.
Sub accounts of Resellers can each be placed onto separate IP addresses and, as a result, can each have their own dedicated SSL installed.
Of course, both shared accounts and Resellers' sub accounts can use the server's shared SSL free of charge. However, some clients prefer to see their domain in the URL bar when they visit https.
4. How resource intensive will these sites be (RAM, CPU, MySQL)?
We've already established that disk space and bandwidth will be no problem. But what about CPU, RAM, and MySQL resources?
It's important to be aware of the resource needs of your website. As administrators, we have to make sure all users "play nice" on the server. We can't have user X eating all of the CPU cycles computing pi to the trillionth decimal place while you are trying to serve web pages to your loyal visitors. We have to monitor the actions of all of our users and in the event someone is stepping beyond the bounds of acceptable resource consumption, we have to take action. In most cases, this entails disabling the abusive script, but in extreme cases we have to suspend the abusive user account to prevent other domains from encountering performance degradation on their sites.
If you are hosting 100 domains as addon domains, all serving nothing but static HTML pages, maybe you will stay off the radar.
But considering most sites are more complicated than static HTML, you may want to be aware of how many sites you host as addons and what content they serve. If you're hosting the latest and greatest Joomla modules, with up to date news feeds, integrated forums modules, polls, blog posts, etc your site can certainly require a degree of CPU to serve your pages. Now imagine you have 5 or 10 of these sites all hosted as addon domains. The resources these sites need to generate their content can quickly add up and before you know it you've got a friendly email from Acenet, Inc. in your inbox wondering why your user is consuming 2 of the 8 CPU cores on the server. That may be an exaggeration, but you get the idea. In the event your resource usage becomes so excessive that we have to suspend your user, now all of your sites are down instead of whichever one may be the direct cause of the spike in CPU, RAM, or MySQL consumption.
If each of these had been separate Reseller accounts, the offending account could've been suspended temporarily while we work through the cause, leaving the rest of your domains live and kicking.
The conclusion here is that you need to be aware of the needs of your sites in a general sense. Hosting unlimited domains within a shared hosting space is certainly a nice feature. For those webmasters who have multiple presences on the web, it's very convenient to be able to manage all of their personal domains from a single control panel. For those entrepreneurs who are hosting multiple domains for other individuals, the features and security associated with a Reseller plan and the inherent isolation of Linux users is a must have. ----------------------------------------------------------------------
I'have a problem with my aps setup on sanbox.When i create on customer ccp when i click finish i have this error. I must only test.
Error: Instance of application with id 124 and version '1-4' can not be provided: There is no resource of class 'Shared hosting Apache' with provisioning attributes 'Web Cluster' in subscription with id 1.:There is no resource of class 'Physical hosting (IIS)' with provisioning attributes 'Web Cluster' in subscription with id 1..If i add the shared hosting apache resourse i get this error : There are no "apache" services that satisfy given attributes: "Web Cluster".
I am developing a website for a client of mine (the client is a close friend and know's that he is getting a newbie). This site will be larger (project wise) than anything that I have ever done (everything I have done in the past has been FrontPage). We will be using several third party applications that need to run on the server as well as our own custom developed applications. We do not yet know how much access to the server's deeper structures we will need for all of the applications that we want loaded on our server to run. Things we have in mind: oscommerce, mysql, php5, apache, linux, vbulletin, blogger, phpbb, adserver, ect... Would these things run ok on a shared host and would I have full authority to configure them without needing full access to the server? Or will I need access to the entire server (dedicated server) in order to have full customization capabilities? I guess all I am trying to figure out at this point is will shared hosting for a large project limit our abilities to use 3rd party apps, or do most 3rd party application designers build their stuff to work in a shared hosting environment anyway? If we need to get a dedicated server we will, but if we can get away with shared hosting for a while (especially during development when the site will not be generating revenue) it would be nice to avoid the price of a dedicated server. Many thanks for your comments, insight, and expertise! Also, if anyone can sight some common scenarios that may require a dedicated server over a shared hosting plan, that may help me to understand what the limitations of a shared hosting plan vs. a deicated or virtual dedicated server are.
Here is my dilemma, thanks to a thread in these forums I was directed to a hosting website called pc-core.net and I was interested in using them, because it does not appear that they oversell at all. My question is regarding the fact that they have the shared hosting for $12/month with ~5gb of disk space and 50gb of transfer. I then just looked at reseller hosting for the heck of it, and noticed i could get a reseller hosting account with 45gb storage and 450gb of bandwidth for $10/month. Even though I wont be selling hosting, or anything like that, can I use a reseller hosting account like a normal shared hosting account?...just with more space and bandwidth?
I'm new to the VPS scene, so could someone tell me the difference between VPS and say shared hosting or dedicated hosting? Actually I really like to know what a Virtual Private Server actually is.. I know shared hosting is typically a single account on a server with several hundred other accounts which is used primarily for the sole purpose of hosting websites, and I know that dedicated hosting is functionally the same as colo except that you rent the server, instead of having your own purchased server plugged into some network. So what is VPS?
Do website builders generally go with shared hosting or dedicated server? I mean, if they work on several websites would they get a dedicated server instead of shared? From what I understand through reading shared hosting is basically if you only have one website. So one with multiple websites would go with a dedicated server?
