Search results

No, the docroots are different: example.com => /home/user/domains/example.com/public_html example2.com => /home/user/domains/example2.com/public_html

I don't have a server with Apache, so I can't try this. Apache for sure doesn't work in this way.

Hello, there is a bug with parsing .htaccess file. For example on DirectAdmin we have an account with two domains: example.com (main domain) example2.com The .htaccess file from public_html of the first domains (example.com) is being parsed for the second domain example2.com. In previous...

Hello, there is a bug with suExec in version 4.1. On cPanel servers some cgi scripts (e. g. Counters) are storred in /usr/local/cpanel/cgi-sys and are accessible from ScriptAlias /cgi-sys. Prior version 4.1 there were being run with user permissions (suExec). In version 4.1 there are run as nobody.

The suffix php52 would be easier to understand for our clients, because now they will now know that suffix php5 (or php) means version 5.2.x or 5.3.x.

Hello, could you add suexec support for suffix php52? Currently suexec doesn't work for suffix php52. If we set the version 5.3.x as default for suffix "php5" then we will not have any suffix for version 5.2.x. AddType application/x-httpd-php52 .php

Why should we avoid "php52"? If we set the version 5.3.x as default for suffix "php5" then we will not have any suffix for version 5.2.x. Could you add possibility to use also the "php52" suffix?

Hello, is there possible to enable GZIP compression by .htaccess file, when it is turned off in LiteSpeed configuration file? Something opposite to: RewriteRule . - [E=no-gzip:1]

DirectAdmin proxy problem Yes, this will be the reason. The DirectAdmin send a location header: Location http://server_address:2222/ The location header is being changed by the Apache directive: ProxyPassReverse Is there possibility that the header will by also changed by the...

DirectAdmin proxy problem Yes, DirectAdmin run on port 2222. After successful login DirectAdmin redirect to URL with port 2222. The problem is that at Apache proxy evering goes fine and DirectAdmin doesn't redirect to URL with port 2222. We are still waiting for a reaply from DirectAdmin...

Thanks, now every thing works ok.

Hello, I wrote about cPanel proxy, but there is also problem with proxy to DirectAdmin backend. After setup the proxy works, but the problem is after succesful login to DirectAdmin. The site is being redirected to the port 2222. When we remove the port from the URL bar (after login) then we can...

cPanel proxy problem 1. You must enable LSWS proxy to cPanel backend (propably it's deing done by default). 2. Create a new account at WHM. 3. Login to the new account by the proxy (URL cpanel.accout_domain.com) 4. Go to email accounts. 5. Then you will see the described error.

After upgrade to the new cPanel 11.25 (from same days it is stable) I have problem with proxing cPanel backend. When I log to cPanel and then go e.g. to Email Accounts I will see an error with AJAX instead of list of email accounts: AJAX Failure: Attempt 1 of 3. Retrying in 3 seconds...

I had also the same problem. After adding below line to Environment of PHP External App evering goes fine: LSAPI_MAX_PROCESS_TIME=300

No, in "User's home directory Only" problem still occur. The Follow Symbolic Link is set to Yes (tried also set to No). The Check Symbolic Link is set to No. At the same configuration it was/is working in version 4.0.1 and earlier.

The problem still occur for us. We get the "403 Forbidden" error for autoindex at LSWS 4.0.6, 4.0.7 and 4.0.9. The version LSWS 4.0.1 work properly without error.

Answer It takes about 10-20 seconds to finish. I enabled debug logging, but there isn't anything interesting. I see that the whole lsws is restarting, when I try to execute that script. I did a strace: http://host8.xon.pl/strace Maybe the problem is in line: shmctl(1343619094, IPC_RMID...

Answer The owner of /var/log/httpd/domains was root:nobody and permissions were 0710. I changed the owner to apache:nobody and now it works properly. Thank you for help.

Answer Yes, the files are owned by apache:apache.