I have one big problem with apache 1.34

[jey07ro]

My site , a chat site, has many, many users over 300 users online from a proxy server! I realy care about them, but that seems that overload the server, the only answare from tech departament is this : "they only way to fix it is for them not to use a proxy." but I is no way for them to "not use a proxy" what should I doooooooooo

 

[smah]

? I'm not sure that Apache cares if your users are all coming from 1 proxy server, multiple proxy servers, or all directly.

 

[elgrandeperro]

Did you do some basic Apache tuning or are you running the default? Also, turning on server-status is very useful.

gene

 

[jey07ro]

Well I didn't do anything ... because is a reseller acount, and I get this response from tehnical suport after the clients proxy was banned , so now my site is a big failure

 

[NullTerminator]

I agree with Smah. Apache coould care less if your users come from a proxy or not. It just seems that there is more traffic form the prpoxy than else where.

so now my site is a big failure

So find another host!

I have a site (3 actually) at eapps.com. For $20 a month I get a virtual (Linux) server. I have full control of apache and tomcat and access to the OS as root. They have several levels of "power" if you need more memory allocation or bandwidth.

You can run as many domains as you want, as many emails and aliases as you want, MySql, Postgres, etc. and support has been very good.

check it out

http://eapps.com/Docs/VPSStandardPrices.jsp

ps I do not work for them in any way at all. Just happy with their product and service

Jeb Beasley
NullTerminator \0

 

[elgrandeperro]

So most likely it wasn't apache, but their firewall denial of service protection that might have bit you.
gene

 

[GiffordS]

Null....

Maybe you can help me out. I just signed up w/ eapps and am having a problem w/ the apache config.... I think. I ftp'ed my site up to the root user html directory, which is the same directory that housed their "site coming soon" or whatever it was message. Anyway, I deleted their content and added my own into that exact same directory. Now, when I call my url I don't get my site or the default "site coming soon" page. Instead, I get the apache welcome page! I've been busting through apache docs all day and have no idea why it's not finding these files. When I go into my eapps cp and go to the file manager it shows all my content as the files for the site. It's driving me a little crazy. Any thoughts?

 

[smah]

GiffordS, you should probably start a new thread for this matter because it's a seperate issue. When you do, you can confirm if there's an index.html in that directory.

 

[mbrooks]

So let me get this straight. You upgraded to Apache 1.3.34 and now you are having overloading issues?
When you compiled apache did you adjust the HARD_SERVER_LIMIT within the /src/include/httpd.h?

M. Brooks

http://mbrooks.info

 

[NullTerminator]

Email support@eapps.com and check their new user faqs. You'll get the best response to your question faster. My content was under /home/mydomain.com/ROOT

Apache has an welcome page hardcoded into the application so you will never find it in the filesystem.

You will likely get an answer fro eapps within a couple hours.

Carefully read the configuration information that they sent you.

Jeb