You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we just download your Cyberduck software and try to connect it with a
bucket Object Storage created and manage by SCALEWAY French hoster. We
followed all tutorial describe in your website and generate a file
name "scaleway.cyberduckprofile" with all informations as specified as
following :
Protocol
s3
Vendor
poc
Description
avantcam-source.s3.fr-par.scw.cloud
Default Hostname avantcam-source
avantcam-source.s3.fr-par.scw.cloud
Default Port
443
Username Placeholder
Access Key XYXY....
Password Placeholder
Secret Key ZZZZ....
Authorization
AWS4HMACSHA256
Region PAR
fr-par
Regions
fr-par
we try to launch this file configuration user account
"scaleway.cyberduckprofile" with your Cyberduck Sotware but nothing
happen after cyberduck start.
Obviously we try also to configure manualy S3 new type account with
"open connexion" in your Cyberduck User Interface. We set url target
Object Storage hosted by Scaleway :
avantcam-source.s3.fr-par.scw.cloud and also put Public and Private
key access to the bucket but after this Cyberduck try to connect to
the bucket but only message "try to connect" is display and folder are not display in Cyberduck interface.
We send several mail to Scaleway support team but they answer to us
that they are not the editor of Cyberduck software and cannot do
nothing for us. They also say to us that apparently our file
configuration user account "scaleway.cyberduckprofile" is good but
they don't know and cannot explain us why your cyberduck sofware
didn't speak and work with theres S3 Object Storage service online.
Could you please help us to solve this issue because we are actualy
stop in our validation test with Cyberduck software ?
Thank you in advance for your help,
Have a good weekend,
Read you soon,
Sinpraseuth - CINESTAF Company
Attachments
scaleway.cyberduckprofile.txt
(0.9 KiB)The text was updated successfully, but these errors were encountered: