The site's a fair bit quicker now - however the graph is all weird. I'll fix that in the morning.

How about external HTTP requests? I mean, does your host need to forward outbound ports too?

No idea. Here's a good suggestion - try it?

In case you're interested - here's a full/detailed documentation about the API that I now offer. http://docs.typefish.co.uk/documentation/12/

It's back on http://www.typefish.co.uk/samp-conn/ - I don't know if you guys want to re-sticky this or not.

It's actually a measure to prevent query flooding. The server is limited to about 50 queries per second.

Services to the site may be disrupted over the next couple of hours so be aware.

It's 80 - it's a HTTP request.

No, a graph, stupid.

I've added a surprise. Guess what it is.

Are you sure it's PHP 5.3.8? What does phpinfo in Apache report?

Look at my signature, then look at the source code, learn and then make your own.

Quote: Originally Posted by funky1234 Are you forwarding ports correctly? Is it allowed through your firewall? Also it won't appear on the hosted list unless you pay for the privelledge. ...

It's not an exploit - it's rather an attempt to stop the server from causing a DoS.

There is a limit of about 100 or so (I can't remember off the top of my head) query requests per second across the entire server, so that's what may be causing it - SA-MP's own "defence" mechanism.

Use a SOCKS via SSH proxy - host a sshd port on 443 and you can usually get around such things.

Well, obviously I had learnt PAWN first. But still, making something and then making it secure on your a first project was rather daunting.

I started to learn PHP by making control panels. Seriously.

Here is a simple bit of PHP for you to ponder over. PHP код: trait Block {         public                 $hello = null,                 $sMessage =...

I don't use exec() for starting anything. Ever. It hangs. For Linux, I use a combination of proc_open and proc_close, and for Windows I use the WshShell COM object.