Rclone Operation forbidden

[BlompSupport]

Hello Blomper,

I have passed the message to the tech team.
I will let you know if they have made any changes in the swift backend.

Regards,

[BlompSupport]

Dear Blomper,

I've received feedback from the tech team concerning your inquiry.

They have implemented some modifications to Openstack. According to them, these changes should not adversely affect the user experience.

Kindly verify whether the issue has been resolved.

Thank you.

[ZZ9B9]

No, I still face the issue.

Why not test accessing blomp service using the sample rclone config I shared?

I am definitely sure the issue will be reproduced.

Thanks.

[BlompSupport]

Hello Blomper,

We are sorry that that you are still experiencing issues with Rclone.

Since we do not provide direct support for Rclone, we recommend checking the links below, where the Rclone and Blomp communities engage in discussions about similar issues. You may find a potential solution through these discussions. Additionally, you have the option to contact Rclone directly for assistance.

Additional links:

https://forum.rclone.org/t/rclone-mount ... em/29151/8

https://support.blomp.com/viewtopic.php ... 59a5537466.

We thank you for using Blmop and for being part of this amazing community.

Wishing you a great day ahead.

Regards,

[zeref]

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.

I also started getting recently 404, then I tried with

Code: Select all

auth = http://authenticate.blomp.com/v2.0/

(so I've added /v2.0/) and now it works.

[BlompSupport]

Hey Zeref,

Thank you for sharing your experience and helping the Blomp community. We appreciate you as a member of the our awesome Blomp community.

Have a fantastic day as you are

Kind Regards,

[mksm_]

Yes, week or so now I getting same 404 Error to. Definitely problem from Blomp side.
Failed to create file system for "cloud:": HTTP Error: 404: 404 Not Found

Yes I changed https://authenticate.blomp.com/ to https://authenticate.blomp.com/v2.0/ and suddenly it works

It's strange why we should get this information from users and not from support

[BlompSupport]

Hey Blomper,

It's awesome to see our community buzzing with communication and interaction—it's what makes our community so fantastic!

We are happy that you have resolved the issue. Just a quick heads up, though: we don't offer direct support for rclone, and we're not the go-to for rclone info. But hey, if you've got any other questions or just want to chat about our Blomp services, hit us up anytime.

We're here to make things easy for you!

Cheers,

[knightrider1994]

Hello, I am wanting to rejoin the Blomp team, but after restoring my configs for rclone I am unable to connect, When running any actions against my remotes I get the errors below. I have tried with the /2.0/ auth url and no luck, Is there anyone that might be able to take a look?


Error when trying to LS on alias -

rclone ls blomp-alias: -vv
2024/03/30 07:38:28 DEBUG : rclone: Version "v1.66.0" starting with parameters ["C:\\ProgramData\\chocolatey\\lib\\rclone.portable\\tools\\rclone-v1.66.0-windows-amd64\\rclone.exe" "ls" "blomp-alias:" "-vv"]
2024/03/30 07:38:28 DEBUG : Creating backend with remote "blomp-alias:"
2024/03/30 07:38:28 DEBUG : Using config file from "C:\\Users\\USERNAME\\AppData\\Roaming\\rclone\\rclone.conf"
2024/03/30 07:38:28 DEBUG : Creating backend with remote "blomp-remote:EMAIL"
2024/03/30 07:38:30 DEBUG : fs cache: renaming cache item "blomp-alias:" to be canonical "blomp-remote:EMAIL"
2024/03/30 07:38:30 DEBUG : 4 go routines active
2024/03/30 07:38:30 Failed to ls: Operation forbidden


rclone.config -

[blomp-remote]
type = swift
tenant = storage
user = EMAIL
auth = http://authenticate.blomp.com/v2.0/
auth_version = 2
chunk_size = 1P
key = PASSWORD
leave_parts_on_error = true

[blomp-alias]
type = alias
remote = blomp-remote:EMAIL

[BlompSupport]

Dear Blomper,

Happy Monday!

We are sorry to hear that you can not connect to Blomp after restoring your Rclone configs.

Please make sure that you are using the latest version of Blomp! Kindly update the latest version of Blomp and let us know if it works.

If you're still encountering difficulties, please note that while we don't offer direct support for Rclone. However, we still may be able to help. We suggest exploring the following resources.

https://forum.rclone.org/t/rclone-mount ... blem/29151
https://support.blomp.com/viewtopic.php ... 06b947d9b4

These links connect you to discussions within the Rclone and Blomp communities, where similar issues are addressed. You might discover a solution through these conversations.

Alternatively, reaching out to Rclone directly for assistance is also an option.

Thank you for choosing Blomp and for being a valued member of our community. Have a wonderful day ahead!