Getting Data In

Http Collector Cloud Trial - 406 Not Acceptable

ee_admin
New Member

Hello,

I'm trying out the Splunk Http Event Collector but not able to make a request!

curl "https://myinstance123.cloud.splunk.com/services/collector" \
  -X POST \
  -d "{\"_json\":\"hello world\"}" \
  -H "Authorization: Splunk myToken" 

I'm getting this

<html>
<head><title>406 Not Acceptable</title></head>
<body bgcolor="white">
<center><h1>406 Not Acceptable</h1></center>
<hr><center>nginx/1.14.1</center>
</body>
</html>

I really need to test this not sure what to do. I can't disable the SSL from global setting as mentioned in docs. I also tried with 8088 port but not working.

Tags (1)
0 Karma

ee_admin
New Member

Note: before someone ask me to try with -k see the below result

C:\Users\ee_admin>curl -k https://myinstance123.cloud.splunk.com/services/collector -H 'Authorization: Splunk myToken' -d '{"event":"hello new event"}'
<html>
<head><title>406 Not Acceptable</title></head>
<body bgcolor="white">
<center><h1>406 Not Acceptable</h1></center>
<hr><center>nginx/1.14.1</center>
</body>
</html>
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...