Troubleshoot ACS error messages

The table lists common ACS API error messages and suggested troubleshooting steps you can take to investigate and resolve these issues.

Feature	Error message	Troubleshooting steps
All ACS endpoints	403-forbidden: operation not supported for splunk stack, please refer to the API documentation for limitations and more detail	Check ACS feature compatibility with your Splunk Cloud Platform deployment Experience. See ACS compatibility matrix.
	403-forbidden: operation not supported for splunk version, please refer to the API documentation for limitations and more detail	Check ACS feature compatibility with your Splunk Cloud Platform deployment version. See ACS compatibility matrix.
	404-stack-not-found	Make sure stack name is correct. Each Splunk Cloud Platform deployment is identified by the stack-name, which is the prefix of the deployment's URL. For example, if your deployment's URL is "https://my-company-name.splunkcloud.com" the stack-name is "my-company-name".
	500-internal-server-error	Check if stack has a search head. ACS does not work on a single instance.
	401-unauthorized: call not properly authenticated	Possible causes: JWT token has expired or is not valid yet. Check the Expires On and Not Before token fields. If token has expired, create a new valid token and try again. Make sure to specify the JWT token value and not the token-id value in the Auth header.
	401-unauthorized","message":"failed to parse token	Possible causes: Incomplete or invalid JWT token specified in Auth header. Make sure to specify the JWT token value and not the token-id value in the Auth header.
	409-object-already-exists	An object with the same name already exists. To update the object, use PATCH or PUT based on the specific ACS API feature.
Configure IP allow lists	400-bad-request cannot remove all access to stack's <feature>	This check prevents users from removing all subnets for a certain feature. It ensures there's at least one subnet, preventing users from cutting off all access to their stack for ingestion.
	400-bad-request missing access feature parameter	You must specify the {feature} parameter with the ACS request, for example search-api, hec,s2s, and so on. For more information, see Determine IP allow list use case.
	400-bad-request subnet overlaps splunk's reserved IP blocks	Refer to Splunk Cloud Platform's reserved IP block: "54.147.174.149/32" "3.210.45.80/32" "50.19.33.107/32" "18.208.12.214/32" "35.168.6.234/32" "54.227.109.89/32"
	400-bad-request cannot delete splunk's reserved subnet
Configure outbound ports	400-bad-request invalid port number provided. Please retry with a port number within range 1-65535	Determine correct port number and try again with a port number between 1-65535.
Manage HTTP Event Collector (HEC) tokens	404-hec-not-found	If returned by GET request after creating new hec-token, token creation is still in progress. It might take a few minutes for hec-token creation process to complete. Repeat GET request until status code is 200.
Manage indexes	403-forbidden internal index names cannot be used	Refer to list of internal indexes: "Main" "History" "Splunklogger" "Summary" "lastchanceindex"
	403-forbidden internal index names cannot be deleted
	400-bad-request internal index names are not allowed for defaultIndex
	404-index-not-found	If returned by GET request after creating new index, index creation is still in progress. It might take a few minutes for the index creation process to complete. Repeat GET request until status code is 200.
Manage private apps	400-bad-request This app has failed AppInspect validation	Possible causes: Appinspect validation failures. Verify the failure count in the Appinspect report. Incorrect Appinspect tags. Make sure to specify the correct tags, as follows: For Victoria Experience: Version 8.2.2111 and lower, correct tags are 'included_tags="cloud,self-service"'. Version 8.2.2112-8.2203, correct tag is 'included_tags="private_app"'. Version 9.0.2205 and higher, no tag required when sending POST request to app/validate endpoint. But make sure to specify query parameter ?included_tag=private_victoria, when sending GET requests to the app/validate/status/{request_id} and app/report/{request_id} endpoints. See Validate your private app (Victoria Experience). For Classic Experience: Version 8.2.2203 and lower, the correct tag is 'included_tags="private_app"'. Version 9.0.2205 and higher, no tag required when sending POST requests to app/validate endpoint. But make sure to specify query parameter ?included_tag=private_classic, when sending GET requests to the app/validate/status/{request_id} and app/report/{request_id} endpoints. See Validate your private app (Classic Experience). Splunk Cloud Platform versions prior to 8.2.2111 might have manual checks failing Appinspect validation. Check if the user doesn't override value of private_app_vetting_global in server.conf Make sure the App-inspect token is not expired. It expires in about ~1 day. Try with a fresh token. If using Github private-app-demo or ACS CLI, Victoria stack must be on version 8.2.2112 or highger.
	400-bad-request "message":"AppUpload_InspectValidation: Unable to retrieve AppInspect validation result. Try again later.	Possible causes: Incorrect Appinspect tags. Make sure to specify the correct tags, as follows: For Victoria Experience: Version 8.2.2111 and lower, correct tags are 'included_tags="cloud,self-service"' Version 8.2.2112-8.2203, correct tag is 'included_tags="private_app"'. Version 9.0.2205 and higher, no tag required when sending POST request to app/validate endpoint. But make sure to specify query parameter ?included_tag=private_victoria, when sending GET requests to the app/validate/status/{request_id} and app/report/{request_id} endpoints. See Validate your private app (Victoria Experience). For Classic Experience: Version 8.2.2203 and lower, the correct tag is 'included_tags="private_app"'. Version 9.0.2205 and higher, no tag required when sending POST request to app/validate endpoint. But make sure to specify query parameter ?included_tag=private_classic, when sending GET requests to the app/validate/status/{request_id} and app/report/{request_id} endpoints. See Validate your private app (Classic Experience).
	400-bad-request Extract app information from the package failed	Possible causes: Occurs when you file is not added to the app package or you specify an incorrect path. Make sure to specify a valid app installation package. Invalid app-package file format. App package format must be .tgz, .tar.gz, .spl or .tar file.
Web Application Firewall (WAF) related errors	403-forbidden	A 403 response with awselb in response header indicates the request was blocked by WAF. Possible fixes: For private apps: Make sure to specify the complete file path, for example /Users/<username>/downloads/app.tgz without ../../ in the path. Try to untar and tar the file again. For example tar -xvf {app_file}.tgz and COPYFILE_DISABLE=1 tar cvf {app_file}.tgz {app_file}. Make sure to specify User Agent Header. Check Rate limit. How many requests are you sending? Is it greater than 100 reqs/ 5 min? Send request again on different machine and network. If still blocked, contact Splunk Support for assistance.

For further assistance with ACS errors, contact Splunk Support.