Skip to content

Commit 87dd670

Browse files
committed
Combine monikers to fix indent code block issue
1 parent 773affb commit 87dd670

File tree

1 file changed

+15
-25
lines changed

1 file changed

+15
-25
lines changed

articles/iot-edge/how-to-configure-proxy-support.md

Lines changed: 15 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -280,13 +280,13 @@ This step takes place once on the IoT Edge device during initial device setup.
280280

281281
2. In the config file, find the `[agent]` section, which contains all the configuration information for the edgeAgent module to use on startup. Check and make sure that the `[agent]`section is uncommented or add it if it is not included in the `config.toml`. The IoT Edge agent definition includes an `[agent.env]` subsection where you can add environment variables.
282282

283-
3. Add the **https_proxy** parameter to the environment variables section, and set your proxy URL as its value.
284-
285283
:::moniker-end
286284

287285
<!-- 1.3 -->
288286
:::moniker range="=iotedge-2020-11"
289287

288+
3. Add the **https_proxy** parameter to the environment variables section, and set your proxy URL as its value.
289+
290290
```toml
291291
[agent]
292292
name = "edgeAgent"
@@ -300,51 +300,41 @@ This step takes place once on the IoT Edge device during initial device setup.
300300
# "UpstreamProtocol" = "AmqpWs"
301301
"https_proxy" = "<proxy URL>"
302302
```
303-
:::moniker-end
304303

305-
<!-- 1.4 -->
306-
:::moniker range=">=iotedge-1.4"
304+
4. The IoT Edge runtime uses AMQP by default to talk to IoT Hub. Some proxy servers block AMQP ports. If that's the case, then you also need to configure edgeAgent to use AMQP over WebSocket. Uncomment the `UpstreamProtocol` parameter.
307305

308306
```toml
309-
[agent]
310-
name = "edgeAgent"
311-
type = "docker"
312-
313307
[agent.config]
314-
image = "mcr.microsoft.com/azureiotedge-agent:1.4"
308+
image = "mcr.microsoft.com/azureiotedge-agent:1.3"
315309
316310
[agent.env]
317311
# "RuntimeLogLevel" = "debug"
318-
# "UpstreamProtocol" = "AmqpWs"
312+
"UpstreamProtocol" = "AmqpWs"
319313
"https_proxy" = "<proxy URL>"
320314
```
321315

322316
:::moniker-end
323317

324-
<!-- >= 1.3 -->
325-
:::moniker range=">=iotedge-2020-11"
326-
327-
4. The IoT Edge runtime uses AMQP by default to talk to IoT Hub. Some proxy servers block AMQP ports. If that's the case, then you also need to configure edgeAgent to use AMQP over WebSocket. Uncomment the `UpstreamProtocol` parameter.
328-
329-
:::moniker-end
318+
<!-- 1.4 -->
319+
:::moniker range=">=iotedge-1.4"
330320

331-
<!-- 1.3 -->
332-
:::moniker range="=iotedge-2020-11"
321+
3. Add the **https_proxy** parameter to the environment variables section, and set your proxy URL as its value.
333322

334323
```toml
324+
[agent]
325+
name = "edgeAgent"
326+
type = "docker"
327+
335328
[agent.config]
336-
image = "mcr.microsoft.com/azureiotedge-agent:1.3"
329+
image = "mcr.microsoft.com/azureiotedge-agent:1.4"
337330
338331
[agent.env]
339332
# "RuntimeLogLevel" = "debug"
340-
"UpstreamProtocol" = "AmqpWs"
333+
# "UpstreamProtocol" = "AmqpWs"
341334
"https_proxy" = "<proxy URL>"
342335
```
343336

344-
:::moniker-end
345-
346-
<!-- 1.4 -->
347-
:::moniker range=">=iotedge-1.4"
337+
4. The IoT Edge runtime uses AMQP by default to talk to IoT Hub. Some proxy servers block AMQP ports. If that's the case, then you also need to configure edgeAgent to use AMQP over WebSocket. Uncomment the `UpstreamProtocol` parameter.
348338

349339
```toml
350340
[agent.config]

0 commit comments

Comments
 (0)