Search results

Issue is fixed for us when using newer binaries.

I just saw that the FAQ mentioned suhosin_uploadscan when the real name of the variable is suhosin_php_uploadscan. Let's update this thread with similar items so that the FAQ is updated while we wait to be able to do pull requests on Github ;)

OK, so ./build versions adds empty missing variables at every run. Maybe it should tell the user to run some other command first to update his options.conf? The problem is that on FreeBSD, we have to manually edit options.conf in order for CB to only install what we really want.

OK, I have a problem with the removal of that feature then. Feature #1119 is about both SymLinksIfOwnerMatch and reduced AllowOverride. The patch only takes care of the SymLinksIfOwnerMatch problem. httpd-directories-old.conf should be updated or an option should be given to be able to user the...

Something got forgotten when the template got updated I see this |*if HAVE_PHP1_FPM="1"| RewriteEngine on RewriteOptions InheritBefore <FilesMatch "\.(inc|php|phtml|phps|php|PHP1_RELEASE|)$"> AddHandler "proxy:fcgi://php-fpm|PHP1_RELEASE|.|USER|/" .inc .php .phtml .php|PHP1_RELEASE|...

I got the empty appended duplicates on the version before 910 The only commands I used were ./build update_script ./build update ./build versions and perhaps ./build rewrite_confs

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...

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.