Unable to connect to crowd server URL due to No Transport is available for url.
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Problem
Users are unable to login into Crowd Console, including internal admin.
When trying to login, the following appears in the atlassian-crowd.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
2017-01-19 20:17:59,361 http-bio-8095-exec-23 ERROR [crowd.console.action.Login] Failed to connect to the authentication server, please check your crowd.properties
org.springframework.security.authentication.AuthenticationServiceException: Unable to connect to crowd server URL: 192.168.10.10:8095/crowd/services/SecurityServer; nested exception is:
org.codehaus.xfire.XFireRuntimeException: No Transport is available for url 192.168.10.10:8095/crowd/services/SecurityServer
at com.atlassian.crowd.integration.soap.springsecurity.CrowdAuthenticationProvider.translateException(CrowdAuthenticationProvider.java:301)
at com.atlassian.crowd.integration.soap.springsecurity.CrowdAuthenticationProvider.authenticateUsernamePassword(CrowdAuthenticationProvider.java:164)
at com.atlassian.crowd.integration.soap.springsecurity.CrowdAuthenticationProvider.authenticate(CrowdAuthenticationProvider.java:102)
at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
at com.atlassian.crowd.integration.soap.springsecurity.DynamicProviderManagerImpl.authenticate(DynamicProviderManagerImpl.java:40)
at org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter.attemptAuthentication(UsernamePasswordAuthenticationFilter.java:94)
at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:211)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:110)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:50)
...
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
Caused by: java.rmi.RemoteException: Unable to connect to crowd server URL: 192.168.10.10:8095/crowd/services/SecurityServer; nested exception is:
org.codehaus.xfire.XFireRuntimeException: No Transport is available for url 192.168.10.10:8095/crowd/services/SecurityServer
at com.atlassian.crowd.service.soap.client.SecurityServerClientImpl.getSecurityServer(SecurityServerClientImpl.java:176)
at com.atlassian.crowd.service.soap.client.SecurityServerClientImpl.authenticatePrincipal(SecurityServerClientImpl.java:255)
at com.atlassian.crowd.service.cache.CacheAwareAuthenticationManager.authenticate(CacheAwareAuthenticationManager.java:49)
at com.atlassian.crowd.integration.http.HttpAuthenticatorImpl.verifyAuthentication(HttpAuthenticatorImpl.java:247)
at com.atlassian.crowd.integration.soap.springsecurity.RemoteCrowdAuthenticationProvider.authenticate(RemoteCrowdAuthenticationProvider.java:50)
at com.atlassian.crowd.integration.soap.springsecurity.CrowdAuthenticationProvider.authenticateUsernamePassword(CrowdAuthenticationProvider.java:150)
... 95 more
Caused by: org.codehaus.xfire.XFireRuntimeException: No Transport is available for url 192.168.10.10:8095/crowd/services/SecurityServer
at org.codehaus.xfire.client.XFireProxyFactory.create(XFireProxyFactory.java:61)
at com.atlassian.crowd.service.soap.client.SecurityServerClientImpl.getSecurityServer(SecurityServerClientImpl.java:129)
... 100 moreCause
The Crowd Server URL is incorrectly configured in the crowd.properties file inside <crowd-home-directory>.
1
2
3
4
5
6
7
8
9
session.lastvalidation=session.lastvalidation
session.isauthenticated=session.isauthenticated
application.password=pass
application.name=crowd
session.validationinterval=0
crowd.server.url=192.168.10.10:8095/crowd/services/
http.timeout=30000
session.tokenkey=session.tokenkey
application.login.url=192.168.10.10:8095/crowdResolution
Edit the crowd.properties file and make sure to add the http or https protocol in the crowd.server.url and the application.login.url:
1
2
3
4
5
6
7
8
9
session.lastvalidation=session.lastvalidation
session.isauthenticated=session.isauthenticated
application.password=pass
application.name=crowd
session.validationinterval=0
crowd.server.url=http\://192.168.10.10:8095/crowd/services/
http.timeout=30000
session.tokenkey=session.tokenkey
application.login.url=http\://192.168.10.10:8095/crowdUpdated on April 8, 2025
Was this helpful?
Still need help?
The Atlassian Community is here for you.