Common issues with Upsource
This document lists common issues that Upsource users and administrators face, and suggests solutions.
| Issue | Cause | Solution |
|---|---|---|
| You forgot your administrator password. | Reset your administrator account password. | |
| Upsource fails to start. | External (standalone) Hub is not yet initialized. |
|
| Code insight in Maven or Gradle based project is not working. The code analysis status indicator remains grey. | Code intelligence is disabled or not properly configured. | Enable/edit code intelligence settings. If it doesn't help, get mvn.out (gradle.out) file and contact support. |
| Upsource services consume all memory. | OutOfMemory exception. | Increase heap size available to Upsource frontend process. |
| New commits are not getting indexed. | ||
| Revisions are stuck in "indexing in progress" state. | ||
| Web UI is extremely slow. | ||
| Cassandra database won't start when Upsource launched. | Not enough memory for Cassandra database. | Increase heap size available to Cassandra process. |
| Slow Cassandra performance. | Insufficient memory lock settings. | Increase memory lock limit. |
| Web UI never finishes loading. | When using IIS reverse proxy, a WebSocket connection is established but no packets are sent or received. | Disable WebSocket compression. |
| Blurry fonts in some parts of the UI (Chrome browser). | Disable Chrome hardware acceleration. |