Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Crowd Server 3.0.0 displays "web 1.0" GUI, has exceptions in catalina.out in crowd.log directory


A few days ago, my Crowd Server stopped displaying the nice GUI (blue bar across the top with Crowd, Applications, Users, Groups, Directories) and started showing what I call a "Web 1.0" GUI instead and lists things as just hyperlinked text in a bullet point list and says "Welcome to the Crowd administration console".

My JIRA/Confluence/Bitbucket/Bamboo still authenticate correctly for all my users, but there is some things this GUI is not letting me do (I.e. password reset).

I don't know if it is related at all, but in crowd.log directory, the catalina.out file is spamming once/second the following Exception: INFO [com.amazonaws.http.AmazonHttpClient] Unable to execute HTTP request:




at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(

at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(

at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(

at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(

at org.apache.http.impl.client.DefaultRequestDirector.execute(

at org.apache.http.impl.client.AbstractHttpClient.doExecute(

at org.apache.http.impl.client.CloseableHttpClient.execute(

at org.apache.http.impl.client.CloseableHttpClient.execute(

at com.amazonaws.http.AmazonHttpClient.executeHelper(

at com.amazonaws.http.AmazonHttpClient.execute(





at com.atlassian.scheduler.compat.local.LocalOnlyPluginJob.execute(

at com.atlassian.sal.core.scheduling.TimerPluginScheduler$

at java.util.TimerThread.mainLoop(



Over and over and over....


This machine is on a network that has no access to the Internet, never has, and never will.  Why is it trying to connect to Amazon, how do I turn that off, why did it start doing it, and is that the root cause of my "Web 1.0" GUI issue?

2 answers

1 accepted

1 vote
Answer accepted
AnnWorley Atlassian Team Feb 28, 2018

Hi - It looks like you are running into an issue with gzip compression. There is a workaround on this bug report: Tomcat7 produces corrupted gzip response with newest zlib (1.2.11) library

Quoting one of our Crowd developers:

Regarding the connection to, this is how Crowd sends some analytics events that helps us to understand how customers use our products. You may learn more about data we collect here (this is for all of Atlassian products).

Interesting, we did not update any libraries recently on that machine so I wonder why it just started doing it.  Going to try the workaround.

Workaround worked, thank you!

Also apparently my admin *had* updated zlib actually.

Regarding the connection to, it is worth noting that I've been  considering Atlassian's analytics approach for BTF systems remarkable transparent and customer friendly in the past. I've always been asked whether to enable/disable it at configuration time, and the analytics configuration page is easy to understand, including instructive examples of which data is collected, and which fields are anonymized.

Atlassian has recently become slightly more pushy though and now requires administrators to 'Acknowledge changes to the privacy policy', without offering to opt-out of analytics collection right then and there. Regardless, the surrounding explanation is still completely transparent and includes links to the example data and analytics configuration page:

  • View an <example> of the type of data we collect.
  • Once you click to acknowledge the new Privacy Policy, data collection will be enabled unless you <change your settings>, which you may do at any time.

In other words, users now always need to implicitly opt-in to analytics collection first by acknowledging the privacy policy changes, and can then explicitly disable it right afterwards.

Anyway, given your statement that the system "has no access to the Internet, never has, and never will", I suspect that opting out of analytics collection at configuration time slipped through somehow. You can easily disable it as follows:

  • Click administration menu 'Analytics'
  • Set 'Atlassian Analytics' to 'Disabled'

Yes, this network is not legally allowed to touch the Internet, so....


The "web 1.0" GUI did let me get to 'Analytics' and I selected "Disabled" and clicked save, and that gave me a

HTTP Status 405 - HTTP method Post is not supported by this URL.

type Status report

message HTTP method POST is not supported by this URL

description The specified HTTP method is not allowed for the requested resource

Apache Tomcat/7.0.69

Also, I thought by paying for a Crowd license we get support through the usual way we do for all the other licenses we pay for, I guess the 50 user count license is considered "starter" and we do not?  Is there a 50 user one that is not starter, or do we need a higher user count solely to get the usual support?

Fixing the "web 1.0" issue per workaround above, let me also disable the analytic.


Thank you!

AnnWorley Atlassian Team Mar 02, 2018

@Zlatko Kajan It is a little misleading that our article about the starter license support offering is entitled We’re updating our support offering for server starter (10-user) licenses Per the table on this page, 50-user Crowd licenses are starter licenses: Starter Licensing and Pricing

It does look like you need to buy the next license tier to qualify for support through our portal, from We’re updating our support offering for server starter (10-user) licenses:

However, If your team requires full-time Atlassian technical support you can upgrade to the next user tier license. See our how-to documentation for instructions.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events