I'm trying to use new Connect & Compose service on Bluemix. Compose seems to work all right, but when I choose DB in "Connect", and then tried to proceed vi "Next" button. But I got "Failed to fetch list of bluemix services" error message. See the screenshot below.
Failed to fetch list of bluemix services
Is there any prerequisite setting or some issues with my space ? (I suspect the later, since I have multiple services in my spaces).
Thanks in advance !
I've just tried to use the Connect & Compose service on Bluemix and I managed to connect to a SQL Database instance previously bound to an application. I have many services in my space, too. Probably you're right, there is a problem with your space, I suggest you to open a ticket to Bluemix Technical Support. Please note that this is a new BETA service. Refer to Bluemix - Getting customer support for further information.
Related
I have been trying to create a Kubernetes Cluster with my Bluemix account owner but always getting the following error upon creation:
IBM Cloud Infrastructure exception: Your account is currently prohibited from order 'Computing Instances'.
Any idea what the issue is? There seems to be no direct way to getting support from Public Bluemix to address this issue. We opened a ticket but it has not been addressed.
You should contact IBM Bluemix Support for this kind of question. Before you login to the Bluemix Console, there is a Support link.
From the look of the exception. It seen like you are trying to create a "second" kubernetes cluster. If this is what you are trying to do, you will need a SoftLayer account; or your ID in your SoftLayer account is not setup properly.
You need admin rights to create clusters in Bluemix. Just makes sure that you get the admin status and it should work for you. The normal permissions granted to you are that of an user. Hope this helps
I have a BlueMix application using NodeRed and I want to sign up for the ElephantSQL service so I can store some tabular data, but when I browse to the service in the catalog I don't see any option to sign up. The only thing that is close is an option "connect to" which allows me to select one of my applications. However, selecting my target application does not sign me up for the service and when I browse back to the service I see it has forgotten my selection.
I understand and that is definitely the cause of the issue. Please open ticket with Bluemix Support so we can look into your account and resolve this issue:
https://console.ng.bluemix.net/docs/support/index.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'm trying to unbind & delete a Mongolabs service instance from my app in IBM Bluemix. Unfortunately, Bluemix displays the error:
BXNUI0035E The 'Mongolab-cv' service could not be deleted.
And leaves the service allocated and bound to my app.
How do I fix this?
Mike
The MongoLab service was deprecated last year. Service instances created before it were not deleted, but since the service broker is not available anymore you will not be able to delete or unbind this service.
Please raise a support ticket to get this service removed from your space.
To open a ticket check the link below:
ibm.biz/bluemixsupport
When opening a ticket provide your organization name, space and service name.
I am taking the DWC001 Bluemix Intro course exercise 3b. After creating a node.js app and binding a new Cloudant database, then deleted my app from dashboard, checked delete for Cloudant, my Cloudant service remains and I cannot delete it.
This error from Dashboard & cmdline:
Service instance RLCCloudant: Service broker error:
{"description"=>"Error 400 received from broker url
https://cloudantbroker.ng.bluemix.net/v2/service_instances/40791045-620f-
4fda-b9d4-eabe50c4783c?plan_id=cloudant-shared&service_id=cloudant"}
As you can see in the Bluemix Status Page we are currently experiencing some issues provisioning and managing Cloudant service instances in Bluemix. Bluemix users attempting to provision/unprovision/bind/unbind Cloudant service instances may see errors during these operations. The operations team has restored the service to allow provisioning, binding and unbinding. Issues may still be experienced when unprovisioning a service (as in your case).
Please visit that status page to see when the issues are resolved.
The service has been restored by Cloudant team as announced at https://developer.ibm.com/bluemix/support/#status.
Now the deletion action is working as normal.
"Service Broker Error" usually means that something went wrong communicating with the service side. Please send a request to delete the service to Bluemix Support.