Skip to content
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

problems connecting #177

Closed
moonwalk123 opened this issue Aug 30, 2016 · 5 comments
Closed

problems connecting #177

moonwalk123 opened this issue Aug 30, 2016 · 5 comments

Comments

@moonwalk123
Copy link

I have launched an instance of your s3 using Docker and can successfully talk to it using cyberduck using an IP address

My software has a requirement to use FQDNs for all addresses, and when I try to connect I get the following error: "Couldn't parse the specified URI.".

How do I configure it to use hostnames?

@nicolas2bert
Copy link
Contributor

nicolas2bert commented Aug 30, 2016

Hey @moonwalk123,

If you specified a host name (e.g. myhostname.com)
Add a new region to your config.json :

"regions": {

     ...

     "localregion": ["localhost"],
     "specifiedregion": ["myhostname.com"]
},

You can provide your own config.json using Docker volume:

docker run -v $(pwd)/config.json:/usr/src/app/config.json --net=host -d scality/s3server

@nicolas2bert
Copy link
Contributor

Hey @moonwalk123, does it help?

Let me know,

Nicolas

@moonwalk123
Copy link
Author

thanks, that worked

Just trying to get SSL set up at the moment, is their a configuration option I need to turn on for that to work?

@nicolas2bert
Copy link
Contributor

Yes @moonwalk123 ,

Add the following section to your config.log

"certFilePaths": {
    "key": "YOUR/PRIVATE/KEY/PATH",
    "cert": "YOUR/PUBLIC/KEY/PATH", 
}

If you are using self-signed certification, on your client side, you will have to either provide a certificate authority or disable the certificate checking.

@moonwalk123
Copy link
Author

Thanks for your help, got everything up and running

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants