iDrive e2 - can't access new bucket/region

Help and Support
21

The interesting thing is, I have recreated this 3 times and it's given me 3 different London endpoints, none of which worked :thinking:

22

Even more interesting is that when I create iDrive remote it does not retrieve any endpoint.

23

I think there is no problem with iDrive. But:

  1. Your server location can not access e5q1.ldn.idrivee2-17.com - clearly some network issue. Could you try to traceroute it?

  2. Idrive remote creation - there is something strange happening with rclone config. This is not the end of the world as you could always create remote by hand. Still would be nice to understand and fix it.

24

are you using vpn, proxy server or something in between your machine and then endpoint?

25

yes that is.

when working with static remotes such as idrive, crypt, sftp, etc,
i do not use rclone config and do not use rclone config file.

tho now, i tested rclone config and it does not auto-populate the endpoint.
on the flip-side, the rclone docs at idrive does not mention endpoint and the example remote does have the endpoint?

26

The same - I do not remember when was last time I used rclone config. Only tried now - no endpoint retrieved:

Configuration complete.
Options:
- type: s3
- provider: IDrive
- access_key_id: 1234
- secret_access_key: 1234
Keep this "asdasdasdasdasd" remote?

EDIT:

When I provide valid credentials it does retrieve endpoint:

Configuration complete.
Options:
- type: s3
- provider: IDrive
- access_key_id: XXX
- secret_access_key: XXX
- endpoint: p7v1.ldn.idrivee2-40.com

And this is one I would expect.

So I think it is me just not knowing how it works:) As I do most config by hand

27

The server does not use any VPN or proxy. It does use NextDNS but the endpoint is resolved to the correct IP (as shown in the ping command and using dig).

28

That's so weird that both your rclone configs don't retrieve an endpoint and mine does.

Are you choosing '5' for S3 and '12' for iDrive from the config choices?

How are you using rclone without a config file?

29

Let's forget rclone config - it is working (see my last post EDIT). Problem is networking here on OP server.

30

some remotes such as gdrive, onedrive uses tokens which expire, so rclone to save the updated tokens in the config file. so rclone needs to write that token.

some remotes such as s3, sftp, crypt, ftp, etc do not use tokens, rclone never needs to change/write the config.
so can pass the config to rclone as
--- connection strings
--- environment variables

31

I think now we know what the problem is and also that we can not fix it...

It is either iDrive blocking traffic from the OP server or vice versa - with small chances of some issue in between....

But if this server works for other iDrive bucket (in DE) than I would start with sending email to server provider... asking why ping e5q1.ldn.idrivee2-17.com fails.

@dinosm could you run from your server:

$ traceroute e5q1.ldn.idrivee2-17.com
32

i think you are correct.

i checked the rclone source code
setEndpointValueForIDriveE2 gets user region endpoint against the Access Key details by calling calling the API

i checked the idrive docs
API to get user region endpoint against the Access Key details

33

That gives:

traceroute to e5q1.ldn.idrivee2-17.com (191.96.59.8), 30 hops max, 60 byte packets
 1  172.31.1.1 (172.31.1.1)  10.640 ms  10.598 ms  10.666 ms
 2  15770.your-cloud.host (49.12.139.33)  5.524 ms  5.582 ms  5.571 ms
 3  * * *
 4  spine4.cloud1.nbg1.hetzner.com (88.198.252.205)  6.592 ms spine3.cloud1.nbg1.hetzner.com (88.198.252.201)  6.616 ms  7.218 ms
 5  * * *
 6  core11.nbg1.hetzner.com (213.239.203.101)  7.168 ms core12.nbg1.hetzner.com (213.239.239.141)  1.824 ms core11.nbg1.hetzner.com (213.239.203.101)  1.735 ms
 7  core5.fra.hetzner.com (213.239.224.238)  5.081 ms  14.941 ms  14.848 ms
 8  combahton-gw.hetzner.com (213.133.113.34)  4.223 ms  4.168 ms  4.376 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *

Tracerouting the endpoint that does work gives:

 1  172.31.1.1 (172.31.1.1)  4.839 ms  4.781 ms  4.764 ms
 2  15770.your-cloud.host (49.12.139.33)  2.865 ms  2.934 ms  2.886 ms
 3  * * *
 4  spine3.cloud1.nbg1.hetzner.com (88.198.252.201)  3.809 ms  4.141 ms  4.131 ms
 5  * * *
 6  core11.nbg1.hetzner.com (213.239.239.121)  3.727 ms core11.nbg1.hetzner.com (213.239.203.101)  1.237 ms core12.nbg1.hetzner.com (213.239.203.105)  1.377 ms
 7  core1.fra.hetzner.com (213.239.245.254)  4.296 ms  3.365 ms core1.fra.hetzner.com (213.239.245.250)  3.851 ms
 8  ae18.cr6-fra2.ip4.gtt.net (154.14.78.153)  4.662 ms  4.502 ms  4.473 ms
 9  ae3.cr3-fra6.ip4.gtt.net (89.149.140.14)  8.756 ms  3.901 ms  3.925 ms
10  ip4.gtt.net (213.254.222.202)  5.019 ms  4.978 ms  5.076 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
34

It looks indeed like hetzner decision to block it. Maybe somebody else using their services was abusing it? It is impossible to guess.

Contact their support.

There is no issue with rclone. There is no issue with iDrive.

Also if you have any response please share - it can help others with similar problem.

35

Traceroute isn't great to make a conclusion as many providers along the way will block that.

If you can't ping it, that's generally a better test as that will tell you it's not accessible if you can ping it from other locations.

Plex blocked hetzner

Maybe idrive did, you can ask them I'd imagine.

36

iDrive in general is not blocked by Hetzner (or the other way round), as my iDrive endpoint in Frankfurt works just fine.

I will however ping Hetzner and iDrive to ask about this.