i fallowed this tutorial
https://github.com/ARM-software/Cloud-IoT-Core-Kit-Examples/blob/master/readme.md
to connect my Pi to google cloud iot core, but when i tried to add repository with this command
sudo gcloud components repositories add https://storage.googleapis.com/cloud-iot-gcloud/components-2.json
i got this massage : ERROR: (gcloud.components.repositories.add) Account [tiosahelal#gmail.com] does not have permission to install this component.
but when i skipped that part of the tutorial, i can make new devices in google cloud iot, but when i test it with this tutorial https://github.com/ARM-software/Cloud-IoT-Core-Kit-Examples/tree/master/CPUTemp
i got :
('on_connect', '5: The connection was refused.')
('on_disconnect', '5: The connection was refused.')
You no longer should need to use alpha components with Google Cloud IoT Core because the components appear in Beta.
For example:
gcloud beta iot registries list --region=us-central1
For the connection refused issue, make sure to double check all of the MQTT settings:
username is ignored
mqtt.googleapis.com is the host, port 8883 or 443 (maybe try 443?)
Client ID is: projects/{project-id}/locations/{cloud-region}/registries/{registry-id}/devices/{device-id}
If any of the configurations is incorrect, you will be unable to connect. Also, make sure that your device certificate, used when you added your device to your device registry, has not expired.
Related
when i try to register with the authentication keys, im getting the below error
enter image description here
It seems you hit some network issue. Maybe you can check if you have whitelist azure's IP range.
A connection to the service back end is not possible for the self-hosted IR. Most often, the firewall, DNS, or enterprise network settings are to blame for this problem.
To resolve this
Check to see whether the integration runtime service is running. if it is running and no proxy is configured on the self-hosted IR run the below command in your Windows PowerShell, I will give you glimpse of error.
Code from Microsoft document
(New-Object System.Net.WebClient).DownloadString("https://demofactorypratik.eastus.datafactory.azure.net/")
You can get the above link form Integration runtimes > your self-hosted IR > Nodes > View Service URLs.
Expected result:
If you get a "Remote name could not be resolved" message, there's a DNS issue. if you get an "ssl/tls cert is not trusted" message, then install the public certificate by using Certificate Manager. Go to Event viewer (logs) > Applications and Services Logs > Integration Runtime, here you can find check what's the exact issue.
I can successfully be able to connect Self-hosted IR
Also see, Self-hosted IR connectivity issues
I got the following error when trying to use a Notary client to get the digest of a signed image in my IBM Container Registry. Can anyone advise how to solve it?
# notary -s https://us.icr.io:4443 lookup us.icr.io/securek8s/hello-world latest
* fatal: unauthorized: The login credentials are not valid, or your IBM Cloud account is not active.
BTW, I built the Notary client from https://github.com/theupdateframework/notary
Notary uses your credentials from your Docker login cache. The error message that you received suggests that your login to us.icr.io isn't valid. This usually means that your credentials have expired.
If you have the ibmcloud CLI and the container-registry plugin installed, you can refresh your login by making sure that you're targeting the US South registry (ibmcloud cr region-set us.icr.io) and then logging in with ibmcloud cr login.
If you don't have the CLI plugin installed, you can log in using Docker commands directly. For more information, see Automating access to IBM Cloud Container Registry
in the IBM Cloud docs.
Recently, I started seeing an issue when trying to setup secure gateway within API Connect on IBM Cloud, I previously had it working but looks like they changed this wizard interface and its broken since then
here is what I did to recreate the issue:
Setup new APIC instance on IBM Cloud
API connect Manager UI > Admin > Secure Gateways > Add (name & save)
once created, in Secure Gateway Clients section, click on +Set Up
I see no ID or Token generated
no matter what type of client I choose (DataPower, Docker or Installer)
Anyone facing the same issue?
Empty ID and Token when trying to setup Secure Gateway Client
turned out that creating SecureGateway from within the APIC is deprecated feature anyway.
you will need to create standalone SecureGateway resource on Bluemix and call it from your API assembly.
here is the instructions
https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.apionprem.doc/task_api_secure_gateway.html
Hi I am trying to deploy the Custom Login application give in
Github
to Bluemix I deployed the .wlapp to the container. But I could not deploy the AuthAdapter provided. It is failing to get deployed.
Keeping that aside I tried to deploy the starter application provided in the
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/sample-app/
It is giving Error shown is as below
The request is coming to my localhost mobilefirst server
What should I do to solve this problem and get the apps deployed on bluemix mfp container
How to deploy custom auth adapters which is not getting deployed to Bluemix
You did not mention if you are using the pre-configured evaluation container, or your own container.
Pre-configured: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/evaluate/
Your own container: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/run/
You can't open a question and say "deployment fails". It's not going to help anyone solve your problem. mention the error you're getting during the deployment attempt.
An "auth adapter" implies it is using some security test(s). If your server on Bluemix (see "your own container") was not configured correctly with said security test(s) in its authenticationConfig.xml file, this could fail an adapter deployment.
The screen shot in your question clearly shows a CORS issue. Chrome does not allow CORS (attempting to get data for different domains).
Make sure that your application points to the correct server - not your local host one, since you want to use your Bluemix server, right? So in its worklight.plist file or wlclient.properties file, make sure the wlHost property is pointing to the correct server.
I am following this tutorial for connecting Raspberry Pi to AWS IoT using Node.js SDK. I see the following in vim ~/.aws/credentials
[default]
aws_access_key_id = SOMETHING
aws_secret_access_key = SOMETHINGELSE
When I enter the command aws iot describe-endpoint I get the following response:
{
"endpointAddress": "A34SXNTM6AT7XH.iot.us-west-2.amazonaws.com"
}
However when I browse to that URL: https://a34sxntm6at7xh.iot.us-west-2.amazonaws.com/
I get the following error:
Missing Authentication Token
Any idea what could be wrong and how could it be solved?
Here's the files in the ~/certs folder:
pi#raspberrypi:~/certs $ ls
certificate.pem.crt private.pem.key public.pem.key root-CA.pem
Mona,
Your custom endpoint responds to two protocols: MQTT and HTTPS. However, it does not serve any web content and thus does not work in the browser as a site URL. The "endpointAddress" you get from aws iot describe-endpoint will be plugged into your Node.js Device SDK that you're using in the Raspberry Pi example you linked (no https://).
You can also interface with device shadows using the HTTPS version of the endpoint by signing requests with AWS Signature version 4. More on that here: http://docs.aws.amazon.com/iot/latest/developerguide/thing-shadow-rest-api.html and here: http://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html though you will likely get going faster by using the AWS CLI or AWS SDK to perform operations like this.
Ryan # AWS
By default, the example programs will look in the current directory for your certificate and private key files, but you can also use the '-f' option to specify another directory if you want to. As for the 'Missing Authentication Token' message you noticed when trying to access the endpoint from your browser, you can safely ignore it.
If you use "TLS mutual authentication" you need to connect on port 8443, so in your example, it would be https://a34sxntm6at7xh.iot.us-west-2.amazonaws.com:8443/things/<thing_name>/shadow