Closed NovoJeep closed 4 years ago
@NovoJeep Thanks for the feedback! We are currently investigating and will update you shortly.
Hi @NovoJeep Tese issues are mostly for documentation feedback. Your question might be better suited for the developer forums like MSDN or StackOverflow where there is a community of developers that can help. Please share your link to the question here and I can help if you are not getting traction on the forum. Please make sure to clarify if white listing 8883 it's not an option? Or if MQTT over websocket is also not an option for you?
If you need urgent support please create a support ticket so you can get one on one help from a support engineer. (If you do not have access to a support plan please let me know and I can help you create a one time free support ticket)
Hi Alberto,
Thanks for that reply.
I already asked the Azure Support but the contact only said something like “No Way” which is not a solution for that problem.
Today I opened a Question at StackExchange (StackOverflow redirected me since it’s not a coding issue)
Best,
Julien
From: Alberto Vega notifications@github.com Sent: mardi 1 octobre 2019 00:40 To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Julien PLATRET jp@novolyze.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] How to change TCP Port? (#39655)
Hi @NovoJeephttps://github.com/NovoJeep this issues are mostly for documentation feedback. Your question might be better suited for the developer forums like MSDN or StackOverflow where there is a community of developers that can help. Please share your link to the question here and I can help if you are not getting traction on the forum, with that said if you need urgent support please create a support ticket so you can get one on one help from a support engineer. (If you do not have access to a support plan please let me know and I can help you create a one time free support ticket)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/39655?email_source=notifications&email_token=AHKEW5KJJLTKYDRBVHK2X7LQMJ53XA5CNFSM4I3DWC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD77KEYY#issuecomment-536781411, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHKEW5O76OJXL5L73CGPELDQMJ53XANCNFSM4I3DWC4A.
Strictement personnel et confidentiel: Ce message et toutes ses éventuelles pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur. L'Internet ne permettant pas d'assurer l'intégrité de ce message, Novolyze (et ses filiales et sociétés conjointes) décline(nt) toute responsabilité au titre de ce message, dans l'hypothèse où il aurait été modifié.
@NovoJeep Can you please share the support ticket number so I can take a look. also is white listing 8883 not an option for you? What about MQTT over websocket is that also not an option for you? I am trying to understand better your use case scenario constraints so I can reach out internally for help.
@Alberto Vegamailto:notifications@github.com unfortunately for adoption reason, we cannot ask customer to open TCP 8883 and on our side, the Equipment we use (which we don’t make) is only able to communicate with standard MQTT protocol without being encapsulated in Websockets…
From: Alberto Vega notifications@github.com Sent: mercredi 2 octobre 2019 02:45 To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Julien PLATRET jp@novolyze.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] How to change TCP Port? (#39655)
@NovoJeephttps://github.com/NovoJeep Is white listing 8883 not an option for you? What about MQTT over websocket is that also not an option for you?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/39655?email_source=notifications&email_token=AHKEW5KHRRMF54M77I4DQO3QMPVHLA5CNFSM4I3DWC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEADFZQI#issuecomment-537287873, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHKEW5PZNRI7IXBR62YDD4LQMPVHLANCNFSM4I3DWC4A.
Strictement personnel et confidentiel: Ce message et toutes ses éventuelles pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur. L'Internet ne permettant pas d'assurer l'intégrité de ce message, Novolyze (et ses filiales et sociétés conjointes) décline(nt) toute responsabilité au titre de ce message, dans l'hypothèse où il aurait été modifié.
@NovoJeep Thanks for confirming I will reach out internally for help. What are you planing to do with the Azure Functions? Can you please elaborate more on why the device can't use MQTT over websocket? You can't change the code?
Hi @NovoJeep can you please answer the questions from my previous post? I need the info so we can better help.
Sorry, it seems my latest replt did not reach the hub.
Unfortunately for customer adoption to our solution, we cannot asj them to open tcp port 8883 and the device we use but we do not make ryns its own operating system for which we don't have source code. This industrial device is also not able to use websocket, only mqtt but we can change tcp port.
@NovoJeep Since you can't modify the code you won't be able to authenticate to IoT Hub? Even without the port constraints your customer has?
@Alberto-Vega-MSFT I just found something called "Azure IoT Protocol Gateway" maybe this could help to fix my issue.
Will you able to do the authentication with Azure IoT Hub using that device?
I can connect to IotHub from my office but I had to open TCP8883 for that.
Okay I will be closing this issue for now. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Hello,
We have a "Device" which is only able to use standard MQTT which should use TCP Port 8883 as presented in this Page.
Our Device is to be installed in factories where usually Firewall Blocks this 8883 TCP Port but allows TCP Ports 80 and 443.
Today we have a Virtual Machine hosting a MQTT Broker which I could set to listen on TCP 443.
Now we would switch our app to IoT Hub and benefit of Azure Functions but I cannot find a way to configure this.
I had the idea to create a load balancer with NAT rules so the Device could go over the Internet through TCP 443 which would be NAT to 8883 of my Iot Hub.... Unfortunately the Load Balancer only allows this with a VM, not the IoT Hub.
Any other idea ? Solution? Procedure ?
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.