Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error installing provider "aws": Get https://releases.hashicorp.com/terraform-provider-aws/: x509: certificate has expired or is not yet valid. #18944

Closed
shishirkumar2104 opened this issue Sep 26, 2018 · 8 comments

Comments

@shishirkumar2104
Copy link

Terraform Version

[root@localhost terraform]# terraform init

Initializing provider plugins...
- Downloading plugin for provider "aws"...

Error installing provider "aws": Get https://releases.hashicorp.com/terraform-provider-aws/: x509: certificate has expired or is not yet valid.

Terraform analyses the configuration and state and automatically downloads
plugins for the providers used. However, when attempting to download this
plugin an unexpected error occured.

This may be caused if for some reason Terraform is unable to reach the
plugin repository. The repository may be unreachable if access is blocked
by a firewall.

If automatic installation is not possible or desirable in your environment,
you may alternatively manually install plugins by downloading a suitable
distribution package and placing the plugin's executable file in the
following directory:
    terraform.d/plugins/linux_amd64

[root@localhost terraform]# uname
Linux

Got this error while running terraform init command on Linux (Centos )

Terraform Configuration Files

...

Debug Output

Crash Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

@bennycornelissen
Copy link

Can you share a bit more info about the machine? Which version of CentOS are you running? Is it configured to use NTP? Especially virtual machines tend to have quite a bit of time drift without proper configuration of either NTP or clocksource syncing. That’s the angle I would consider first if it’s a VM.

@shishirkumar2104
Copy link
Author

I am using - Centos 6.10
[root@localhost ~]# cat /etc/centos-release
CentOS release 6.10 (Final)
[root@localhost ~]#
[root@localhost ~]# cat /proc/version
Linux version 2.6.32-696.10.2.el6.x86_64 (mockbuild@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Tue Sep 12 14:33:29 UTC 2017

The system does not have NTP settings. Its date is set to couple of months before.

@shishirkumar2104
Copy link
Author

I set the date to current date. Now I am getting below error -
[root@localhost terraform]# terraform plan
Error asking for user input: 1 error(s) occurred:

  • provider.aws: dial unix /tmp/plugin753287081|netrpc: connect: no such file or directory
    [root@localhost terraform]#

@bennycornelissen
Copy link

Which version of Terraform are you running? You may be running into this issue: hashicorp/terraform-provider-aws#2121

@mildwonkey
Copy link
Contributor

@shishirkumar2104 - are you still having an issue with this, or can this be closed?

@mildwonkey mildwonkey added the waiting-response An issue/pull request is waiting for a response from the community label Oct 26, 2018
@fabiolimanunes
Copy link

you need sudo terraform init ,

@ghost ghost removed the waiting-response An issue/pull request is waiting for a response from the community label Jun 19, 2019
@apparentlymart apparentlymart added the waiting-response An issue/pull request is waiting for a response from the community label Jun 19, 2019
@hashibot
Copy link
Contributor

Hello again!

We didn't hear back from you, so I'm going to close this in the hope that a previous response gave you the information you needed. If not, please do feel free to re-open this and leave another comment with the information my human friends requested above. Thanks!

@ghost
Copy link

ghost commented Aug 15, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 15, 2019
@ghost ghost removed the waiting-response An issue/pull request is waiting for a response from the community label Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants