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

Can't contact API, getting 302 because of corporate proxy #873

Open
pelacables opened this issue Apr 3, 2023 · 0 comments
Open

Can't contact API, getting 302 because of corporate proxy #873

pelacables opened this issue Apr 3, 2023 · 0 comments

Comments

@pelacables
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 6.28
  • Ruby: 2.5.9p229
  • Distribution: RH8
  • Module version: 9.2.0

How to reproduce (e.g Puppet code you use)

run the zabbix server behind a corporate proxy where no_proxy needs to be configured. even if it want to talk to itself as it's the case.
Otherwise the API call is routed through the proxy and the zabbix provider shows a HTTP 302 error

IOW, curl bi-bio-zabbix.domain.com without no_proxy set and run from bi-bio-zabbix.domain.com goes first to the corporate proxy.

What are you seeing

Error: Could not prefetch zabbix_host provider 'ruby': HTTP Error: 302 on https://bi-bio-zabbix.domain.com/api_jsonrpc.php
Error: Failed to apply catalog: HTTP Error: 302 on https://bi-bio-zabbix.domain.com/api_jsonrpc.php

What behaviour did you expect instead

API reached.

Output log

Any additional information you'd like to impart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant