Skip to content

Wildcard access URL behavior is confusing for new installs #19120

@bpmct

Description

@bpmct

Setting a wildcard access URL is practically a requirement for any Coder deployment that supports web IDEs (e.g. code-server) and needs preview URLs for an app.

Frameworks like Vite, React, Express, etc. do not support path-based apps (coder.example.com/workspace-name/proxy/4200/) by default and some modules (e.g. KasmVNC) do not support path-based apps.

See related ProductBoard for customer insights

Acceptance Criteria

This can be split into sub-issues, or expanded upon

  • Our documentation mentions the importance of wildcard domains during the install / set up of Coder
  • Users see clear warnings on the workspace page when wildcard is not configured
  • Template admins see clear warnings when they use a coder_app that requires a subdomain, but wildcard is not configured

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions