This message originated from Cribl Community Slack.
Click here to view the original link.
Hi. I created a raw HTTP/S source in Cribl on port 10081. When a .NET client tries pushing JSON data to the endpoint a 403 response is received. It's not an issue with proxies/firewalls and not due to any problems with auth tokens. We aren't having this issue using our other sources in Cribl Cloud. Has anyone run into similar issues and if so, how were they resolved?
Solved
Cribl HTTP/S Source Receiving 403 Response When Pushing JSON Data
Best answer by Brandon McCombs
you can create new inputs in Cloud but can't configure just any port. Ports are available for custom inputs in the range of 20000-20010. If you want to reuse a default port with a custom input (to use a different name, for example) then you can but must disable the default input first that is using that port.
Did you commit and deploy?
The RAW HTTP source will accept literally any HTTP data. There are not checks or verifications.
you can create new inputs in Cloud but can't configure just any port. Ports are available for custom inputs in the range of 20000-20010. If you want to reuse a default port with a custom input (to use a different name, for example) then you can but must disable the default input first that is using that port.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.