Repository navigation
bug: auto-generated task name is too long preventing Task from starting #20224
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Description
We've gotten reports from a customer of failure to start/spin up a task because the domain name is too long. Note I changed the domain name in the error below to not include specific customer information. See the linked Slack thread for specifics.
It was brought up potentially using Subject Alternative Name (SAN) instead of CN.
Relevant Log Output
ValueError: Domain name [task-turquoise-elephant-71-name-redacted.direct.coder.dev.redacted.ab](http://task-turquoise-elephant-71-name-redacted.direct.coder.dev.redacted.ab/) is too long. Must be 64 characters or less. Please create a new workspace with a shorter name.
Expected Behavior
Tasks, regardless of the character count of the task name, should spin up without issue.
Steps to Reproduce
- Create a test user with a super long username
- Setup a deployment with a long domain name
- Create a task
Environment
tbd
Additional Context
No response
Activity
johnstcn commentedon Oct 15, 2025
@DanielleMaywood to close this out with the solution
DanielleMaywood commentedon Oct 16, 2025
The issue isn't with Coder but with the customer's template/provisioning script when they generate X.509 certificates using OpenSSL. The solution is for them to use SAN for the FQDN instead of CN, since CN has a 64-character limit per RFC 5280.