Adding a Local Group in JIRA Results in a Connection Error to an External Directory

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When adding a local group you it fails with an error.

The following appears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 2018-0x-xx 17:23:25,318 http-nio-9280-exec-16 ERROR user 1043x8932108x1user 255.252.255.255,127.0.0.1 / secure/admin/user/GroupBrowser!add.jspa [c.a.j.w.a.admin.user.GroupBrowser] Error occurred adding group : new_group_name com.atlassian.crowd.exception.runtime.OperationFailedException: org.springframework.transaction.CannotCre ateTransactionException: Could not create DirContext instance for transaction; nested exception is org.sp ringframework.ldap.CommunicationException: ldap.server.hostname:636; nested exception is j avax.naming.CommunicationException: ldap.server.hostname:636 [Root exception is java.net.S ocketException: Connection reset]

Cause

When adding local groups, JIRA makes sure that said group doesn't exist in external directories first. If there is a connection issue, you won't be able to add that group till it's resolved.

Resolution

Make sure all external directories are accessible through JIRA, please see steps for LDAP troubleshooting, if you're still experiencing problems.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.