503 Error

Connect with other users about what to run on your webhosting (and how to run it) here.
Post Reply
User avatar
hakkuo23
This is my homepage
This is my homepage
Posts: 88
https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
Joined: Thu Aug 05, 2010 5:04 pm

503 Error

Post by hakkuo23 »

How can I remove this error since you guys don't offer a better plan for webhosting. Is there any other company that offers more resources without going to a VPS since I'm not a fan of that xD
User avatar
kraze
Former staff
Former staff
Posts: 4362
Joined: Fri Sep 17, 2010 9:06 am
Location: California

Re: 503 Error

Post by kraze »

Hi,

What exactly are you referring to? If I remember correctly 503 error is when to many people or connections are attempting to visit/connect to your site at once.

Is this your problem?
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
IcEWoLF
This is my homepage
This is my homepage
Posts: 1192
Joined: Thu Aug 10, 2006 9:41 pm
Contact:

Re: 503 Error

Post by IcEWoLF »

I use a VPS and I love it for web hosting.

Anyways, a 503 error doesn't sound like a resource issue, but more like something like this: http://www.checkupdown.com/status/E503.html

I had the NFo base web hosting package and it worked well.
Image
Image
User avatar
Edge100x
Founder
Founder
Posts: 13120
Joined: Thu Apr 18, 2002 11:04 pm
Location: Seattle
Contact:

Re: 503 Error

Post by Edge100x »

If the error talks about hitting capacity, then you're probably running into your concurrent user limit. This is extremely hard to do under normal circumstances, so that situation would likely indicate that one of your scripts is buggy and taking too long to process. If it takes 2s to process a broken script that should normally take 0.1s to process, for instance, you immediately go from being able to handle 2000 page loads per second to only 100, under the 200-connection top plan (assuming an even usage distribution).

One way that I've seen scripts randomly take too much time to execute is when they have been dependent on flaky external services, such as the Coral CDN. Another is when the script queries something with every page load, such as a game server or voice server, instead of caching the result -- if the server goes down, it might hang while waiting for a response.
Post Reply