No, the installer and the apache2 packages are identical. If it had a problem with the GPL installer, it’ll have the same problem with the Pro installer.
I’m working on reproducing the problem here, and will hopefully figure out why apt won’t let us replace the default apache package soon.
I tried changing the default website template by selecting not to add suexec, but it won’t save. It gives an error “Failed to save server template : Missing or invalid Apache user”
Unfortunatly I have tried installing the GPL version on a debian 4 clean server as well 2 times, ( I had to have my provider reimage the server 2 times with a clean debian 4 install ).
Both times it does not seem to pick up the APT replacement packages from virtualmin, causing numerous errors, not just in apache.
The install script does not give any error otherwise, it simply installs the wrong packages (debian equivilants) as far as I can see.
Since I generally I only want to use Debian, it would be very helpfull this will get fixed asap. I’m also considering of buying the Pro version, but I want a good few months of a stable working version first. And unfortunatly, most options do not work presumably due to the wrong packages installation.
apache2 references to mpm dependancies of version *-50, however there is no reference to this version in the packages file, nor does debian itself offer this version.
Presumably this is the customized version that needs to be installed, without a reference it seems the debian version gets installed instead. And apache2 itself is a virtual package.
This is only the preliminary problem I see, there may be a lot more problems why the packages dont get installed correctly.
Perhaps I am overlooking something, I tried the following in /etc/apt/preferences:
Package: *
Pin: origin software.virtualmin.com
Pin-Priority: 1001
and although this does apperently influence the priority, it still wont correctly install apache due to a dependancy problem.
I cannot make my CGI perl scripts to work, now following twhat is in this thread i changed ownership of the script to www-data and removed on the webserver the option to run scripts as owner. the script works as long as is inthe cgi-bin directory.
the suexec2 ETC did gave any results…
and if i understood well i should preffer that option over the www-data thing for securityreasons.
Also i would like to have the scripts running outside the cgi-bin folder i.e: in a folder under public_html as it is for a proxy im setting…
Just so I know the state of your system – did you by chance install with the install.sh script?
the script works as long as is inthe cgi-bin directory.
Okay, that’s a good start.
and if i understood well i should preffer that option over the www-data thing for securityreasons.
Yeah, suexec provide a nice security benefit since it can run as the individual Virtual Server owner, rather than the generic www-data user.
If you’re having trouble getting it to work, let us know what you’re trying, and what error you’re getting (be sure to take a peek in the Apache error_log for that domain in $HOME/logs/error_log).
i would like to have the scripts running outside the cgi-bin folder i.e: in a folder under public_html as it is for a proxy im setting...
Sure, you can do that by adding "ExecCGI" to the Options line.
To add it to an existing site, you can manually edit the VirtualHost section for that domain in /etc/apache2/sites-enabled.
For new domains, you can go into System Settings -> Server Templates -> Default -> Apache Website, and update the section at the top named "Directives and settings for new websites". Any new Virtual Server will get your updated configuration.
-Eric
That’s it… so no reference to the home thing in the previous posts…
I looked at the error log in the folder you told me, it points to another folder in /var/logs/tld.log
I could not find any error related to the execution of the script execpt for once i made a typo in the address
I guess i could instead of chopping the cgi-bin part that will allow scripts to be run everywhere just add another line public_html/folderiwantmyscript2b ??