• Stephen Dolman
    Since updating to the latest CloudBerry Explorer version (, the region is being automatically added to our S3 files. Does anyone know if this can be removed? Currently on freeware version.
    This is under 'Object Properties' >> 'Web URL'
    • Now: https: //e-gain.s3.eu-west-1.amazonaws.com/EE/<filename>
    • Previous: https: //e-gain.amazonaws.com/EE/<filename>
  • David Gugick
    As far as I can tell from AWS docs, the region is a part of the full name you use to access objects in Amazon S3: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-bucket-intro.html

    I am not sure about the format you are using. From what I can see, there are two ways to access:

    Virtual-hosted–style access:
    Path-style access:

    You could try using the recommended virtual hosted style without the region and see if it works.
  • David Gugick
    Also see if this helps:

    Otherwise, you can open a support case as I am not sure if the issue you're running into is something that was supported by Amazon but has been deprecated, or it's something that can be changed it the product or your application that accesses the objects.
  • Stephen Dolman
    Thanks. The above is great reference but I don't think it gives me the basic solution I'm looking for.

    In summary I want the Web URL within a hosted files Web URL to not auto-populate with the region, in the 'Object Properties' window.

    Cloudberry Explorer running on older machines (today) - Build, populates the Web URL with no region in the URL by default.

    Cloudberry Explorer running on our new machines (today) - Build, populates the Web URL with the region in the URL by default.

    This seems to indicate its a change in the product build when forming the web URL in the Object Properties.

    How can I raise a support case?

  • David Gugick
    You need to hit the Support section of the msp360.com web site. Usually you need maintenance on a product to open a support case, but if they ask (and you do not have maintenance), then ask politely and let them know you tried the forum. If that fails, I can try to open an internal case.

    Having said that, I think the product is working correctly now given the Amazon specs for URL access. I realize that the older version may not have been AWS compliant in that regard. Why can't you use the recommended URL style, if I may ask? Is it because you have an application expecting the old format and changes would be difficult?

    What happens when you upload a file to your S3 bucket using the AWS Management Console - is the URL format the same as Explorer or does it use the older format? Just curious.

    And I guess I should have asked: Is this the paid or free version of Explorer. If the free version, you will not be able to open a support case...
Add a Comment