Closed kiranpradeep closed 5 years ago
@kiranpradeep thanks for the feedback. You could find the setting steps of iotedge runtime in proxy scenario at https://docs.microsoft.com/en-us/azure/iot-edge/how-to-configure-proxy-support
Can you try whether it helps?
@adashen I had checked the link earlier and it is about setting proxy in production iotedge runtime. The closest that link get to is the UpstreamProtocol: AmqpWs option in configuring iotedgeagent (link). But edgehubdev doesn't use that config.yaml.
@kiranpradeep iotedgehubdev does not use edgeAgent, so there is no need to config config.yaml. And you can follow https://docs.microsoft.com/en-us/azure/iot-edge/how-to-configure-proxy-support#json-deployment-manifest-files to config the "edgeHub" module in JSON deployment manifest.
@adashen Thanks. That helped. After setting _httpsproxy and UpstreamProtocol (amqpws) env variables, I was able to use edgehubDev behind http proxy.
But, that works only when I start in simulator mode with deployment manifest template. When I start edgehubDev for single module debugging, the env variables are not in effect (verified with docker inspect edgeHubDev) and so edgeHubDev cannot connect over proxy. How to set the env variables with edgeHubDev so that single module debugging works on machines behind http proxy?
@kiranpradeep The latest version 0.10.0 has just added the support for env in single module debugging. (https://github.com/Azure/iotedgehubdev/releases/tag/v0.10.0) You could use "-e" option to add the envs when starting the simulator.
I am trying to get edgehubdev working over a http proxy. But that needs edgehubdev to use amqp over websockets. How to specify that while starting iotedgehubdev ?