Hello Team,

Following faulty behaviour has been noticed when adding the “Nginx by HTTP” template to a host: The {HOST.CONN} macro is resolved to different values when testing the HTTP Agent item in the frontend and when its actually used by the server which leads to confusing results.

Steps to reproduce:

1. Create host with 2 Agent interfaces
2. Link the "Nginx by HTTP" Template and change the Items created by it (not dependent ones) so that they use the non default Agent interface
3. The “Nginx: Get stub status page” Item uses the {HOST.CONN} macro to connect to the status page
4. Test the Item in the Frontend → Macro is resolved to the IP of the Interface assigned to the Item → Test works as expected
5. Check the Item in the frontend without testing it → Error message saying the connection to the default interface of the host (not the one assigned to the Item) got refused

Result:
Inconsistent behaviour between what the server is doing and the result a user gets when testing the item in the frontend - {HOST.CONN} macro assigning correct interface during the frontend test when "Host Interface" indicates different interface than default one, but in the reality server is picking up the default interface for the data collection anyway.

Expected:
Consistent behaviour between what the server is doing and the result a user gets when testing the item - enable "Host Interface" field to make {HOST.CONN} macro use different interface than default one if selected so.