Why Was My Custom Name Rejected?

When you set a custom name for your content URL, Connect Cloud validates it before saving. This page explains each reason a custom name can be rejected and what to do.

The name contains invalid characters

A custom name may only contain letters (A–Z, a–z), digits (0–9), and hyphens. It cannot end with a hyphen.

If your name contains spaces, underscores, dots, or any other character, update it to use only letters, digits, and hyphens.

The name is too long

The limit depends on whether you are using the default sharing domain or a wildcard custom domain.

Default sharing domain

When you are not using a custom domain, Connect Cloud constructs your URL by joining your account name and the custom name with a hyphen:

https://[account-name]-[custom-name].share.connect.posit.cloud

Before checking the length, Connect Cloud lowercases the combined string and converts any underscores in the account name to hyphens. The combined portion — account name, hyphen, and custom name — must be 63 characters or fewer after that conversion.

If your account name is long, the budget left for the custom name is smaller. For example, an account named my-long-organization-name (25 characters) leaves room for at most 37 characters in the custom name.

To fix it, choose a shorter custom name.

Wildcard custom domain

When you are using a wildcard custom domain, the custom name becomes a subdomain of your domain (for example, client1.mydomain.com). In that case, the custom name alone must be 63 characters or fewer.

To fix it, choose a shorter name.

The name is already taken

A custom name is held by active content. If another piece of content is already using the same name on the same domain, the request is rejected.

Deleting content releases its custom name immediately.

To fix it, choose a different name, or delete the content that currently holds the name you want.

Domain type restrictions

When you assign a wildcard custom domain to your content, you must also provide a custom name — the wildcard domain has no usable URL without one.

A non-wildcard custom domain maps directly to a fixed hostname and cannot accept a custom name. If you need to assign different subdomains to different pieces of content, use a wildcard domain instead.