Identify the Chat4U website importer
Understand the Chat4U crawler identity, private access tokens and available access methods.
3 min read
- Project
- Knowledge
- Website access
Open the affected website source in Knowledge. Review its request details, save the access method your administrator configured, and test access before retrying the import.
Use the access method shown by your website source and supported by your provider. This page explains what your administrator should match.
- Finish with
- The correct identifier or credential method for your exception
Named crawler exception
The importer sends a User-Agent beginning Chat4UBot/. Match that stable prefix when your provider supports it, within the hostname and paths you intend to import. The complete header is:
User-Agent: Chat4UBot/1.0 (+https://chat4u.ai/docs/knowledge/chat4u-crawler)A User-Agent is a public request label that anyone can copy. It does not prove a request came from Chat4U. Changing the name alone does not create a firewall exception. Follow the matching Cloudflare or AWS WAF procedure after finding the responsible protection.
Website access token
For a Custom header rule, arrange a dedicated private value with your administrator. Configure that same value in the provider's rule and the source's custom-token field. The configured header is X-Chat4U-Import-Token; the website must actually check its value. An arbitrary token does not authenticate an ordinary website account.
For Vercel, select Vercel automation bypass and follow the Vercel setup. Its header is x-vercel-protection-bypass and its token comes from the correct Vercel project.
Chat4U sends a token only to the configured secure origin and permitted paths. Keep it out of shared instructions and URLs. After replacing/removing a token, test the current settings again.
Verified crawler addresses
Find the current addresses in Project → Knowledge → your website source → Website access settings (or Resolve website access). Under Access method, select Allow verified importer IP addresses, then Copy IP addresses and share it with your website administrator. Use this method only when the source displays a verified current list; if unavailable, use a supported token/name exception or direct content.
Copy the exact addresses displayed by Chat4U to your administrator. Allow each exact IPv4 address (or its /32 equivalent), rather than an entire cloud-provider range. Where supported, also match Chat4UBot/, the selected hostname and necessary public content paths. Test access after saving the rule.
If an address changes, copy the current list from the source settings, replace the old exact address in your website rule and test again. Do not substitute temporary worker/task addresses. If your source marks this method unavailable, use another supported method while Chat4U restores the verified route.
Permission and content scope
Your authority confirmation permits importing inside Chat4U; it does not update your hosting controls. Domain verification and a robots.txt edit do not themselves open a firewall. Configure access for the intended content, then inspect the completed import. Removing an exception stops future website requests; deleting imported knowledge is a separate action.
Last updated on