-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
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
An error occurred (404) when calling the ListDomainNames operation #72
An error occurred (404) when calling the ListDomainNames operation #72
Comments
Thanks for the report. Can you please provide more details about your environment/configuration, and the steps to reproduce? It looks like this error is coming from the backend of the Web UI, so I'm assuming the error is triggered once you point your browser to http://localhost:8080 , is that correct? If not, which user action actually triggers that error? Which exact command did you use to start the Docker container? Can you please post the entire output of the terminal in which you execute Also, did you set any of the custom configurations (see https://github.com/atlassian/localstack#configurations)? For instance, did you provide custom values for the Finally, just to double check that you are using the latest image, can you please post the output of the following command:
Thanks |
Sorry my question was not so clear. My network is behind a proxy, all requests should go through that proxy or failed. I've set the And:
|
Unfortunately I still cannot reproduce this issue. Can you please elaborate a little more on your exact setup (exact proxy configuration, value of Generally speaking, having all services behind a (single) proxy might be a problem, because LocalStack expects the services to run on different ports. When you encounter a |
I'm closing this issue for now, as there are not enough details provided to reproduce the problem (might be related to incorrect proxy settings). Please feel free to re-open if the problem persists and you can provide more details. Thanks |
This error raised after the docker container started. What should I do? I'm running it in docker on Windows 10.
The text was updated successfully, but these errors were encountered: