Search results

Are you using the port offset feature to have Apache on 79 and LSWS on 80? If so, what port is in the httpd.conf for the newly created site (in the VirtualHost container)? Frank

Just a FYI (have not had time to test yet). The latest version of cPanel let's you specify the http and https ports under "tweak settings". I now have them set to 79 and 442 so the httpd.conf "should" be built properly. Frank

cPanel has replied back to my ticket. They say in a future release you'll be able to specify an alternate port. But for now you can't modify the template and remove the port or change the port. It's simply ignored. Going to have to keep an eye on all domains and add-on's added and manually...

Hold on just a bit. cPanel is taking one more look at it. Frank

ok, Well just as a FYI for other cPanel users this is going to be an issue. Even though you modify the template it still generates the httpd.conf as <virtualHost xx.xx.xx.xx:80>. cPanel has replied that this is working as designed so there is no issue. It's not an issue for cPanel but...

Does the php -v say that it's LSAPI or a CLI version? Frank

I received a reply from cPanel. The templates (and looks like other useful ones) are located in /usr/local/cpanel/src/templates. Looks pretty simple to either hard code the port to 79 or just remove it all together. Frank

Yea, that makes perfect sense. before the latest upcp (the new easyapache) it wrote them like: <VirtualHost 205.234.192.199> now they are <VirtualHost 205.234.192.199:80> I already have a ticket into cPanel to see if that is (hopefully) part of a template that can be modified. If...

I've sent the httpd.conf to support. Frank

Hello, We've upgraded to 3.2.3 and that does not seem to help. We had to remove the :80 before LSWS would recognize it. This is an urgent problem unless we can modify the way that cPanel is building the httpd.conf Frank

Yup. LSWS will simply use 1 core and leave the other one open to do other things like process php etc. Frank

Hello, I can't 100% confirm this yet, but the latest upcp which brought us up to the latest easyapache seems to have broken lsws because it changes how the httpd.conf is written. Before it looked like this: <VirtualHost 205.234.192.199> ServerAlias www.xxx.com ServerAdmin...

It's pretty straight forward once you have the database created. Here is the doc from the WP site: http://codex.wordpress.org/Installing_WordPress It's prob. easier if you just ask questions about any parts that don't make sense. Frank

Yea, it's not quite as much an issue with the 500 errors like suexec as it is with galleries etc. The files are all owned by nobody and then there are issues. BTW, if you guys have fantastico did you have to flip the setting in fantastico to say your suexec or just leave it normal? Frank

medialayer, Are you suggesting that code or have you actually used that on a cPanel server? Thanks, Frank

I'm pretty sure that I've read that they normally lag a few days before release the updates for manual update/download vs. when they show up via the gui interface. Frank

How much does that large of a rule set affect LSWS? Apache (1.x) had a big problem with large rule sets / complex regex and 2.x is better but not that much. Thanks, Frank

Hello, I'm just wondering how people handled switching to LSWS/phpsuexec and cPanel. We've tried it on one small server and run into all sorts of permissions problems (files owned by nobody:nobody). I'm sure we could run find commands and either change the ownership or the permissions but...

Hello, I'm pretty sure that by default the DoS protection is totally silent/not logged. We think our DoS config is causing problems. Is there any way to enable logging for the DoS so we can see when it kicks in? Thank you, Frank

ok, I saw that but I'm still a bit confused. Would I put: ALL,1.2.3.4T To allow all and then make 1.2.3.4 trusted (and unaffected by the throttles)? Frank