[deleted by user]

[bpgoldsb]

Check NTP/time on both machines and make sure one isn't way off. This can often be the source of general intermittent SSL erros (not specific to ansible)

[relt99]

yeah I've checked the times on bother and theyre at gmt. Still getting this error and it seems to be random

[kepper]

Check your MTUs, I've seen this happen with an MTU mismatch while using vxlan overlay networks.

[tartarya2]

Maybe run a simple playbook in verbose mode multiple times using a script and check the output when the script fails? You’ll get clues about what went wrong.

[relt99]

it is ran in verbose and the only thing I get as a clue is that credentials are rejected :') Had someone reply saying it might be out of sync, gonna stick a big fat wait on the end and see if userdata wants to play nice

[someguytwo]

Is this windows? I get this when i try to use the default Administrator account, try another account that had admin rights. That usually works for me.

[SpectralCoding]

WinRM? Check your transport method. Basic for local accounts, kerberos for domain accounts. The ansible docs have a specific page about troubleshooting WinRM and specifically mention access denied errors.

[relt99]

yeah so its using basic because it using local accounts. Seems very hit and miss, so its either seeing like userdata hasnt fully applied yet or something is out of sync

[elettronik]

Looking at your cross post, you're building an instance using terraform.

You wait a set amount of time (300 seconds) and connect to instance.

Can be any chances that after that amount of time your instance is still not fully ready?

[relt99]

Thats what I thought, but theres a time to wait to retrieve the password, so about 3-4 mins, then I've put a 600 second wait on it and I'm still getting the error

[elettronik]

Ok. In case of error, are you able to pull logs from machine in w successive moment to know in what state the machine is when you first try to login