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.
Search found 5 matches
- Tue May 30, 2017 12:25 pm
- Forum: Version 3
- Topic: AWS credentials invalid - after upgrade
- Replies: 3
- Views: 44429
- Tue May 30, 2017 12:02 pm
- Forum: Version 3
- Topic: AWS credentials invalid - after upgrade
- Replies: 3
- Views: 44429
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
- Sun Dec 06, 2015 9:57 am
- Forum: Version 2
- Topic: snapshots not deleted
- Replies: 7
- Views: 69963
Re: snapshots not deleted
Thank you Stephan.
- Wed Dec 02, 2015 7:32 pm
- Forum: Version 2
- Topic: snapshots not deleted
- Replies: 7
- Views: 69963
Re: snapshots not deleted
Hi,
I believe I found the source of the issue.
When I specify the job to backup a specific instance, the delete after parameter is saved just fine.
When I switch to "Tag" it's not being saved.
Co you think this could be fixed for "Tag" based as well?
Thanks,
Effy
I believe I found the source of the issue.
When I specify the job to backup a specific instance, the delete after parameter is saved just fine.
When I switch to "Tag" it's not being saved.
Co you think this could be fixed for "Tag" based as well?
Thanks,
Effy
- Tue Dec 01, 2015 10:49 am
- Forum: Version 2
- Topic: snapshots not deleted
- Replies: 7
- Views: 69963
Re: snapshots not deleted
Hi Stephan,
This issue started when I used v2.
I upgraded today to v3, and noticed the same issue still exists.
I've also tried re-creating the job, and the new job didn't update this setting as well.
This is an EC2 snapshot job.
Thanks for your help,
Effy
This issue started when I used v2.
I upgraded today to v3, and noticed the same issue still exists.
I've also tried re-creating the job, and the new job didn't update this setting as well.
This is an EC2 snapshot job.
Thanks for your help,
Effy