PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-18

Cloudflare Workers VPC: Configure a private CA and mTLS

Cloudflare Workers VPC can now verify a private origin with a custom CA and authenticate to it with a client certificate. Check which your origin requires, then set the certificate references and verification mode on the VPC Service. Submit the full configuration during rotation to keep the certificates you still use.

Cloudflare Workers VPC Private CA mTLS Certificate rotation

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The custom CA lets Workers VPC trust the origin. The client certificate lets the origin authenticate its caller. You can configure either one independently.
  • The settings apply to HTTPS connections from http services and TLS connections from tcp services, including PostgreSQL accessed through Hyperdrive.
  • A certificate reference requires an explicit verification mode. verify_full checks the certificate chain and hostname.
  • A VPC Service update replaces the entire configuration. Include the settings you need to retain when rotating a certificate.

Work out who needs to trust whom

Cloudflare announced the feature on November 18, 2026. If your company's private CA issued the server certificate for an internal API, attach that CA certificate or chain to the VPC Service so it can verify the origin. If the origin also requires a certificate from callers, attach a client certificate as well.

Mutual TLS, or mTLS, authenticates both sides. The caller verifies the origin, and the origin applies its own rules to verify the client. For example, if an internal API uses a server certificate from the company CA and requires its scheduler to present a client certificate, keep both settings.

Which connections use these settings?

For a VPC Service of type http, the settings apply to connections that use https to the origin. For type tcp, they apply to TLS connections, including PostgreSQL connected through Hyperdrive in Cloudflare's example. Plain HTTP does not perform these TLS checks.

Check the actual service type, protocol and hostname before configuring the connection. If you are investigating a certificate error, start with the origin certificate's issuer and covered hostnames. If the origin requires client authentication, check which client certificate or issuing chain it trusts.

How do you upload certificates and keep full verification?

Upload the required certificates to the Cloudflare account and obtain their IDs. Upload the CA certificate or chain for origin verification. For client authentication, upload the client certificate with its matching private key and reference the certificate ID on the VPC Service.

Set the verification mode explicitly when you specify either certificate reference. verify_full checks the chain and the hostname. To keep that mode, check that the origin certificate covers the hostname you actually connect to. Cloudflare does not allow a custom CA with disabled.

Cloudflare lists Wrangler 4.164.0 or later, the Cloudflare API, and Terraform provider 5.29.0 or later as configuration options. Check the tool version used by your deployment before making the change.

Will rotating the client certificate clear the existing CA?

A VPC Service update replaces its entire configuration, including TLS settings. To change the client certificate, upload the replacement first, then submit the full service configuration with both the existing CA ID and verification mode. The update clears any certificate reference or verification mode you omit.

An update with no TLS settings returns the service to verify_full with publicly trusted CAs and Cloudflare Origin CA. Cloudflare says changes can take a few seconds to apply. Afterwards, use an authorized test request to check the handshake and confirm that the settings you wanted to retain are still present.

Sources

Frequently Asked Questions

Do I need a custom CA for an origin with a publicly trusted certificate?

You can keep the default verify_full when its trust store can validate the certificate chain and hostname. If the origin also requires a client certificate, you can configure that independently.

Does the public guide confirm the permissions and charges for my account?

The announcement and configuration guide describe the supported connections and settings. Confirm permissions, plan coverage and costs for your actual account and project.