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.

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

Dogstatsd getting 403 with proxy configured. #1514

Closed
conorbranagan opened this issue Apr 6, 2015 · 0 comments · Fixed by #1518
Closed

Dogstatsd getting 403 with proxy configured. #1514

conorbranagan opened this issue Apr 6, 2015 · 0 comments · Fixed by #1518

Comments

@conorbranagan
Copy link
Contributor 

2015-04-06 11:42:09 PDT | DEBUG | dd.dogstatsd | dogstatsd(dogstatsd.py:202) | Posting payload to http://localhost:17123/api/v1/series?api_key=API_KEY
2015-04-06 11:42:09 PDT | ERROR | dd.dogstatsd | dogstatsd(dogstatsd.py:218) | Unable to post payload.
Traceback (most recent call last):
  File "/opt/datadog-agent/agent/dogstatsd.py", line 208, in submit_http
    r.raise_for_status()
  File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/requests/models.py", line 825, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
HTTPError: 403 Client Error: Forbidden
2015-04-06 11:42:09 PDT | ERROR | dd.dogstatsd | dogstatsd(dogstatsd.py:220) | Received status code: 403
2015-04-06 11:42:09 PDT | DEBUG | dd.dogstatsd | aggregator(aggregator.py:689) | Received 0 events since last flush
2015-04-06 11:42:09 PDT | DEBUG | dd.dogstatsd | aggregator(aggregator.py:700) | Received 0 service check runs since last flush

The forwarder does not show any transactions coming in so it seems likely that the proxy is returning a 403, despite the fact that dogstatsd is supposed to override the proxy.

Case with full logs and config: https://datadog.zendesk.com/agent/tickets/24202
remh pushed a commit that referenced this issue Apr 7, 2015
[Core] Do not use proxy for local connections
38ee79a 
Starting with Agent 5.0.0, there should always
be a local forwarder running and all payloads
should go through it.

So we should make sure that we pass the no_proxy
environment variable that will be used by requests

See: https://github.com/kennethreitz/requests/pull/945

Fix #1514
@remh remh mentioned this issue Apr 7, 2015
Merged
remh pushed a commit that referenced this issue Apr 8, 2015
[Core] Do not use proxy for local connections
ef3f417 
Starting with Agent 5.0.0, there should always
be a local forwarder running and all payloads
should go through it.

So we should make sure that we pass the no_proxy
environment variable that will be used by requests

See: https://github.com/kennethreitz/requests/pull/945

Fix #1514
@remh remh closed this as completed in #1518 Apr 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Core] Do not use proxy for local connections DataDog/dd-agent
1 participant
@conorbranagan