Invalid endpoint
See original GitHub issueHello i’m trying to use minio on docker containers, and I usually use docker names as hostnames since it resolves correctly with the docker DNS system.
But I can’t because I got this exception :
Minio.Exceptions.InvalidEndpointException: 'Minio API responded with message=Endpoint: minio_recette does not follow ip address or domain name standards.'
I use both the java & c# api for minio, and solved my problem on the java side by using http://minio_recette:9000 as my endpoint, but the c# doesn’t allow for “/” in the endpoint.
Could you please support simple names, for docker containers ? Thanks
I’m still trying to find a way around this…
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Invalid endpoint on aws s3 ls
Any ideas why I get 2 dots in place of my region in the s3 link, causing the invalid endpoint error? Thanks for...
Read more >Invalid endpoint: https://ec2..amazonaws.com · Issue #8220
Describe the bug. When I run these commands and use policy listed below (defaulttest.yml), I get an error -. `pip install c7n.
Read more >Troubleshoot API Gateway Invalid endpoint address errors
I'm seeing "Execution failed due to configuration error: Invalid endpoint address" errors in my Amazon CloudWatch execution logs for Amazon API Gateway.
Read more >Invalid Endpoint Error in AWS CLI [Solved]
# Invalid Endpoint Error in AWS CLI [Solved]. The "Invalid endpoint" error occurs when the region that applies to the AWS CLI command...
Read more >Invalid Endpoint Error in AWS CLI [Solved] | by Glasshost
This error means that you have specified an incorrect endpoint for your AWS service, or you may have specified an endpoint that is...
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
I see the issue was reported closed? Have there been any updates or workaround figured for this issue?
For the dotnet project, I am using I used only the IP: Port configuration i.e. “127.0.0.1:9000”.