Why RChilli parser is not working in the cloud environment ?

If your RChilli parser is not working in the cloud environment, here’s a detailed checklist to help you troubleshoot and resolve the issue:

✅ 1. Verify API Credentials and Endpoint Configuration

Ensure that your parser request contains valid and active:

• User Key

• SubUser ID

• Version (e.g., 8.0.0)

• Correct API Endpoint

  • For binary data: https://rest.rchilli.com/RChilliParser/Rchilli/parseResumeBinary

  • For public URLs: https://rest.rchilli.com/RChilliParser/Rchilli/parseResume

📌 Reference Example:

💡 Make sure there's no space in the subuserid field.

✅ 2. Check for Expired API Key or Credits

Your API key might have expired due to:

• All parsing credits being used

• Parsing plan expiry

📌 How to check:

• Log in to My Account

• Check the Parsing Pending Credits and Parsing Expiring Date

• If expired, update your plan under My Plans or contact support@rchilli.com to refresh your key.

✅ 3. Server Configuration & Region Selection

If you are working in the cloud and experiencing latency or connection issues:

• Make sure you've selected the correct server region (US, EU, SG)

• Check whether the server location supports your parser product

📌 You can select or update your server in:

• The Sign Up flow

• The My Account portal under Choose Multiple Servers

✅ 4. Docker or Local Server Setup

If you're deploying in a cloud server via Docker, validate:

• Your cloud server meets the minimum requirements

  • 64-bit Linux, 64 GB RAM, 16 cores, 100 GB storage

• The Docker container is running correctly

• You are using the correct service URL

If unsure, contact support@rchilli.com for guided Docker installation.

✅ 5. Common Cloud Misconfigurations

• CORS Issues: Ensure your cloud service allows cross-origin requests if you’re making frontend API calls.

• Firewall or Network Security: Your cloud environment may be blocking external HTTP/S traffic.

• Wrong Service URL: Check if the API call is hitting the right RChilli endpoint from your cloud setup.

✅ 6. Use Postman or cURL to Isolate the Problem

Try testing the API from Postman or a simple cURL request to confirm if the issue lies with:

• Your cloud setup

• Or the RChilli API/key itself

If it works from Postman, then the problem is within your cloud app (e.g., security groups, API headers, etc.).

🔁 Still Not Working?

If the issue persists:

1. Collect the error message or failed response from the API call.

2. Share:

   • Your API request payload (excluding sensitive data)

   • API endpoint used

   • Screenshot of the error (if any)

3. Email to: support@rchilli.com for direct assistance.