We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version used: 1.0.0-canary.5 for both CLI and terraform module. Example followed: atomic-deployments
Terraform setup is successful. Outputs:
api_endpoint = api_endpoint_access_policy_arn =
Deployed using tf-next deploy --endpoint milliVolt CLI 1.0.0-canary.5
success Deployment package uploaded success Deployment ready
Available at:
Set alias to custom domain. Alias set successfully. Checked using tf-next alias ls .
Tried accessing the website and getting "This site can’t be reached" error.
tried accessing directly using the cloudfront url. Getting 500 - Internal Server Error Code: PROXY_MISSING_CONFIG
The text was updated successfully, but these errors were encountered:
it is working with custom domain but not by directly accessing cloudfront.
Sorry, something went wrong.
No branches or pull requests
Version used: 1.0.0-canary.5 for both CLI and terraform module.
Example followed: atomic-deployments
Terraform setup is successful.
Outputs:
api_endpoint =
api_endpoint_access_policy_arn =
Deployed using tf-next deploy --endpoint
milliVolt CLI 1.0.0-canary.5
success Deployment package uploaded
success Deployment ready
Set alias to custom domain. Alias set successfully. Checked using tf-next alias ls .
Tried accessing the website and getting "This site can’t be reached" error.
tried accessing directly using the cloudfront url. Getting 500 - Internal Server Error
Code: PROXY_MISSING_CONFIG
The text was updated successfully, but these errors were encountered: