Hostname would be something like:
and to not get SSL-Certificate problems, hostnames can't look like
as it would require a ..mydomain.com SSL-Cert.
Therefore this instance sticks to namepspace.mydomain.com/bucket
But if you need me to do anything / send any error messages, that would help you to identify the issue,
I can gladly do.
Unfortunately, some environments use a wildcard DNS entry that will always succeed, preventing Cyberduck from falling-back to path-style access. Would it be possible to have a configuration setting (or similar) that disables virtual host style access completely, please?