In most cases, yes, you need to provide instance or server access for standard license renewal of RChilli services—unless you are using an on-premises or Docker-based setup.
When You Do Not Need Instance Access
If you are using cloud-hosted RChilli APIs (the standard SaaS model with REST API calls), license renewal is handled automatically through your:
- User Key
- Subuser ID
-
My Account subscription plan
No server or application access is required—just ensure:
- Your parsing credits or expiration date is updated in My Account
- You are using the correct server region (US, EU, etc.)
When You Do Need to Provide Instance AccessYou may be required to provide server or instance access if:
| Scenario | Why Instance Access Is Required |
| Docker-based or On-Premises Setup | The license is often tied to the MAC address or system fingerprint, so support may need access to rebind or validate it. |
| Custom Build or Private Deployment | Support might need to update license files manually inside your environment. |
| Troubleshooting License Issues | If the API fails to validate the renewed license despite an update, logs and access may be needed. |
In such cases, you should share:
- MAC address of the host (for license binding)
- Temporary access (VPN or shared session) only if requested by the RChilli support team
Best Practice
If you're unsure whether your license requires manual activation or remote access:
- Email support@rchilli.com with:
- Your deployment type (SaaS / Docker / On-Prem)
- Your user key / subuser ID
- Recent plan renewal details
Reference:
Comments
0 comments
Please sign in to leave a comment.