Troubleshooting

Use this page to identify and resolve common issues you might encounter when installing, configuring, or operating the Archive Browser. If the solutions provided below do not resolve your problem, refer to the logging section at the bottom of this page to collect diagnostic data before contacting support.

SSL and Network Connection

• The Browser Shows an SSL Security Warning

  Possible Cause: The Archive Browser uses a built-in self-signed SSL certificate by default.

  Resolution: For development or internal use, you can safely proceed past the warning. For production environments, configure a custom certificate signed by a trusted CA in the configuration file.

• The Application Starts But Cannot Be Reached in the Browser

  Possible Cause: A local firewall blocks the port, another application is already using the configured port, or the application process encountered an error during startup.

  Resolution: Open the port in your network firewall, change the port in archivebrowser.ini, or check the log files in the temp/ directory.

• Port 8443 Is Already in Use

  Possible Cause: Another application or service on the host machine is already bound to port 8443.

  Resolution: Stop the conflicting application, change the port parameter in archivebrowser.ini, or use the PORT environment variable override.

Application and Startup Failures

• Application Fails to Start: "Dev-Mode JAR" Error

  Possible Cause: The executable JAR file was built from source without including the -Pproduction Maven flag.

  Resolution: Rebuild the release directory from source using the correct production profile command: ./mvnw package -Pproduction

• JWT or API Keys Are Rejected After Restart

  Possible Cause: The mandatory jwt_secret value in the archivebrowser.ini file was changed.

  Resolution: Changing this secret instantly invalidates all existing tokens. Set a stable, production-quality secret during initial deployment and do not alter it unless performing a deliberate security rotation.

Data and Indexing Issues

• The Executions Table Is Empty

  Possible Cause: The archive folder path is not configured, the specified path is wrong or inaccessible, the index is still actively building, or the archive folder contains no files.

  Resolution: Verify your directory paths in Settings > General. Check Settings > Status to ensure the file system is accessible and the index builder is running.

• The Index Is Not Updating When New Archive Files Are Added

  Possible Cause: The file system watcher missed the addition of the new files, which can happen on certain network shares.

  Resolution: Navigate to Settings > Status and click the Re-index button to force a full rescan and index rebuild.

LDAP Authentication

• LDAP Users Cannot Log In

  Possible Cause: LDAP mode is not active, the user is missing from the explicit whitelist, the user lacks the required group membership, or connection settings are incorrect.

  Resolution: Ensure mode=ldap is set in the INI file. Verify your user whitelist or admin group configuration. Test the directory connection using the Test Connection button in the Settings.

• LDAP User Search Returns No Results

  Possible Cause: No service account is configured, the bind credentials are incorrect, or the service account lacks read permissions on directory objects.

  Resolution: Configure a valid Bind DN and Bind password in Settings >LDAP and verify the credentials with the Test Service Account button.

Log File Location and Format

The application writes logs to the path configured using the logging parameter in the [GLOBAL] section of the INI file (archivebrowser.ini). By default, it is set to ../temp/archivebrowser_##.log.

To enable more detailed logging for troubleshooting, add the following parameter to the [GLOBAL] section of your INI file and restart the application:

logging.level.com.automic=DEBUG

Note: Remember to remove or comment out this setting after troubleshooting is complete to save disk space.

Contacting Support

If you cannot resolve your issue using this guide, collect the following information before contacting Broadcom Support (https://support.broadcom.com/enterprise-software/product-catalog.html):

• The log file around the time the problem occurred.

• The application version from the About dialog in the user menu.

• The archivebrowser.ini file (with sensitive values like secrets and passwords redacted), see Configuring the Archive Browser.

• A detailed description of the steps to reproduce the problem.