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
