Actually i bought a proxy website from someone here at DP, it recieves around 2k u/v daily but i am having webshoting problem, it has been like more than 10 days i bought the website but the website hasn't been up for more than 3 days totally, i tried vps first and now i am trying dedicated server but also i am having lots of issue. The website is using phproxy script and what happens is that as soon as it's online it goes down and again if i restart the http server it works well but after some time again it goes down, it's continuing the same issue. I don't want to waste huge bux for hosting, i don't even want a dedicated server if it works properly. first i purchased a vps, due to that problem i went for a dedicated server but still the same problem exist, please suggest me what should i do.
If you PM me the root pass + url of your proxy, I can take a look for you. Read my sig article for a bit of information, but seems you already took the dedicated path which is good. There can be many things wrong, but I need to check it.
Try and change from PHProxy, try anther proxy maybe? look more into access_logs, look into netstats too... there might be a HTTP Flood going on there..
Switch to a PHP based proxy if you aren't using one already. You need to get it up as fast as you can or else you'll lose almost all of the traffic!! Get a plan with: http://wdservers.com
Yes llamafier is correct. If you haven't already lost 90% of the traffic that it had, then you will soon. The only thing working for you here is that Christmas Break people will not be using a proxy that might have regularly used it. It if doesn't work for even a day you can typically count on losing 90% of your traffic. If all else fails just scrap the whole design and start fresh. Get a fresh template or just make your own using php proxy. The domain is the important part. Dedicated is the way to go if you are serious long term. Hope you get it worked out. MAtt
Hi, Sorry to know that you're facing serious hosting problems just after buying the proxy. How much monthly bandwidth is it using? Is hotlinking protection enabled? I'd suggest using glype proxy script. Oh, you can have a look at my sig
Open the index.inc.php and check what is the max download file size limit and try to lower that value to 10mb and then check the load on the server. I think your proxy is hotlinked to access some big files.
Yeah that's his side of the story, lol. But the guy knew by my previous request for help that I didn't know what I was doing with that directadmin. Then I come home to see an email with the subject line "IP Theft" from him and that message inside. He knew full well I wasn't trying to steal anything. And when he continued on in his reply that I was indeed stealing and he wouldn't refund me, I went through the roof. Just give me my money back for a service that I haven't used and won't be able to use, and we part on good terms. I don't have any experience with that type of hosting, but I've been doing business online for 8 years, and no one has ever accused me of being a thief.
Why on earth would you add IP's you don't own though? And take down other people's websites in the process? That's just wrong. If he gave you your money back, would you compensate the person whose VPS you took offline by adding IP's you don't own?
Uh, because I'm "obviously extremely lacking in the brain department, and should stick to shared hosting!" How it came about is I bought a proxy site from somebody, and it was still on his server. I was anxious to relieve him of it, but couldn't put it on my hosting, so I just went with the recommendation in loopline's proxy ebook. I should have chose cpanel, which I'm more familiar with. But went with directadmin, because I read somewhere that it was better for hosting proxy sites. But as far as the IP goes, it was just a simple, honest mistake. It was a matter of time, juggling a bunch of different projects and trying to figure out the directadmin thing, so I could get that site up. I've always seen the nameservers setup like that, two consecutive IPs, so that's what I put in, wasn't even really thinking about it. As far as the first problem, with the folder and ftp, for some reason my ftp client wasn't refreshing view, so I couldn't see that directadmin did indeed add a folder for it. And I was just hurried and got a little confused thinking that it doesn't add a folder like cpanel does, but uses a different system or something. I had a VPS a couple years back with WHM/cpanel and never had a problem, but then again I had more time to sit around and tinker with it.
At any rate, while I'm certainly not proud of the way I acted, I see on that thread he realized he too could have handled it better, which I appreciate. I see him in a different light now. So I retract my recommendation against his hosting.