Troubleshooting

My RIPS scan does not start

If RIPS is not able to start a scan an error message is returned to indicate what went wrong. Use the following list to match errors to their possible causes and resolutions.

  • "Application quota is expired."
    • The quota that was used to create the application is expired.
    • To resolve this issue update the quota of the application to an active one.
  • "No quota available."
    • No active quota was found with free scans.
    • Make sure that the lines of code (LOC) do not exceed the maximum number of lines.
    • To resolve this issue purchase new scan quotas or wait for future quotas to become active.
  • "No access to quota."
    • The user that tries to start the scan does not have access to the quota.
    • To resolve this issue create an ACL entry for the quota and grant USE access to the user.
  • "The quota is not active."
    • The selected quota has not started yet or is already finished.
    • To resolve this issue purchase new scan quotas or wait for future quotas to become active.
  • "No scans left in quota."
    • The selected quota is exceeded.
    • To resolve this issue purchase new scan quotas or wait for future quotas to become active.
  • "Too many lines of code (x/y)."
    • The selected quota is valid for y lines of code but the selected path or upload has x lines of code.
    • To resolve this issue either reduce the lines of code or purchase a license for more lines of code.
  • "You can not use the path in the cloud."
    • It is not possible to specify a path in the SaaS version.
    • To resolve this issue upload a source code archive and reference the upload id instead.
  • "You can not set path and upload at the same time."
    • Path and upload are exclusive, so it is not possible to specify both.
    • To resolve this issue either remove "path" or "upload" from the request.
  • "You have to set path or upload."
    • Neither a path nor an upload were specified.
    • To resolve this issue set "upload" in the SaaS version, and "upload" or "path" in the On-Premises version.
  • "The upload is already consumed."
    • The upload is used by a different scan that is not finished yet.
    • To resolve this issue upload a new source code archive and use the new upload instead.
    • To prevent uploads from being consumed set "uploadRemoved" to "true" when starting a new scan.
  • "Upload is from different application."
    • The upload does not belong to the current application and can not be selected for security reasons.
  • "No access to custom."
    • The selected custom profile is from a different application and can not be selected for security reasons.
    • To resolve this issue make sure to specify the correct custom profile id.
  • "Source code archive is corrupted."
    • There is an error when opening the archive.
    • To resolve this issue make sure that your archive is not corrupted. A reupload may be necessary.
  • "Source code path is not readable."
  • "The given path does not exist."
    • The given path was not found on the system.
    • To resolve this issue make sure that you have placed the source code in the correct directory (/var/rips2/src by default) and that you use the internal location when starting a scan (/src).
  • "The given path is not accessible."
    • The given path was not found on the system.
    • To resolve this issue make sure that you have placed the source code in the correct directory (/var/rips2/src by default) and that you use the internal location when starting a scan (/src).
  • "The given path is outside of the source directory."
    • For security reasons it is not possible to scan a directory outside of the internal source code directory (/src).
  • "You can not scan the base directory."
    • It is not possible to set the path to the root of the internal source code directory (/src).
    • To resolve this issue create a sub directory in the internal source code directory and scan the sub directory instead.
  • "The given path is not readable."
  • "There are no PHP files in the target."
    • No PHP files were found in the path or upload, thus the scan does not start.
    • This safety check tries to prevent users from scanning the wrong directory.
  • "Parent scan is from different application."
    • The given parent scan is from a different application.
    • To resolve this issue make sure that you specify a correct parent.
  • "No scans available."
    • The application was already scanned but no scans are found.
    • It is not possible to resolve this issue. Contact the customer support.
  • "Code from parent is too different."
    • The code changes in the new scan compared to the parent scan exceed the threshold.
    • To resolve this issue scan your code more frequently, to minimize the amount of changes between scans.
    • If this is not possible for you please contact the customer support.
  • "No license key found."
    • No license key is available.
    • To resolve this issue request a new license key from the customer support.
  • "Your license key is invalid."
    • A license key is available but it can not be decoded.
    • To resolve this issue request a new license key from the customer support.
  • "Your license key is expired."
    • A license key is available but it is expired.
    • To resolve this issue request a new license key from the customer support.

My RIPS scan does not finish

  • Please ensure your machine is equipped with enough memory.
  • Try to reduce the analysis depth in the advanced scan settings.

My RIPS user interface is not reachable

  1. Please ensure that Docker and the RIPS Docker containers are running (systemctl status docker).
  2. Please check if you are using the correct HTTP port and bind address (docker ps). You will not be able to reach the port from a different system if you bind the UI or API port to localhost unless you are using a reverse proxy to forward connections.

My RIPS update fails

  • Please try to run the update command as root user (for example, sudo).
  • Please ensure that your machine is connected to the Internet (ping docker.ripstech.com).

RIPS user interface connectivity issues

If RIPS is not able to connect to the server it will display a warning while waiting for the connection to be restored.

You can also click here to get help about how to restore the connection.

Clear browser cache

Sometimes, after updating RIPS to a new version, it is necessary to reset your browser cache.



For all other or remaining issues, please contact our support at bugs.ripstech.com.