Stash sends requests to the domain amazonaws.com
Miscellaneous
- 500 Error Stash and MySQL database
- An error occured is shown every time users see a Pull Request
- an error was encountered while retrieving plugin details
- Application links missing, and log reports an attempt to delete trusted applications configuration
- Bitbucket Server does not send emails after a restart
- Browsing Directory Names with Space Fails with java.net.URISyntaxException Exception
- Cannot clone nor push with http://username@stash:7990/scm
- Cannot run Stash 1.x on Tomcat 7/JDK 7
- Captcha image doesn't render
- Changing Server ID for Stash Cloned Instances
- Commit build status is always red even if other builds succeed
- Configuring syntax highlighting for file extensions
- Could not generate DH keypair on SSL
- Create support zip fails with timeout message
- Creating a Project or Repository Fails With HV000041: Call to TraversableResolver.isReachable() threw an exception
- dispatch_protocol_error: type 100 seq 8 Error When Connecting via SSH
- Enable automatic merging fails with HTTP Status 400
- Errors from trusted application link or Unable to delete application link
- Git hook scripts are not executing
- Highlighting source code does not allow text to be pasted using Middle Click on Linux versions of Firefox
- HipChat limited connectivity in Stash
- HTTP 500 error on certain functions in Stash when using unsupported JDK
- HTTP 500 error when navigating to a file
- Identifying a Repository on the Stash Server
- JohnsonHttpRequestHandlerServlet message in the Stash log
- Mail Server Connection Failed With 'java.net.SocketException: Permission denied: connect.' Exception
- Mail server connection failed with GMail
- Moving Stash to a different context path
- NoDefaultBranchException error regarding the default branch - this branch does not exist
- No subject alternative names - LDAP with SSL
- Nothing displayed on the pull request page
- Notifications fail to be sent when using SubGit SVN Importer
- Permission error on user profile page after adding SSH key
- Plugin incompatibility with Stash 3.0
- PreReceiveHook and PostReceiveHook are not invoked
- Projects disappear on upgrade due to an incompatibility with the Stash Project Categories plugin
- Pull request is too large to render
- Pull Request Won't Merge Changes to Master Branch
- REST API Stuck and Only Returns SSH-2.0-SSHD-CORE-0.9.0-ATLASSIAN-5
- Restoring the Stash Administrator's Password
- Server Unreachable - Timeout when merging or viewing Diff of pull request
- SSH add-on does not load when Stash starts
- SSH Server doesn't start
- Stash Automated Support Request Fails to Lodge a Support Ticket
- Stash connection to non-default ports using TLS1.2 fails with SocketException: Connection reset
- Stash Displays 'There are too many files in this directory. Only showing the first 500.'
- Stash Does Not Start - Could not acquire change log lock
- Stash Does Not Start - Missing column: remote_address_binary
- Stash Does Not Start - Unable to clean the cache directory
- Stash Does Not Start - Wrong column type
- Stash Process Dies Unexpectedly Due to Linux OOM-Killer
- Stash sends requests to the domain amazonaws.com
- Switching branch type in Create Branch screen does not work
- Syntax highlight changes
- The Atlassian Marketplace server is not reachable
- Timestamp Incorrect Due to Java Environment
- Unable to connect to Atlassian Marketplace with UPM
- Unable to delete projects and repositories with application based firewall
- Unable to launch Stash (no Spring WebApplicationContext is available)
- Unable to log in to HipChat from Stash
- Unable to update UPM
- Unable to view commit details
- Unable to view repository - 500 error page
- Updating add-ons by file upload hangs using UPM
- UPM Self-Update fails when updating from UPM 2.7.8 or 2.7.9 to newer versions
- Users can't login to Stash - LDAP response read timed out
- XSRF Security Token Missing
- You don't have permission to access file on this server
- You do not have permission to create a repository within the project
- Your diff is too large to search
On this page
Related content
- No related content found
Symptoms
We keep getting outgoing firewall hits to http://s3-1-w.amazonaws.com/ on the box that was recently upgraded to Stash 3.2.
Cause
According to Stash 3.2 release notes, we now ship Stash with Analytics - which sends those requests.
Resolution
You can opt in to, or out of, data collection at any time. A Stash admin can change the data collection settings by going to Analytics (under 'Settings') in the Stash admin area.
Please refer to Collecting analytics for Stash for more details.
Last modified on Feb 23, 2016
Related content
- No related content found
Powered by Confluence and Scroll Viewport.