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.

Sign up for GitHub

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

Jump to bottom

Error accessing infoblox thru https proxy #28

Closed

vrvenky1407 opened this issue Apr 22, 2019 · 4 comments

vrvenky1407 commented Apr 22, 2019

Error accesing infoblox using http/https proxy

I am getting the following error when I run plan.
Error: Error running plan: 1 error(s) occurred:

provider.infoblox: Get https://xxxx.xxxx.com:443/wapi/v2.7/userprofile?_proxy_search=GM&_return_fields=name: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

I have specified my infoblox IPAM ipaddress and dnsname in no_proxy host env varaible still it is not able to connect. Please let me know how to handle this problem.

Contributor

saiprasannasastry commented Apr 23, 2019

Hi , proxy search is used for CP Member, the current plugin is not supported on CP Member

Author

vrvenky1407 commented Apr 25, 2019 •

edited

Loading

This is for allocating IP Address to on-prim VSphere environment. Why is the infoblox provider trying to connect thru proxy when I have specified my infoblox IP Address and its dns name in no_proxy environment variable.

How to avoid proxy search by the provider?

AvRajath added a commit that referenced this issue


          Merge pull request #28 from AliaksandrDziarkach/fix_acctest_error_mes…

e90f811

…sage

Fix acctest error message

Contributor

somashekhar commented Mar 5, 2021

Are you still working on this use case ? Let us know if you need support on this issue.

Contributor

somashekhar commented Mar 12, 2021

Will be closing the issue with above discussion. Do contact us if incase you face the issue again.

somashekhar closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment