https://lakefs.io/ logo
Join Slack
Powered by
i use `aws s3 --profile lakefs --endpoint-url <htt...
# help
б
i use 
aws s3 --profile lakefs --endpoint-url <https://192.168.0.65:8000> ls <s3://s3bk/main>
to see my bucket, but it errors, how can i fix it? follow are error message:
Copy code
SSL validation failed for <https://192.168.0.65:8391/s3bk?list-type=2&prefix=main&delimiter=%2F&encoding-type=url> [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:852)
t
Hi @Борис Антипов, welcome!
Do you see errors in your lakeFS logs?
б
@Tal Sofer lakefs works well and no errors occurs
here's my config, i have already to disable sslmode
Copy code
database:
        connection_string: "<postgres://postgres:123@192.168.0.65:5432/postgres?sslmode=disable>"
auth:
  encrypt:
    secret_key: "123"
blockstore:
  type: s3
  s3:
    force_path_style: true
    endpoint: <http://192.168.0.65:8391>
    credentials:
      access_key_id: admin
      secret_access_key: seaweedfs
t
Thanks! can you try 
aws s3 --profile lakefs --endpoint-url <https://192.168.0.65:8000> ls <s3://s3bk/main>  --no-verify-ssl
and see if this works? https://www.shellhacks.com/aws-cli-ssl-validation-failed-solved/
б
@Tal Sofer it does not work😂
t
Where is your lakeFS server running? and are you using s3 as your storage? I’m not familiar with this error, will take a look and update here what iv’e found 🙂
б
lakefs server running at 
<http://192.168.0.65:8000>
, s3 endpoint url is 
<http://192.168.0.65:8391>
i upload 
3d8ee342e3614df29b1381e99685990e
by lakefs web
t
I meant if you running lakeFS in AWS, and if you are using aws s3 as you storage?
б
i use seaweedfs as my storage
t
That’s very cool!! and clarifies your blockstore configurations
б
Copy code
database:
        connection_string: "<postgres://postgres:123@192.168.0.65:5432/postgres?sslmode=disable>"
auth:
  encrypt:
    secret_key: "123"
blockstore:
  type: s3
  s3:
    force_path_style: true
    endpoint: <http://192.168.0.65:8391>
    credentials:
      access_key_id: admin
      secret_access_key: seaweedfs
i think it is a problem about my aws config, no bussiness with lakefs
t
We never tests lakeFS with seaweedfs, so I opened https://github.com/treeverse/lakeFS/issues/3033 to track this task.
б
ok, thanks😀
t
Your welcome, we are very excited to hear about new use cases for lakeFS and will appreciate any feedback or feature request 🙂
👏 1
i think it is a problem about my aws config, no bussiness with lakefs
I tend to agree, you may want to look at _ca_bundle_
👌 1
a
Sorry to enter the conversation late. I think you should be accessing your endpoint using http, not https. Please check your endpoint URL.
👍 1
б
@Tal Sofer Hi，`lakectl ingest --from s3://s3bk/filersUp.sh --to lakefs://s3bk/main` how the cmd use? it errors:
Copy code
Error executing command: Invalid 'to': not a valid path uri
a
Background: it will be difficult to get a certificate with an IP address as the common name. You will certainly need to use a private CA, and then configure your local client to accept that CA.
sunglasses lakefs 1
б
@Ariel Shaqed (Scolnicov) it works!
lakefs 2
👍🏼 2
t
@Борис Антипов you are missing a slash at the end of your path, please try 
lakectl ingest --from <s3://s3bk/filersUp.sh> --to <lakefs://s3bk/main/>
2 Views
Open in Slack
PreviousNext
Powered by