Hi Glenn,

it seems that self-service has TLS enabled in its profile. Please compare the server settings with your LAM server profile (where you create users). Maybe the domain name of the LDAP server is different or TLS is not enabled there.
Using the same settings should fix it.

The server address "Directory" looks strange. Here should be the domain name of the LDAP server.

Best regards
Roland


Am 18.06.25 um 20:50 schrieb Mallon, Glenn:
Thanks for the reply.  Sorry for the delay in getting back.

Apache log:

[Wed Jun 18 14:35:11.859102 2025] [php:warn] [pid 1354] [client 
128.103.251.195:62080] PHP Warning:  ldap_start_tls(): Unable to start TLS: Can't 
contact LDAP server in /opt/local/www/apache2/html/lib/account.inc on line 774, 
referer: 
http://10.245.34.22/templates/selfService/selfServiceLogin.php?name=Users&scope=user

[Wed Jun 18 14:35:11.859756 2025] [php:error] [pid 1354] [client 
128.103.251.195:62080] PHP Fatal error:  Uncaught TypeError: ldap_get_option(): 
Argument #1 ($ldap) must be of type LDAP\\Connection, null given in 
/opt/local/www/apache2/html/lib/account.inc:1744\nStack trace:\n#0 
/opt/local/www/apache2/html/lib/account.inc(1744): ldap_get_option()\n#1 
/opt/local/www/apache2/html/templates/selfService/selfServiceLogin.php(235): 
getExtendedLDAPErrorMessage()\n#2 {main}\n  thrown in 
/opt/local/www/apache2/html/lib/account.inc on line 1744, referer: 
http://10.245.34.22/templates/selfService/selfServiceLogin.php?name=Users&scope=user

Self service config:

[cid:image001.png@01DBE060.1174EF80]

I copied the config by doing a side by side view of both config pages and 
replicating where it was the same.

I am able to log in and create a user.  Only self service seems to be 
non-functional right now.

Thanks.

~ Glenn

From: Roland Gruber <p...@rolandgruber.de>
Date: Thursday, June 5, 2025 at 2:34 PM
To: Mallon, Glenn <glenn_mal...@harvard.edu>, lam-public@lists.sourceforge.net 
<lam-public@lists.sourceforge.net>
Subject: Re: [Lam-public] Unable to connect to self service.
Hi Glenn,

as you get an error 500, can you check what is logged by Apache's error
log? Please also provide a screenshot of the self-service config (first
tab, server settings).

Do you mean a file copy with "The config was manually copied from the
old server"? As there are more than five years between 6.5 and 9.1
please try to create the self-service config from scratch in 9.1.

Is the LAM admin part (where you can create e.g. users) working for you?

Best regards
Roland


Am 05.06.25 um 18:59 schrieb Mallon, Glenn:
I get the same result.

I’ve imported the cert from the old server now.  In the mainmanage.php I have 
“ldaps://” listed next to the Import from server button.

In the self-service config (selfService/adminMain.php) I have just checked 
“Activate TLS” which results in a 500 server error.  The config was manually 
copied from the old server, but obviously I have done something wrong.

From: Roland Gruber <p...@rolandgruber.de>
Date: Monday, June 2, 2025 at 2:07 PM
To: lam-public@lists.sourceforge.net <lam-public@lists.sourceforge.net>
Subject: Re: [Lam-public] Unable to connect to self service.
Hi Glenn,

did you try these?

ldap://10.245.34.22
ldap://localhost

If your server supports TLS you can activate the checkbox for it in the
server profile. This might require that you import the server
certificate into LAM (same as for ldaps://):

https://www.ldap-account-manager.org/static/doc/manual/ch03.html#idm772

"Can't contact LDAP server" can also mean that the SSL-connection failed.


Best regards
Roland


Am 02.06.25 um 16:00 schrieb Mallon, Glenn:
Thanks for this suggestion.  Changing the port and trying all ldap prefixes 
still returns the same error.
________________________________
From: Stefan Kania <ste...@kania-online.de>
Sent: Tuesday, May 27, 2025 3:22 PM
To: lam-public@lists.sourceforge.net <lam-public@lists.sourceforge.net>
Subject: Re: [Lam-public] Unable to connect to self service.

ldaps is port 636 not 389

Am 27.05.25 um 19:49 schrieb Mallon, Glenn:
I'm moving from 6.5 to 9.1 by way of a new server.  I've managed to solve a 
host of issues, but when I try to log in to self service, I get the following:

Cannot connect to specified LDAP server. Please try again.
Can't contact LDAP server

I have tried various base URLs, both the local ip (ldaps://10.245.34.22:389) 
and localhost (ldaps://localhost:389).  I have also tried ldapi:// ldap:// and 
ldaps:// but am coming up with the same error.

I am binding with the admin account for now.  Is there something obvious I am 
missing?

Harvard University Press <https://www.hup.harvard.edu/>

*Glenn Mallon*
IT Operations Specialist
Harvard University Press
617.496.0286
79 Garden Street | Cambridge, MA 02138-1400
www.hup.harvard.edu<http://www.hup.harvard.edu> <https://www.hup.harvard.edu/>



_______________________________________________
Lam-public mailing list
Lam-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lam-public

--
Stefan Kania
Landweg 13
25693 St. Michaelisdonn






_______________________________________________
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


_______________________________________________
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

Reply via email to