Hi Joe,
the ldap-account-manager.conf installs a global alias in Apache. This
should be valid for all virtual hosts.
What package type did you install (DEB, RPM, tar.bz2)?
If you get an error 500 there should be some more details in Apache's
error logs.
Best regards
Roland
Am 15.04.21 um 02:34 schrieb Joe Gullo:
I have a web server with a bunch of my web apps on it. It runs apache, but
doesn't really have a default site (it has a *:80 with an index.html with
<html></html> and that's it). It has 2 main virtual hosts which listen on
names (home.domain.tld:80, home.domain.tld:443, app.domain.tld:80,
app.domain.tld:443). Each is in a sites-available conf file
When I install lam, everything looks fine, I edit the conf file, but when I
navigate to http://<IP>/lam I just get either a 404, or a 500. I have
tried putting a lam folder in my document root, but it doesn't seem to
work. I think what's happening is one of my virtualhosts is intercepting
the conf? That, or the /lam directive in the ldap-account-manager.conf is
being treated as a subdirectory of one of my virtualhosts, instead of the
default *:80 site?
I'm wondering if someone has a prototype apache configuration that works in
a similar setup for me to reference.
Joe Gullo
Sysadmin, Web Designer, Artist
http://www.surfrock66.com
surfroc...@surfrock66.com
(714)926-0336
_______________________________________________
Lam-public mailing list
Lam-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
Lam-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lam-public
