Hey, @alex-feel,
Thank you for providing those screenshots and additional information! That makes a lot more sense to me now what was going on.
Your screenshots helped show that the issue is occurring due to the runner IP not having access to Vultr.
- The IPs you’re listing are correct, BUT those IPs are for the Terraform Cloud API, and for Terraform Cloud Notifications. There are IPs for Sentinel and VCS, though those won’t fix this issue.
- The IPs for the runners are not shared publicly at this time as a means to protect users of Terraform Cloud and allow for optimizations that we can make for hosting runners on the SaaS platform.
- You are able to guarantee IPs for runners if you utilize the Terraform Cloud for Business tier, which allows for you to self-host Terraform Cloud Agents and this would be my recommendation for more control over your IP space utilization and network access control.
Please let me know if there’s anything more I can clarify to that end, and I hope that helps shed more light on why those issues arose when working with the Vultr provider and Terraform Cloud runs!