Rclone Operation forbidden

[mksm_]

Hello,

Can't work with storage via rclone. Always got error :

--
2023/12/29 19:33:59 Failed to size: container listing failed: Operation forbidden
--
2023/12/29 19:27:33 ERROR : Attempt 1/3 failed with 1 errors and: Operation forbidden

2023/12/29 19:27:34 ERROR : Attempt 2/3 failed with 1 errors and: Operation forbidden

2023/12/29 19:27:34 ERROR : Attempt 3/3 failed with 1 errors and: Operation forbidden
2023/12/29 19:27:34 Failed to mkdir: Operation forbidden
--

Rclone 1.65

Config:

[blomp-remote]
type = swift
user = xxx
key = xxx
auth = https://authenticate.blomp.com
tenant = storage
auth_version = 2
endpoint_type = public
leave_parts_on_error = true
chunk_size = 1P
no_chunk = false

[BlompSupport]

Hey there!

Just a heads up, we don't offer direct support for Rclone, but no need to stress! If you shoot us your log file, we might still be able to help.

While you're waiting, why not check out this link https://support.blomp.com/viewtopic.php ... 59a5537466. ? Our Blomp community loves chatting about similar topics, and you might find some useful insights there!

Wishing a fantastic weekend and Happy New Year!

[mksm_]

Thank you! I already showed logs in my first post.

Her the log output from command rclone about blomp: --log-file=mylogfile.txt

2023/12/29 21:44:19 Failed to about: about call failed: container listing failed: Operation forbidden

[mksm_]

Since there is no support from Blomp, I managed to find a workaround. If you have the same problem with Rclone, try it. You need to use an alias or crypt layer over the base Blomp configuration in rclone. Here the example of rclone.conf file:

[blomp]
type = swift
user = xxxxx@mail.com # your login
key = xxxxx # your password
auth = https://authenticate.blomp.com/v2.0/
tenant = storage
auth_version = 2
endpoint_type = public
leave_parts_on_error = true
chunk_size = 1P
no_chunk = false

[blomp_alias]
type = alias
remote = blomp:xxxxx@mail.com # add your login again after ":"

OR if you like to use Crypt instead Alias

[blomp_crypt]
type = crypt
remote = blomp:xxxxx@mail.com # add your login again after ":"
password = xxxxxxxxxxxxxxxxxxxxx # add your encryption password here


Also, I really like to get an explanation from Blomp support as to why it works this way and does not work with the base configuration.

[mksm_]

So. No such thing as Blomp support.

[BlompSupport]

Happy New Year Blomper!!

We apologize for the delay in responding, which is due to the holiday season.
Our tech team has been notified about your issue, and you can expect a prompt response.

Thank you for your patience!

Best Regards,

[BlompSupport]

Dear Blomper,

We appreciate your interest in using Blomp services.

However, please note that we do not currently support Rclone. We recommend checking the Rclone forum linked below, where you can find all the information you need.

https://forum.rclone.org/t/rclone-mount ... blem/29151

Thank you and have a wonderful day.

Best regards,

[ZZ9B9]

However, please note that we do not currently support Rclone. We recommend checking the Rclone forum linked below,

Dont support rlcone?? suddenly? I have been using my rclone configured to use blomp since last 2 years?
Is this a new year gift to us, and no official communication that rlcone wont work with blomp anymore?

I started getting this:

Code: Select all

Failed to create file system for "XXX:": HTTP Error: 404: 404 Not Found

2 days back all was fine.

[BlompSupport]

Greetings Blomper,

Wishing you a joyful holiday season!

We wanted to let you know that direct support for Rclone is not available from us. However, you may find assistance by visiting the Rclone community discussion at https://forum.rclone.org/t/swift-env-au ... ound/22520. There, the community shares insights on similar issues, and you might discover a solution that suits your needs.

Best regards,

[ZZ9B9]

Thanks for the reply, i understand that blomp does not provide rclone support directly, but since its swift based,
standard rclone configuration for swift backends should work.

And it indeed worked since last 2 years i have been using blomp this way, but around jan 4 2024, i started getting the 404 error.
Can you ensure that nothing changed at swift backend at blomp, which might cause this failure?

You can quickly test this out with these settings that used to work (before 4thJan 2024):

Code: Select all

Code: Select all

[blomp-config]
type = swift
user = abc@mail.com
key = XXXX
auth = https://authenticate.blomp.com
tenant = storage
auth_version = 2

Regards and Thanks for your concern.