🚀 Feature Request: wrangler dev --remote with SSL for SaaS hostnames

[timkelty]

Describe the solution

I have HTTP routes pointing to a worker, where the route is a custom hostname creating in SSL for SaaS, e.g.:

• my-ssl-for-saas-domain.com/* → my-production-worker
• *.my-ssl-for-saas-domain.com/* → my-production-worker

I'm trying to get wrangler dev --remote working, but the worker needs the hostname of the request set properly to work.

I've tried this:

wrangler dev --remote --env production --host my-ssl-for-saas-domain.com

…but get this error:

✘ [ERROR] Could not find zone for my-ssl-for-saas-domain.com. Make sure the domain is set up to be proxied by Cloudflare.

Is it possible for this to work, or is there another way to achieve this?

[jamesopstad]

Please could you provide a reproduction that includes your Wrangler config file and we'll take a look. Thanks.

[timkelty]

@jamesopstad There really isn't anything to reproduce besides the wrangler command and the CF zone configuration, but sure: https://github.com/timkelty/cloudflare-worker-default

• my-cloudflare-zone.com -> Root Cloudflare Zone
• my-cloudflare-ssl-4-saas-domain.com -> Cloudflare SSL for SaaS custom hostname, in the my-cloudflare-zone.com Cloudflare zone.

This works fine:

wrangler dev --remote --host my-app.my-cloudflare-zone.com

This does not:

wrangler dev --remote --host my-cloudflare-ssl-4-saas-domain.com

It throws this error:

✘ [ERROR] Could not find zone for `my-cloudflare-ssl-4-saas-domain.com`. Make sure the domain is set up to be proxied by Cloudflare.

[petebacondarwin]

Hi @timkelty - thanks for the extra info.

I assume that the Worker can be deployed and its routes work in production?

I expect this PR is related: #4232

[timkelty]

I assume that the Worker can be deployed and its routes work in production?

Yep!

I expect this PR is related: #4232

Probably worth mentioning I don't have any routes in my wrangler config – they're all added dynamically via API as worker routes.

[petebacondarwin]

In case it helps, this is the function that is being called with your host:

workers-sdk/packages/wrangler/src/zones.ts

Lines 143 to 188 in 4d9d9e6

	/**
	* Given something that resembles a host, try to infer a zone id from it.
	*
	* It's hard to get a 'valid' domain from a string, so we don't even try to validate TLDs, etc.
	* For each domain-like part of the host (e.g. w.x.y.z) try to get a zone id for it by
	* lopping off subdomains until we get a hit from the API.
	*/
	async function getZoneIdFromHost(
	from: {
	host: string;
	accountId: string;
	},
	zoneIdCache: ZoneIdCache
	): Promise<string> {
	const hostPieces = from.host.split(".");
	while (hostPieces.length > 1) {
	const cacheKey = `${from.accountId}:${hostPieces.join(".")}`;
	if (!zoneIdCache.has(cacheKey)) {
	zoneIdCache.set(
	cacheKey,
	retryOnAPIFailure(() =>
	fetchListResult<{ id: string }>(
	`/zones`,
	{},
	new URLSearchParams({
	name: hostPieces.join("."),
	"account.id": from.accountId,
	})
	)
	).then((zones) => zones[0]?.id ?? null)
	);
	}
	const cachedZone = await zoneIdCache.get(cacheKey);
	if (cachedZone) {
	return cachedZone;
	}
	hostPieces.shift();
	}
	throw new UserError(
	`Could not find zone for \`${from.host}\`. Make sure the domain is set up to be proxied by Cloudflare.\nFor more details, refer to https://developers.cloudflare.com/workers/configuration/routing/routes/#set-up-a-route`
	);
	}

You can try with

WRANGLER_LOG=debug WRANGLER_LOG_SANITIZE=false wrangler dev --remote --host my-cloudflare-ssl-4-saas-domain.com

to see exactly what API requests are being made and which are failing.

[timkelty]

@petebacondarwin the API call is:

-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/zones?name=my-cloudflare-ssl-4-saas-domain.com&account.id=xxxx

That seems to be unchanged, even if I a route to my wrangler config:

			"routes": [
				{
				  "pattern": "my-cloudflare-ssl-4-saas-domain.com/*",
				  "zone_id": "xxx"
				},

                                 // 🤷‍♂️
				{
				  "pattern": "my-cloudflare-ssl-4-saas-domain.com/*",
				  "zone_name": "my-cloudflare-zone.com"
				},


                                 // 🤷‍♂️
				{
				  "pattern": "my-cloudflare-ssl-4-saas-domain.com",
				  "custom_hostname": true
				}
			],

It's a bit confusing which flavor of zone_id/zone_name/custom_hostname I should be using here, but none of them seem to change what is passed to the api.cloudflare.com/client/v4/zones?name= api call, which seems to be the problem.

FTR - I don't want to have these routes defined in my wrangler config if possible.

Maybe the wrangler dev command should have a --zone arg?