After login into IBM Watson IoT Platform. I get this error message.
Invalid session
The session is invalid or has expired. Repeat the process.
Logging out and logging in several times did not correct the error.
Yesterday I was still able to process data in the IBM Watson IoT Platform.
Why happens and how do I fix the error?
Related
I am trying to use node-red to connect to my Watson chatbot using the Watson assistant v2 node. For some reason, I keep getting forbidden returns and It doesn't seem to connect properly? Has anyone managed to successfully connect to a Watson service using Node-red?
I am not sure the correct combination of API key or ID to connect to the correct service
In the Watson Assistant UI go to the Assistant you want to use, then to the Settings section. The Assistant ID and URL are shown, then in the Service credentials section the API key.
Enter them in the configuration of your node.
For those who came late for this question:
To use IBM watson node-red nodes
search for the service in IBM cloud.
Create the service.
Get the credentials.
Go to node-red editor and paste the credentials (API key + URL)
I'm using IBM Cloud Node-Red and I'm trying to connect speech to text to my Node Red instance. I keep getting the following message "BXNUI0033E: The 'node-red-speechtotext-1590542039496' service wasn't added to the 'Node RED' app because a problem occurred contacting the resource controller.
Try again later. If you see this message again, go to the IBM Cloud status page to check whether a service or component has an issue. If the problem continues, go to IBM Cloud Support." Any suggestions?
Our access to the api that has run for years suddenly stopped working and returns {"code":401, "error": "Unauthorized"}
There is no issue with signing into the account, charges or resource usage.
The only previous interruptions were when IBM purchased the original vendor and again when IBM changed some access requirements.
The application is .NET C# and the api returns title, author, and text from urls.
How can we find the cause of the interruption?
Thanks
This is a duplicate of The old Watson Conversation API (21st Apr 2017 version) seems to have stopped working. Gives me the 401 Unauthorized error and How to know if an application is using Cloud Foundry?
The answer is the same :
IBM Cloud is switching off any services that have not been migrated to a resource group. The Watson services were part of the first batch affected. You will need to migrate your instance to IAM, then use the generated IAM key for authentication.
If you need to migrate from Cloud Foundry, see Migrating Watson services from Cloud Foundry.
You can find out details about the service instance that you are using by clicking the service instance in your Resource list on IBM Cloud and looking at the credentials.
I have deployed the Bluemix GeoSpatial starter application in Bluemix.
It works fine until I want to connect to the Watson IoT Platform instead of the demo MQTT server.
I changed mqtt1.m2m4connectedlife.com to dzqml6.messaging.internetofthings.ibmcloud.com and added mqtt_uid and mqtt_pw to the start parameters jsonObject.
I created an API key in the Watson IoT Platform Dashboard and used these values for mqtt_uid and mqtt_pw.
Then I get an "Error: Connection refused: Not authorized" in the log when starting the application.
Then I also tried the apiKey and apiToken form the Watson IoT Platform environment variables for mqtt_uid and mqtt_pw but still got the same error.
I also tried different values for clientid and notify/input topics but without success.
I read a couple of other posts with similar errors that were resolved after some time because of a delay between when an organization is created and is distributed to all servers.
https://developer.ibm.com/answers/questions/163862/iot-cloud-error-not-authorized.html
So I waited a day but still have the same error.
I also added myself as a permanent member to the organization as suggested in this post: Refused: not authorized error occurs with IBM IoT Foundation on Bluemix
I would be very gratefull for any assistance on this!
There's a part of the Node.js code in the starter app that directly subscribes to the notify topic. Is the auth error coming from that subscription attempt? If so, did you modify that part of the code to pass credentials?
Here are the lines of code in the app.js that I'm referring to.
var clientId = 'geo-quickstart:' + port;
//create the MQTT client and subscribe
client = mqtt.createClient(1883,"mqtt1.m2m4connectedlife.com", { "clientId": clientId } );
console.log("Subscribing to topic: " + notify_topic_string + "\n");
client.subscribe(notify_topic_string);
If you aren't passing the credentials on the createClient call, try adding a parameter {username: "user", password: "pass"} to the list of arguments.
When you make an MQTT connection by using an API key, ensure that the following points apply:
The MQTT client ID is in the format: a:orgId:appId
The MQTT user name is the API key: such as a-orgId-a84ps90Ajs
The MQTT password is the authentication token: such as MP$08VKz!8rXwnR-Q*
See the documentation for more details. If you still experience errors, let us know your 6 character org ID for the IoT service and we can check logs to troubleshoot why you are getting authorization error.
When I attempt to connect to the IBM IoT Foundation with a registered device, I receive the following error message:
Error connecting to IBM IoT: {"errorCode":6,"errorMessage":"AMQJS0006E Bad Connack return code:5 Connection Refused: not authorized."}
How do I resolve this problem?
It is possible that you have expired as a member of your org if you created the service (and thereby the org) via the Bluemix dashboard. When you log into Bluemix, you get a 24 hour pass as a guest. You can then go into the IoTF dashboard and add yourself as a permanent member.
Do this by launching the IoTF dashboard from your Bluemix IoT service and then go to the Access tab. You should see yourself as a "guest" user, and you can add yourself as a permanent member. From the Access tab, add yourself as a permanent member of the org.
Yeah, maybe just API attempts for trial are out?
CHeck in Bluemix panel