Unable to use "alias" field in now.json the first time we deploy
See original GitHub issueOn a new project, if we include "alias": "www.my-site.com"
, running npx now
gives this error:
> Error! Unexpected error. Please try again later. ()
If we remove the "alias"
field, it works fine and it builds the project.
If we include "alias"
back again after the first build, it works fine.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Unable to use "alias" field in now.json the first time we deploy · Issue ...
If we remove the "alias" field, it works fine and it builds the project. If we include "alias" back again after the first...
Read more >Alias field type | Elasticsearch Guide [8.5] | Elastic
Writes to field aliases are not supported: attempting to use an alias in an index or update request will result in a failure....
Read more >Why can't I use column aliases in the next SELECT expression?
The solution is to encapsulate the query in a subquery and then the alias is available outside. SELECT stddev_time, max_time, avg_time, min_time ...
Read more >Using JSON in Go: A guide with examples - LogRocket Blog
JSON is one of the most-used formats for storing data. In this guide, learn how to work with JSON in Go using the...
Read more >Amazon Route 53 FAQs - Amazon Web Services
You can use Route 53 to create DNS records for a new domain or transfer DNS records ... once when they are created...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@luisherranz @SantosGuillamot Thank you for providing the debug information.
The reason why this error occures is that the deployment is the first deployment of this project. We will automatically promote the first deployment of a project to
target=production
.So we tried to verify the alias, that failed because it is not a domain you own.
We further improved the error message.
I have tried it again and it’s still happening. This is the output after using the
--debug
flag, let me know if you need anything else: