You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on a scenario, the following behavioral alternatives could be expected:
If there are other listeners available to reach out to API/status endpoints, use those instead.
If there are no other listeners, agent would seed proxy protocol payload while talking to specific sockets e.g. like curl does with --haproxy-protocol option (https://curl.se/docs/manpage.html#--haproxy-protocol).
Steps to Reproduce the Bug
Set up nginx or nginx-plus with proxy_protocol listeners (see the above example).
time="2025-02-11T15:23:02Z" level=warning msg="Unable to perform Stub Status API GET request: Get \"http://[::1]:8888/stub_status\": EOF"
time="2025-02-11T15:23:02Z" level=warning msg="Unable to perform Stub Status API GET request: Get \"http://127.0.0.1:8888/stub_status\": EOF"
time="2025-02-11T15:23:02Z" level=warning msg="Unable to perform NGINX Plus API GET request: Get \"http://[::1]:8888/api\": EOF"
time="2025-02-11T15:23:02Z" level=warning msg="Unable to perform NGINX Plus API GET request: Get \"http://127.0.0.1:8888/api\": EOF"
Environment Details
Target deployment platform: EC2 VM, local VM
Target OS: Ubuntu 22.04.5 LTS
Version of this project or specific commit: nginx-agent 2.39.0~jammy
Version of any relevant project languages: irrelevant
nginx version: nginx-plus-r33-p2
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Overview
Agent is unable to communicate with nginx listeners that are configured with proxy protocol enabled, e.g. in a configuration like this:
Expected Behavior
Depending on a scenario, the following behavioral alternatives could be expected:
--haproxy-protocol
option (https://curl.se/docs/manpage.html#--haproxy-protocol).Steps to Reproduce the Bug
proxy_protocol
listeners (see the above example).Environment Details
Additional Context
No response
The text was updated successfully, but these errors were encountered: