I've recently tried upgrading from v3.1 to v3.3, during a windows server upgrade (2012 -> 2016).
I can't get the new version to work, it keeps throwing "AWS credentials invalid", even though the credentials are correct.
I've updated the policy according to the new policy required by 3.3, but nothing seems to help this issue.
Any clues?
Thanks!
Effy
AWS credentials invalid - after upgrade
Re: AWS credentials invalid - after upgrade
This message shows up when AutomatiCloud is not able to login to AWS services. Please check your firewall and proxy settings.
Stephan
Stephan
Re: AWS credentials invalid - after upgrade
Hi,
I've tried disabling the firewall on the Windows Server, and opening all Outbound TCP on one of the server's Security Group, I still receive the same issue.
Is there anyway to debug this and figure out what's the root of this issue?
Thanks,
Effy
I've tried disabling the firewall on the Windows Server, and opening all Outbound TCP on one of the server's Security Group, I still receive the same issue.
Is there anyway to debug this and figure out what's the root of this issue?
Thanks,
Effy
Re: AWS credentials invalid - after upgrade
I've figured out the issue.
TLS 1.0 was disabled on my server, due to IISCrypto usage.
Once I enabled it the backups re-started working.
TLS 1.0 was disabled on my server, due to IISCrypto usage.
Once I enabled it the backups re-started working.