Getting Data In

How to resolve Splunk sc4s server communication error with Splunk Cloud?

deepakkushwaha
Observer

Hi Folks,

Getting error while run the # ./hwf-Splunk-Connect-for-Syslog.sh       sc4s script 

curl: (3) Bad URL, colon is first character
SC4S_ENV_CHECK_HEC: Invalid Splunk HEC URL, invalid token, or other HEC connectivity issue index=main. sourcetype=sc4s:fallback
Startup will continue to prevent data loss if this is a transient failure.sc4s error .png

Labels (1)
0 Karma

jaxjohnny2000
Builder
0 Karma

ezzykelly
New Member

Did you get any resolution to why this is happening? I got the same error

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

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