Installing Cloudron fails - AWS Route53 - Configuration error: Inaccessible host: `route53.amazonaws.com' at port `443'. This service may not be available in the `us-east-1' region.
-
Configuration error: Inaccessible host:
route53.amazonaws.com' at port443'. This service may not be available in the `us-east-1' region.I tried to initialize my domain, created the IAM user, assigned the right policies, but I always get this error.
Also, what's super weird is that the Access Key doesn't seem to be used at all.
Never used. Created today.
I'm using Hetzner. It's a brand-new server.
I also noticed if I use a different Access Key (like a wrong one), the same behavior and error happens, as if the query wasn't even reached AWS.Do you know what could be wrong?
-
Configuration error: Inaccessible host:
route53.amazonaws.com' at port443'. This service may not be available in the `us-east-1' region.I tried to initialize my domain, created the IAM user, assigned the right policies, but I always get this error.
Also, what's super weird is that the Access Key doesn't seem to be used at all.
Never used. Created today.
I'm using Hetzner. It's a brand-new server.
I also noticed if I use a different Access Key (like a wrong one), the same behavior and error happens, as if the query wasn't even reached AWS.Do you know what could be wrong?
@DNA-PC said in Installing Cloudron fails - AWS Route53 - Configuration error: Inaccessible host: `route53.amazonaws.com' at port `443'. This service may not be available in the `us-east-1' region.:
are you able to
ping route53.amazonaws.comfrom the server? I suspect there is some networking or firewall issue -
G girish marked this topic as a question on
-
root@n8n-ubuntu-4gb-nbg1-2:~# ping route53.amazonaws.com
ping: connect: Network is unreachableI guess you're right, but I don't understand what could be the cause, I don't have a Firewall setup on Hetzner.
-
Ah, it might be because I only have a IP v6 and not IP v4.
https://www.reddit.com/r/hetzner/comments/18ur5eu/network_is_unreachable_even_after_rebuild/
-
root@n8n-ubuntu-4gb-nbg1-2:~# ping route53.amazonaws.com
PING route53.amazonaws.com (54.239.31.187) 56(84) bytes of data.
64 bytes from 54.239.31.187 (54.239.31.187): icmp_seq=1 ttl=235 time=92.7 msIndeed, after assigning an IP v4 the ping works.
It should be part of the Cloudron documentation that not having an IP v4 can lead to such troubles.
And/or adapt Cloudron install to reach AWS on IPv6, as fallback. -
root@n8n-ubuntu-4gb-nbg1-2:~# ping route53.amazonaws.com
PING route53.amazonaws.com (54.239.31.187) 56(84) bytes of data.
64 bytes from 54.239.31.187 (54.239.31.187): icmp_seq=1 ttl=235 time=92.7 msIndeed, after assigning an IP v4 the ping works.
It should be part of the Cloudron documentation that not having an IP v4 can lead to such troubles.
And/or adapt Cloudron install to reach AWS on IPv6, as fallback. -
G girish has marked this topic as solved on