I followed the instructions on http://www.steves-internet-guide.com/install-mosca-mqtt-broker-node-red/ on IBM Cloud.
I installed the node-red-contrib-mqtt-broker, but got the error "unknown: mosca in".
Installation error in app log:
OK, so as the log states, Node-RED has been unable to install the node.
Your best bet is to edit the package.json for the app so it is installed during app staging then restage the app. The easiest way to do this is to enable continuous integration for your app. I've not used IBM-Cloud in a while, so you'll have to check the docs for how to do this.
It's probably also worth noting that you will not be able to access the MQTT broker from outside Node-RED when running the mosca node on IBM-Cloud. This is because the IBM-Cloud environment only exposes one port from any application. In Node-RED's case this is the HTTP port.
Related
I started using Node-Red from IBM Bluemix. I successfully created the Node-Red Starter plan and started working with Node-Red. After about a week of using my browser started responding with
This site can’t provide a secure connection mybluemixapp.us-south.cf.appdomain.cloud sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
I can access the URL from my companies network and the connection is secure. I have done a bit of googling and tried the solution post here
but no luck. Any ideas?
I'm trying to deploy a service fabric application to an unsecure Azure Service Fabric cluster. When I open the publish window in VS 2017 I get the following. If my cluster is unsecure, shouldn't I be able to publish it w/o configuring the cert?
I tried a publish anyways and I got:
Try accessing the server via powershell to maybe get a better error. Usually, errors like this are caused by firewalls blocking the port 19000.
I am trying to follow the poc as explained in the below link.Also I have followed the same steps and verified the same.
https://console.bluemix.net/docs/services/IoT/nodereddevice_sample.html#creating-and-connecting-a-node-red-device-simulator
The issue here is I am able to successfully deploy and send/Inject messages from the node-red flow editor.But in my IOT Console I am not able to see my messages in any of the event/Sensor logs.I am getting the below messages only in Connection logs:
**Token auth succeeded: ClientID='d:xxxx:xxxx:xxx', ClientIP=0.0.0.0
Closed connection from 0.0.0.0. The connection has completed normally**
Also I have made the TLS Settings optional in my Security settings Tab in IOT.
But still facing the same issue.
Please Advice..
Thanks!!
This article shows to how to secure the service fabric cluster in the Azure:
https://azure.microsoft.com/en-us/documentation/articles/service-fabric-visualstudio-configure-secure-connections/
But it makes no references as to how to configure developer's machine for the same. I tried to apply the same principles in the above link to see if I can make it work. It always fails to deploy services locally but works like a charm when I publish them to azure's service fabric cluster. If I remove the secure bindings, I can deploy services to local cluster successfully. But this becomes tedious whenever I want to publish the services to the azure's secure cluster.
Does any one have an idea as to how to go about creating a secure service fabric cluster on developer's machine?
I am using Service Fabric version 5.5.216.0 and it seems to be working. Run powershell command:
PS C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup> .\DevClusterSetup.ps1 -PathToClusterDataRoot "C:\SfDevCluster\Data" -PathToClusterLogRoot "C:\SfDevCluster\Log" -AsSecureCluster
Then, open IE to browse "https://localhost:19080/Explorer/". You will see a popup asking you to choose which client certificate to connect. Use the one with name 'ServiceFabricDevClusterCert'. Chrome didn't work for me as it failed directly with no useful warning. Maybe somewhere in chrome I should enable popup window?
I'm just confused on how CloudFoundry exactly works.
So if I create a service, will it be hosted on their cloud and I can expect it to run indefinitely?
Yes, CloudFoundry will host your service and it will run as long as they are up, but to access it you must bind the service to an app.
The concept of service in Cloud Foundry is quite open, it can refer to an app running in CF or outside, e.g. somewhere on the local network or on AWS or anywhere else.
I recently wrote a blog entry about how you can turn an existing app into a CF service, you might find it useful.