Troubleshooting Cloudflare Integration 404 errors

Common Cause #1: Proxy Mode Disabled

The most common cause of 404 errors when using the Fingerprint Cloudflare Integration is having Cloudflare Proxy Mode disabled for the domain in question. The Fingerprint Cloudflare Integration utilizes Cloudflare Workers, and as such requires the domain be proxied through Cloudflare.

To resolve this issue, please follow these steps:

1. Log in to your Cloudflare dashboard.
2. Select the domain associated with your Fingerprint Cloudflare Integration.
3. On the left hand side, select DNS
4. From here, you can look at the 'Proxy Status' column to determine if the domain in question is being proxied through Cloudflare. If the status is 'DNS Only' please click the blue 'Edit' button and then toggle the 'Proxy Status' slider to 'Proxied'

After these steps have been completed, please test your integration. If the 404 error persists please see the next section of this troubleshooting guide.

Common Cause #2: Worker Route Deleted

The second most common cause of 404 errors is the deletion of the worker route. For the Fingerprint Cloudflare Integration to be available on an endpoint there must a Worker Route setup for it.

To resolve this issue, please follow these steps:

1. Log in to your Cloudflare dashboard.
2. Select the domain associated with your Fingerprint Cloudflare Integration.
3. On the left hand side, select ‘Worker Routes’, then ‘Add Route’
4. In the ‘Add Route’ window, enter the route in the following format: example.com/<worker path>/*. You can find the worker path by looking at the URL giving you the 404 error and copying the string of characters immediately after the domain. If you have any trouble finding your worker out please reach out to Fingerprint support for assistance.
5. Select the Fingerprint Cloudflare Integration worker from the drop down menu, then click ‘Save’.

The worker route should now be properly configured, go ahead and test your integration. If the 404 error persists after following both sections of this guide please reach out to Fingerprint support.