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!!
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 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.
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 have a Liberty Websphere application hosted on Bluemix that connects to Exchange Web Services. When I run this api on localhost it works fine and returns the desired results. But when I host it on bluemix, it returns the error
"500 Error: Failed to establish a backside connection"
No errors in the logs.
i have tried the solutions given in other posts and searched a lot on internet. But still not able to solve this issue.
Finally the problem is resolved. There was a configuration error in the application as my company's Bluemix server is on dev environment and the application was trying to connect to the prod environment.
When we connected using the dev IDs, from dev bluemix servers to dev exchange servers, the application works fine.
I signed up for the Bluemix trial, received the confirmation email, but both links in the email end up at this URL: https://idaas.ng.bluemix.net/idaas/public/tamlogin.jsp which never responds. Eventually the browser timesout with this message: The server at www-947.ibm.com is taking too long to respond.
This has been consistent for the past 2 weeks. Anyone seen this and know what the problem might be?
Can you please try to access Bluemix without VPN connection? I believe your issue is related to VPN client. If connecting to Bluemix without VPN works, please upgrade your VPN client to latest version and try to connect to Bluemix with VPN connection.