MID Server behind Corporate Proxy: REST Pattern F5 2.0 failing with "HTTP response: null" despite OS

[manuelpietrucci]

Hi everyone,

I am facing an issue with an F5 2.0 pattern discovery via a MID Server running on a Linux server, which is behind a corporate proxy.

The Problem:
Discovery fails at the authentication step with "HTTP response: null".

Troubleshooting performed:

OS-level connectivity: I verified that the MID Server host can successfully reach the F5 API using curl. It returns a 401 Unauthorized, confirming the network path is open and there is no firewall block.

The "Null" issue: ServiceNow Discovery logs consistently show "HTTP response: null" followed by an exception (Cannot invoke "Object.getClass()" because "o" is null). It seems the Java process is struggling to route traffic through the proxy for this specific endpoint.

Attempted mitigations: I tried configuring no_proxy (systemd/wrapper), but the MID Server ignores these overrides.

I have some doubts regarding the discovery approach and the information provided by the client:

Is the provided information sufficient? The client provided the F5 Management IP/URL and a read-only user for the REST API. Is there anything else usually required for F5 2.0 patterns (e.g., specific iControl REST port requirements, or specific authentication types)?

What is the recommended best practice for F5 API discovery in proxy environments?

Is the "HTTP response: null" indicative of a specific pattern failure or just a proxy issue?

I want to avoid using SNMP as the visibility would be insufficient. Any guidance on how to correctly configure the F5 2.0 pattern discovery or feedback on the sufficiency of the provided credentials would be highly appreciated.

Thanks in advance!