Tag Info

Hot answers tagged

43

What we generally do, at work is : before we update, the document root of the server is : in /www/app-2009-09-01 but is accessed via a symbolic link, called /www/application we put the whole new code base to /www/app-2009-09-08 once the whole code base is there : we remove the old symbolic link we create a new symbolic link, still called ...


25

During the high traffic period your server should be able to handle all requests made by visitors to your website. But there are some limits in concurrent connections handled by the server. So it's best to serve the page requests as fast as possible. Here are some suggestions to consider in these situations, Application level improvements: 1. Minimize ...


8

Options: Set up a local site for testing purposes. Something like WAMP should do the trick. If you're going to do the testing on your live server, temporarily block your site while doing your testing. A 307 HTTP response would be appropriate. Use basic authentication to keep crawlers and everybody else out while you do your testing. Since your site will be ...


7

First of all, unless you planned on the site going down every day at the same time, you have a hosting problem and you should fix that ASAP. There just isn't any good reason for your current hosting provider to go offline that often, for that long, and that consistently. If it is a planned outage, please be sure to serve up a notice so there isn't a bare ...


7

You can use virtual hosts in apache to have 2 versions of the code at 2 different urls. A commonly used example is: test.example.com -> /var/www/version1.2 www.example.com -> /var/www/version1.1 both of which are on the same server, but perhaps only one is accessible to the world. Once you are satisfied that test.example.com is working, you can ...


6

Are you on a Linux/BSD machine? If so, you can easily use symbolic links to accomplish this goal. Create Version 1 of the site here: /var/www/www.example.org.v1 Create a symbolic link pointing to this directory cd /var/www ln -s www.example.com.v1 www.example.com This should give you a directory listing (ls -la) that looks something like this: ...


6

First of all, I'd recommend Cloudflare. You can create a free basic account and it will route traffic via local data centers to minimise the amount of server hops. Cloudflare's also great for caching content and has DDOS protection. Other than that, try to trim the fat from your service layer. Make sure you don't have any overly bloated database queries ...


5

Don't do testing in a production environment if at all possible. It's a recipe for disaster. Create a testing subdomain that's isolated from your production site as much as possible. This will allow you to test you changes on the server without, hopefully, endangering your production site. You can use robots.txt to block 'bots from this subdomain so it ...


4

Well, should have checked the NameCheap knowledgebase, first: How to transfer a domain into Namecheap without a huge downtime? NameCheap offers a FreeDNS service so their name servers can start handling DNS requests before a transfer. I suppose it would keep working when transferring away from NameCheap, too.


4

Check into UptimeRobot http://www.uptimerobot.com It's free, offers HTTP and ping monitoring every 5 minutes with email, text and RSS notifications. To my soon to be former webhost's chagrin, it's very reliable with uptime monitoring logs and past event tracking.


4

It's really very hard to suggest anything without more information, the nameserver thing is weird but not unheard of in the messy world of DNS. If I had to guess I'd say it's something local rather than your site. The most common cause I've seen for this kind of thing is the adblock plugin, cached DNS information or overactive antivirus/antimalware. I'd ...


4

Consider load testing your site. There are free tools available such as JMeter, The Grinder, and Gatling, which can simulate large numbers of visitors to your site. By testing the impact of heavy traffic ahead of time, you can determine whether any tuning you've done has been effective, and look at further tuning if not.


3

I think you really should look into a mirroring structure to perform this kind of work. However, if you can't do this, the best way to decide when to perform this maintenance work would be to observe the hourly traffic on your web site so you will be able to figure out what is the best timeframe. Also try to determine most timeframes as possible, that way ...


3

The best way to do this is usually to do the load balancing inside your network where everything's under your control, eg with a load balancing proxy, a floating IP or internal routing. However, if these servers are on different unaffiliated networks as you say, this is generally not practical. The other method to achieve this is using DNS failover, but ...


3

While Will is correct that the retry-after value is optional, I'd suggest setting it anyway as a matter of practice. Setting the value has the benefit of being unambiguous. A 503 without retry-after "should be handled as a 500." If any crawler/script/etc. requesting the documents has been configured to treat 500 differently, then you can't be entirely ...


3

You must check that your site is available from outside of your network. You can use sites like http://www.downforeveryoneorjustme.com/ to check that your site is accessible. If it passes this test, then likely there is nothing for you to do. I have seen issues such as this where a network is failing to resolve the domain name, or fails to deliver either ...


2

In your case, the solution should be at least 2 servers with the same content and a frontend proxy which proxies the traffic to the servers and handles failover in case one server is down. But it is a quite complex configuration and you probably need to hire a sysadm to configure and manage it unless you know what you are doing.


2

mon.itor.us and SiteUptime have free/ad-supported plans. Check are only at 30-minute intervals however. They both have plan upgrades which measure at 5 minute intervals and are cheaper than Pingdom, so you might find a reasonable cost/benefit trade-off.


2

http://aremysitesup.com/ offers a free plan with 15 minute interval checking, or a paid plan (from $5.42/month) for 5 minute interval checking. If you're just monitoring one site, pingdom's free account offers 1-minute interval checking -- you just need to login once every 90 days to keep it alive: https://www.pingdom.com/signup/free/ (If you're monitoring ...


2

The Retry-After header is optional. It if is specified, then it helps search engines determine when it's appropriate to crawl your site again.


2

Use Scalr Fault-tolerance, backups, uptime, and efficiency Scalr provides you with a high uptime, fault-tolerant website: Scalr monitors all your servers for crashes, and replaces any that fail. It backups your data at regular intervals, and uses Amazon EBS for database storage. And to make sure you never pay more than you should, Scalr ...


2

Google, and all the other Search Engines, crawlers, bots, etc., crawl your site every day (if your site is big enough indeed). Google crawls the important pages for changes at a higher rate, like your homepage and your highest quality content pages, and randomly the rest of your pages to make sure that it's up to date. Now, the pages that randomly Google ...


2

Just switch off Cloudflare for those subdomains. Turning off Cloudflare using the orange button does not change your DNS records. It just bypasses Cloudflare's caching, performance, and security network. Cloudflare will still route traffic to your server. There's no need to worry about DNS servers caching old records, because those records won't have ...


2

If you're on 1and1, likely you're looking for cheap hosting. Cheap hosting means you tend to do everything under one box. A major pain point for hosting is that when you host everything on the same box, you're splitting resources between to important parts of your site: Your web server (Apache, Nginx, etc) Your database (MySQL, PostGreSQL, etc) And being ...


1

I've had a similar problem before and have solved it using CloudFlare's API. I had a Dedicated server and a large VPS for backup. Mirrored the data on the two servers, and used CloudFlare to switch between them (DNS Failover) if the Dedicated went down. Initially did reboots via SSH/IPMI to verify and it worked as configured. Here's the link to the article: ...


1

James, sorry to say but i don't think it will automatically gain previous position by just uploading same content and fixing Google webmaster suggestion. As your website was down for such a long time and it lost all its credential/rankings/ and other reputation. As search engine does not love 404 pages !! Apart from this, there are many updates rolled out ...


1

Pingdom seems to be a popular tool for monitoring web site uptime. I haven't used it myself but they do provide SMS and email alerting.



Only top voted, non community-wiki answers of a minimum length are eligible