@dkocher commented

It should work if you customize the connection profile and set a region like

	<key>Region</key>
	<string>WAW</string>

I have not yet verified this myself.

@dkocher commented

In 669e41d.

@dkocher commented

Can you please try if still see this issue with the current snapshot build 7.8.3.34379 or later
by updating from within Cyberduck in ''Preferences → Update →
Automatically check for updates in → Snapshot Builds''.

49d04f6 commented

I am aware of a Region/WAW hack (described in #10194). But without a hack Cyberduck can't connect even though some regions are accessible. The defect is the same in 7.6.2 and in 7.6.3 as well. I updated to version 7.6.3 but still can't connect without adding the WAW region to my profile. A connection log is the same, logging ends at request: "Host: storage.sbg.cloud.ovh.net", reply: "HTTP/1.0 503 Service Unavailable" with "503 Service Unavailable" message.
When I connect with a hack, Cyberduck offers me all regions, even unavailable SBG.

@dkocher commented

Replying to [comment:6 pik256]:

I am aware of a Region/WAW hack (described in #10194). But without a hack Cyberduck can't connect even though some regions are accessible. The defect is the same in 7.6.2 and in 7.6.3 as well. I updated to version 7.6.3 but still can't connect without adding the WAW region to my profile. A connection log is the same, logging ends at request: "Host: storage.sbg.cloud.ovh.net", reply: "HTTP/1.0 503 Service Unavailable" with "503 Service Unavailable" message.
When I connect with a hack, Cyberduck offers me all regions, even unavailable SBG.

Can you confirm you are running 7.8.3 (34379).

22e47ae commented

Replying to [comment:7 dkocher]:

Replying to [comment:6 pik256]:

I am aware of a Region/WAW hack (described in #10194). But without a hack Cyberduck can't connect even though some regions are accessible. The defect is the same in 7.6.2 and in 7.6.3 as well. I updated to version 7.6.3 but still can't connect without adding the WAW region to my profile. A connection log is the same, logging ends at request: "Host: storage.sbg.cloud.ovh.net", reply: "HTTP/1.0 503 Service Unavailable" with "503 Service Unavailable" message.
When I connect with a hack, Cyberduck offers me all regions, even unavailable SBG.

Can you confirm you are running 7.8.3 (34379).

Where this version can be found as on cyberduck.io the only available is 7.8.2 (34203)

22e47ae commented

In fact it works when using ovh profile template given above and add the Region strings inside it. i did succeed in connecting to it with modified profile AND cyberduck.io 7.8.2 (34203) on windows. Thanks for the directions

@dkocher commented

Replying to [comment:8 keben]:

Where this version can be found as on cyberduck.io the only available is 7.8.2 (34203)

Update from within Cyberduck in ''Preferences → Update →
Automatically check for updates in → Snapshot Builds''.

49d04f6 commented

I can confirm. I have updated to 7.8.3 (34379). An update from snapshot builds.
It does not work without inclusion of region string in profile.

1. Default OVH profile: service unavailable.
2. Profile with

        <key>Region</key>
        <string>WAW</string>

connected.

@dkocher commented

I can no longer reproduce this issue with the fix applied. Can you please share the HTTP transcript from the log drawer on Windows (Ctrl-L) or by obtaining the log from Console.app.

49d04f6 commented

I have updated application to v 7.8.3 build 34380. It behaves the same. The log drawer is similar to the one from my first opening ticket post:

POST /v3/auth/tokens HTTP/1.1
Accept: application/json
Content-Type: application/json
Content-Length: 240
Host: auth.cloud.ovh.net
Connection: Keep-Alive
User-Agent: Cyberduck/7.8.3.34380 (Windows 7/6.1) (amd64)
HTTP/1.1 201 Created
X-Subject-Token: gAAAAABgTyKPhb1xDZfpTi1ebSbx2P9ha-....
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 38039
x-openstack-request-id: req-14aaa4a2-c386-4843-9b9e-b8eac17c7dd2
X-IPLB-Request-ID: 9C435819:0B30_334441F7:01BB_604F228E_A13DBC:21234
X-IPLB-Instance: 24497
HEAD /v1/AUTH_43d77b97e6c24395aa047319370cd843/v3 HTTP/1.1
X-Auth-Token: ********
Host: storage.de.cloud.ovh.net
Connection: Keep-Alive
User-Agent: Cyberduck/7.8.3.34380 (Windows 7/6.1) (amd64)
HTTP/1.1 404 Not Found
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Trans-Id: tx6af90c0989374f64913af-00604f2290
X-Openstack-Request-Id: tx6af90c0989374f64913af-00604f2290
Date: Mon, 15 Mar 2021 09:02:08 GMT
HEAD /v1/AUTH_43d77b97e6c24395aa047319370cd843/v3 HTTP/1.1
X-Auth-Token: ********
Host: storage.uk.cloud.ovh.net
Connection: Keep-Alive
User-Agent: Cyberduck/7.8.3.34380 (Windows 7/6.1) (amd64)
HTTP/1.1 404 Not Found
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txa87333041026438c974df-00604f2290
X-Openstack-Request-Id: txa87333041026438c974df-00604f2290
Date: Mon, 15 Mar 2021 09:02:08 GMT
HEAD /v1/AUTH_43d77b97e6c24395aa047319370cd843/v3 HTTP/1.1
X-Auth-Token: ********
Host: storage.gra.cloud.ovh.net
Connection: Keep-Alive
User-Agent: Cyberduck/7.8.3.34380 (Windows 7/6.1) (amd64)
HTTP/1.1 404 Not Found
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txf7735acd8dfb482997f1d-00604f2291
X-Openstack-Request-Id: txf7735acd8dfb482997f1d-00604f2291
Date: Mon, 15 Mar 2021 09:02:12 GMT
X-IPLB-Request-ID: 9C435819:0B33_3626E64B:01BB_604F2290_3B9ED6:1DF18
X-IPLB-Instance: 33617
HEAD /v1/AUTH_43d77b97e6c24395aa047319370cd843/v3 HTTP/1.1
X-Auth-Token: ********
Host: storage.sbg.cloud.ovh.net
Connection: Keep-Alive
User-Agent: Cyberduck/7.8.3.34380 (Windows 7/6.1) (amd64)
HTTP/1.0 503 Service Unavailable
Cache-Control: no-cache
Connection: close
Content-Type: text/html

I have created %AppData%\Cyberduck\default.properties file with logging=debug line and %AppData%\Cyberduck\cyberduck.log file was created but it is empty.

@dkocher commented

Add additional checks for 503 responses for unavailable regions in 0eb56e9.

49d04f6 commented

v. 7.8.3 build 34400 works as expected. Thank you.