[{"data":1,"prerenderedAt":58},["ShallowReactive",2],{"changelog-entry-\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support":3},{"id":4,"title":5,"body":6,"description":5,"extension":46,"meta":47,"navigation":53,"path":54,"seo":55,"stem":56,"__hash__":57},"changelog\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support.md","Running the Device Agent behind an HTTP proxy",{"type":7,"value":8,"toc":42},"minimark",[9,13,16,24,31],[10,11,12],"p",{},"The FlowFuse Device Agent allows you to manage your Node-RED instances wherever you want them to run.\nIt connects back to the platform over a secure https connection.",[10,14,15],{},"For some enterprise customers, that has posed a challenge as they protect their network with an HTTP proxy that all traffic\nhas to be directed to.",[10,17,18,19,23],{},"With the ",[20,21,22],"code",{},"2.5.0"," release of the Device Agent, we now support running the Device Agent behind a proxy - letting it run in even more locations.",[10,25,26,27,30],{},"Support comes using the industry standard set of ",[20,28,29],{},"http_proxy"," environment variables - familiar to anyone running services behind a proxy.",[10,32,33,34,41],{},"Full details are available in our ",[35,36,40],"a",{"href":37,"rel":38},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Frunning\u002F#running-behind-a-http-proxy",[39],"nofollow","http proxy documentation",".",{"title":43,"searchDepth":44,"depth":44,"links":45},"",2,[],"md",{"date":48,"authors":49,"tags":51},"2024-06-18 13:00:00.0",[50],"nick-oleary",[52],"changelog",true,"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support",{"title":5,"description":5},"changelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","4XfCyeP-EIXy9X1s6a_eqevkMGd-U7MRkdk6jCANW50",1780132422692]