Stash Knowledge Base Home
Popular Articles
Technical Announcements
Important Technical Announcements for Stash
Blog Posts
-
Blog: Stash release announcements
created by
May 07, 2013
-
Blog: Stash 2.4 released
created by
May 07, 2013
-
Blog: Stash 2.3.1 is released
created by
Apr 04, 2013
-
Blog: Stash 2.1.2 released
created by
Feb 11, 2013
-
Blog: Stash 2.1 released
created by
Feb 06, 2013
Click here to see all articles in this space...
- Stash Technical Alerts
- Troubleshooting Git
- Cygwin Git hangs on entering password
- Git command returns "not found" or error code 404
- Git commands return error code 501
- Git commands return error code 503
- Git push returns error code 402
- Git push returns error code 403
- Git Push Fails - fatal: The remote end hung up unexpectedly
- Wrong Git Clone URL When Using Proxy
- Unable to clone Stash Repository with HTTP transport over haproxy using Windows Git clients
- Forking JVM: error=12, Cannot allocate memory or error=12, Not enough space
- Git was not found on the PATH for Stash
- Stash always shows incorrect Merge Conflict in PRs
- Can't access Stash with Git - Issuer certificate is invalid
- Git Commands Return Error Code 400
- Perl validation fails on startup with 'Filename too long' or 'CreateProcess error=267'
- Permission denied on Git config file
- Strange Characters in the Author Column for Commits History
- REMOTE HOST IDENTIFICATION HAS CHANGED when accessing Stash git repo over ssh
- Unable to connect to Stash
- Authentication Fails when Integrating Stash with Github for Windows GUI Client
- User Configured pre-receive or post-receive Hooks Break After Upgrading Stash
- Unable to Push to Stash Repository
- 500 Error Upon Accessing Any Stash Repository
- Pull Requests Not Reflecting Changes Pushed to Remote Branch After an Upgrade
- Git Operations Fail - Permission denied - publickey
- 500 errors when opening a file or the commit list when mailmap is used.
- Repository is not updated by pushing content immediately after its creation
- error: gnutls_handshake() failed: A TLS warning alert has been received.
- Git SSH push timeout on large changes
- Git Push fails with 'receive-pack did not complete' error in the logs
- git upload-archive archiver died with error
- Git push fails - client intended to send too large chunked body
- Detached heads are not currently supported
- Git clone fails with SSL routines:SSL23_GET_SERVER_HELLO
- error: RPC failed result=22 - Push to Stash fails
- Can't clone or pull due to a git outbound proxy
- Error: Unpack Failed: Unpack-objects Abnormal Exit
- Git Push Failed to Write
- Pre-receive hook declined when pushing large number of tags
- This push is too large to process when pushing large amount of data
- Git clone error - could not read Password
- Illegal character in path with Git Submodules
- Git Clone Fails - error: RPC failed; result=56, HTTP code = 200
- SSH not working after Stash upgrade
- Git Commands Return Fatal: Authentication Failed
- error: git-upload-pack died of signal 13
- java.lang.OutOfMemoryError: Unable to Create New Native Thread
- java.io.IOException: The specified network name is no longer available
- Troubleshooting Installation
- 'Address already in use' when Starting up Stash
- After Configuring Stash with SSL, Application Won't Start
- All Repositories Appear Empty After an Upgrade
- A soft-locked cache entry was expired by the underlying Ehcache
- Both old and new directory exist
- Change atlassian.recovery.password when installed as a Windows service
- Change STASH_HOME when installed as a Windows service
- ClassNotFoundException: javax.servlet.ServletContext When Starting Stash WAR in Tomcat 7
- Git 1.7.1 is Not Supported by Stash
- Harmless checkThreadLocalMapForLeaks messages on catalina.out
- How to run Stash over HTTPS with a Personal Information Exchange (PFX) keystore
- Invalid Java location
- java: not found during Stash startup
- LDAP Groups are not being populated with users using FreeIPA
- Login and session conflicts with multiple Atlassian applications
- Manage add-ons - An unexpected error has occurred. Please refer to the logs for more information.
- object directory does not exist - Git operations fail after upgrade or STASH_HOME update
- OpenJDK 64-Bit Server VM is an unsupported JVM
- Push Causes Pre-Receive Hook Declined When Running Windows Server on XenServer
- Sending email fails due to 501 Syntax: HELO hostname error
- SpringMVC dispatcher could not be started
- SSH server fails to start on AWS EC2 instance
- stash.git.notfound error during installation
- Stash as a service and the database as currently configured is not accessible error
- Stash console output: INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found
- Stash Doesn't Start Due to java.lang.UnsatisfiedLinkError
- Stash does not start - After upgrade due to ClassNotFoundException org.apache.catalina.core.JasperListener
- Stash Does Not Start - No fonts found
- Stash does not start - No such file or directory
- Stash failed to Start due to Required plugin failed to start
- Stash fails to start: Perl does not seem to be installed
- Stash fails to start - BASEDIR environment variable is not defined
- Stash fails to start - Missing column
- Stash fails to start on 64-bit Windows with error 'tc-native-1.dll: Can't load IA 32-bit .dll'
- Stash Fails To Start on Windows, Please add git version 1.7.6 or higher to the PATH
- Stash Fails to Start - SEVERE: Error listenerStart
- Stash fails to start - The Spring WebApplicationContext could not be started - Unresolved constraint in bundle
- Stash fails to start - UnsupportedDirectoryOverrideException
- Stash Fails to Startup after installation when Running on OpenJDK
- Stash Fails to Start Up with java.net.UnknownHostException Exception
- Stash fails to start when the current locale is Turkish
- Stash fails to start with org.apache.catalina.core.ContainerBase.startInternal A child container failed during start
- Stash Fails to Start with the Reference to Entity "ABC123" Must End with the ';' Delimiter Error
- Stash hangs right after it starts
- Stash Home [<STASH_HOME>] cannot be created
- Stash Installer fails on Windows 2000
- Stash Install or Upgrade Fails: Error validating Perl
- Stash logo displays localhost
- Stash requires a case-sensitive database, but the target database is case-insensitive.
- Stash service (64-bit) fails to start - not a valid Win32 application
- Stash service installed as "STASH" instead of "Atlassian Stash" and fails with code 4
- Stash Stuck at Empty Repository Screen after Push When Running Windows Server on XenServer
- Stash Upgrade Fails with: tables whose names collide with Stash
- Stash Upgrade Fails with 'Permission Denied' Error
- Stash Upgrade Fails with "Table already exists" Error
- Stash Upgrade Fails with (Permission denied) Exception
- Stash Windows service fails to start - The system cannot open the file
- The database, as currently configured, is not accessible
- The Spring WebApplicationContext could not be started
- Unable to access server on fresh install on Linux
- Unable to access Stash during installation
- Unable to start Stash, with message function: not found
- Upgrading your Stash home directory for Stash 3.2 manually
- White/blank screen after upgrade
- Windows service launches old version after upgrade
- Troubleshooting JIRA Integration
- "There is no application type 'stash' installed." when trying to create an application link
- <REPO_NAME> is already indexing, ignoring second indexing request
- Application Link (Source tab via OAuth) fails in JIRA after Stash upgrade
- Application Link between Stash and JIRA fails due to systems clock not being synchronized
- Application Link fails with No application link found with the id
- Application Link Fails with the string error on a red banner
- Application Stash seems to be offline in JIRA after creating an application link to Stash
- Can't create Application Links. No response was received from the URL you entered
- Can't display issues
- Capabilities Warning Applications with flagged capabilities may be offline or older versions
- CertificateTooOldException when Configuring Trusted Application Link
- Connecting Stash to JIRA for User Management Fails
- Failing to push into repository or managing branch permissions after upgrade
- Git Commits Are Not Linking to JIRA Tickets Due to Corrupted Indexes
- Issues column on Commit tab of repositories does not show link to JIRA issue keys
- JIRA issue Source tab displays No related source found
- JIRA Source Tab Not Working
- OAuth is the only one tab that is displayed for an Application Link
- Oracle exception when creating AppLinks setCharacterStream
- Problem creating an Application Link from JIRA to a HTTPS Stash (or vice-versa)
- Stash does not link commit to JIRA after setting custom JIRA issue key regex
- Stash HTTPS request is redirecting back to HTTP URL during application links creation
- Trusted Application Authentication IPv6 Exception
- Troubleshooting Performance
- Checking the number of established connections on Stash webserver.
- git push fails - Out of memory, malloc failed
- Git push operations extremely slow on Windows
- Potential performance impact of embedded Crowd directory ordering
- RejectedExecutionException
- SSH Fail Intermittently due to upload-pack: Resource temporarily unavailable
- Stash become unresponsive with "Hazelcast instance is not active"
- Stash crashes due to java.lang.OutOfMemoryError PermGen Space Error
- Stash is reaching resource limits
- Troubleshooting Project Management
- Troubleshooting User Management
- <User> cannot be deleted; they belong to a read-only directory.
- Cannot Login to Stash Using External User Account After Moving JIRA/Crowd Server
- Configure Gravatar URLs in Stash
- Could not retrieve SSO Configuration when integrating Stash with Crowd
- Creating new users fails when Delegated LDAP is configured with Stash
- Crowd Synchronization Fails with Integrity Constraint Violation
- Directory server synchronization failed
- LDAP Error Code 32
- LDAP Error Code 49
- SizeLimitExceededException when integrated with LDAP
- SSLHandshakeException - unable to find valid certification path to requested target
- Stash displays 404 j_stash_security_check after User Directory modifications
- Stash throws 500 error when attempting to edit an External User Directory
- Synchronization with LDAP Server Fails with PartialResultException
- Unable to Add Crowd User to Local Stash Group
- Unable to add Global permissions to groups
- Unable to connect to JIRA for authentication - Forbidden 403
- Unable to find the username of the principal
- Unable to login into Stash after turning on Crowd integration
- Unable to sync crowd user directory - query did not return a unique result
- Users can't access Stash due to Google Apps For Crowd plugin in Crowd
- 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
- Troubleshooting Databases
- 500 Error in Stash when selecting Issue Transitions Settings
- A directory exists at the same location when creating repository
- Can't connect to MySQL - You have an error in your SQL syntax
- Cannot connect Stash to MySQL database
- Cannot create SSH keys with a MySQL database after exporting and reimporting via mysqldump
- Cannot Delete a Stash Repository due to missing create temporary table permission
- Cannot Delete a Stash Repository when using Global Transaction ID in MySQL
- Cannot get past license screen during installation
- Clone error - error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
- Connection Timeout with MySQL Database
- Database Deadlocks While Listing Remote Refs
- Database migration failed
- Database migration fails from HSQLDB - Cannot insert the value NULL into column user_name
- Database migration to PostgreSQL fails - Invalid byte sequence for encoding "UTF8": 0x00
- Exception executing SQL update .. java.sql.SQLException: Error writing file (Errcode: 28)
- FATAL: Ident authentication failed for user - Unable to connect to PostgreSQL
- Investigating Stash Database Schema
- MigrationException when migrating to a MySQL database
- mySQL Database Migration fails due to "null" character in Stash table
- ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
- ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
- Password authentication failed with PostgreSQL 9
- Random 500 errors when running Stash - Database connection timeouts
- Restoring backup fail with foreign key contraint
- Stash 2.7 fails to start with MySQL when binary logging is enabled
- Stash can't be started due to the transaction log for database is full
- Stash fails to connect to external database - The target database is not configured for UTF-8 support
- Stash fails to connect to MySQL - The current database MySQL X.X.XX, is unsupported
- Stash Fails to Startup with MySQL 5.6.x
- Stash-JIRA integration is slow after Stash upgrade using Oracle
- Stash server not allowing SSH connections after a database migration
- Stash Upgrade to 2.4.0 Fails with "Specified key was too long" Exception
- Unable to Connect to SQL Server Due to Error: 18456, Severity: 14, State: 12
- Unable to Start Could not get JDBC Connection ClassNotFoundException com.mysql.jdbc.Driver
- Upgrade to Stash 1.3+: Can't create table '<stash_db>.#sql-XXX_XX' (errno: 150)
- Use Integrated Authentication over Kerberos when connecting to MSSQL on Linux
- 'How Do I...' and 'How to...' Guide to Stash
- Configure Stash Logging
- Configuring the Mail Server to Use Gmail
- Connecting to named instances in SQL Server from Stash
- Disable default SSH algorithms
- Enable archive option on git repository
- Enable SQL query logging
- Generate a Thread Dump Externally
- How do I apply the default custom user and group avatars in Stash
- How do I change the default session timeout
- How do I disable Stash's internal authentication and delegate that to an external entity e.g. Kerberos authentication on Apache?
- How do I find which users count against my Stash license?
- How Do I Generate/Extend Stash Evaluation License
- How do I use xinetd to forward port 22 for SSH connections to Stash
- How do you make changes on a specific commit
- How to Alter the Favicon in Stash
- How to configure an outbound HTTP and HTTPS proxy for Stash
- How to configure CAPTCHA in Stash
- How to count the number of files in a repository folder
- How to debug Out of Memory Heap Space
- How to disable delta compression on Stash server for a particular file type
- How to download a repository using Archive for Stash plugin API using command line
- How to Edit the Footer in Stash
- How to enable Google Analytics in Stash
- How to Enable UPM Safe Mode using UPM REST API
- How to find out failed login attempts
- How to read the Stash Log Formats
- How to Redirect Stash Traffic to Port 80 on Linux
- How to restore a deleted branch
- How to serve your Stash repo without using Stash
- How To Troubleshoot Application Link Issue between JIRA and Stash Using AppLinks Diagnostics Plugin
- How to View Detailed permissions for Stash directory
- List ciphers used by JVM
- Log more LDAP query details
- Log the original IP address when Stash is behind a load balancer
- Query for inactive or idle users
- Recommended Action plan if a Repository Becomes Corrupted on a Stash Server
- Redirect HTTP Requests to HTTPS
- Reindex JIRA issue keys
- Restore Stash's Administrator User
- Revert plugin or add-on to an older versions
- Securing Stash (using Tomcat) against Poodle Disabling SSLv3
- Troubleshooting Repositories
- Changed file list missing from commit details after upgrade to version 3
- Changing a branch caused git to "refs/heads/ refs/tags/' exited with code 128 saying: fatal missing object"
- Commit in Stash shows a different username than the one that pushes the code
- Create a fork in a repository or merge branches yields git error code 128
- Troubleshooting fork not syncing
- Troubleshooting Backup Client
- 'ERROR A backup could not be created. Reason: Lexing failed on line: 1..' When creating a backup using the backup client
- Backup client fails due to the error: One or more database connections were not closed within the allotted timeout
- Backup client - Operations from one or more SCMs did not finish within the allotted timeout
- Backup client restore fails due to Out of Memory or GC overhead limit exceeded
- Can't backup due to PKIX path building failed - unable to find valid certification path to requested target
- Could not restore the backup - Attempted reconnect 3 times. Giving up.
- Could not restore the backup to a MySQL database - Reason: The database schema could not be restored.
- No Subject Alternative Names
- Restore does not work - The configured JDBC driver, com.mysql.jdbc.Driver, is not available on the classpath
- Restore fails with FileNotFoundException - Permission denied
- Restore fails with password authentication failed for user
- Stash backup client - 401 Unauthorized
- Stash backup fails - Read timed out
- Stash hits OOME when SBC is backing up sta_shared_lob table
- The backup on the server has become unresponsive and has not progressed in 300 seconds
- The Stash backup directory cannot be located in Stash home
- Troubleshooting Stash Data Center
- JAVA Option '-Dhttp.nonProxyHosts' Does Not Work on Windows OS
- Cannot delete a Stash repository due to 'HT_sta_pr_activity does not exist' error
Learn about Using Confluence as a Knowledge Base
Want to know more about how we built this space? Have a look at the Use Confluence as a Knowledge Base.