Search results

Ah, I think I understand what you mean now... This feature http://www.directadmin.com/features.php?id=1119 has been dropped and you're only using httpd-directories-old.conf... Correct?

I expected the symlink to go to httpd-directories-new.conf, but it was created to httpd-directories-old.conf despite the fact that I have harden_symlinks_patch=yes in my config. So, it still sounds like a bug to me.

Never modify /etc/httpd/conf/extra/httpd-directories.conf! Refer to this post for a safe way to allow sync clients to connect via DA's custom HTTP config. http://forum.directadmin.com/showthread.php?t=46115&p=247488#post247488

This is still an issue in 1.454. We don't want to use SHA if we don't have to, but can't remove it because some users are still on TLS 1.0

That's what we use and is the best option for people looking at sending backups to S3. No need to include S3 in the backup routine itself. What would be great though is to allow users to use duplicity from the CP. Perfect way to make safe backups to a remote location. A simple HTML page would...

The webmail edition comes with a filter management app which takes care of forwards, vacation messages, spam and custom filtering. Everything is stored in sieve files, so it can be edited in other email clients. Regarding import/export of user data, I couldn't find anything. Cpanel used to have...

OK, I've just checked and settings are correct, so I'll contact you to try and figure it out.

1) Yep, I see tons of these 2014:08:04-07:35:51: Apache::apache_equal_or_newer: Apache version is not loaded: 0.0.0 2) But according to your instrucions, the httpd binary doesn't seem to be the issue # su -m nobody -c '/usr/sbin/httpd -v' Server version: Apache/2.4.10 (Unix) Server built: Aug...

But how do you get the Apache version? I'm wondering if the detection breaks when hosts are using "ServerTokens Prod"

I think that if I do that, then CB will try to install it. Maybe ./build versions should simply ignore all apps and libs which are set to no.

Commits list, issues tracker, pull requests make things so much easier, even the documentation could be worked on by several parties.

The new solution works much better, thanks :)

True, I guess you can't patch every Apache hole unless it's needed in the templates :D. (For people still using it for custom configs, you'll also need the patch to allow long proxy names)

Yep, that was a nice surprise :), but still the webapps.list parsing doesn't work and it cannot be used to build httpd-alias.conf

Just migrated to 2.4.10 and have noticed that this patch has still not been integrated Persistent backend connections for ProxyPassMatch The good news is that it should be in the next version of Apache.

I have this in options.conf secure_htaccess=yes When running ./build rewrite_confs the wrong symlink was created in /etc/httpd/conf/extra/ CB linked httpd-phpmodules-old.conf instead of httpd-phpmodules-new.conf

Much better :) There is still one bug Since the installed version is higher than what is offered, CB should just ignore it unless there are known issues with using a higher build on the platform on which the script is run.

I've just tried using CB 2.0.0-RC7 (rev: 910) and it did not work at all webapps.list webmail=/var/www/html/webmail myadmin=/var/www/html/myadmin Microsoft-Server-ActiveSync=/var/www/html/webmail/rpc.php autodiscover/autodiscover.xml=/var/www/html/webmail/rpc.php...

I've just upgraded a server to Apache 2.4.10 and after a rewrite_confs all PHP settings were wiped out from the httpd.conf files. We're using custom virtualhost templates which only include |*if HAVE_PHP1_FPM="1"| but apparently that doesn't work, DA is still looking for |*if...

Yes, the idea is to have one colour per option. It's either red (disabled) or green (enabled), depending on what's been selected. There is no need to paint every PHP version or pureftpd red simply because they're not in use. The option in use is already standing out in bright green.