IBM Cloud Error: 502 Bad Gateway: Registered endpoint failed to handle the request

  • 26 Feb, 2019

I setup the connection to cloudant service to store historical data of my IoT devices. When i click “done” an pop up window appears asking to authorize the connection to Cloudant Service. I confirm to authorize and i get the message 502 Bad Gateway: Registered endpoint failed to handle the request. and i can’t store iot device data on cloudant. I tried several times.

I search a lot about this error message with no luck .  To solve the problem erase all IBM cookies from you browser and restart it.

PrevNext

Related Posts

5 Podman Features You Should Know: Kubernetes & Containers Simplified

5 Podman Features You Should Know: Kubernetes & Containers Simplified

  • 23 Apr, 2026

Você já sentiu que gerenciar containers é como tentar resolver um quebra-cabeça de mil peças, onde metade delas parece não se encaixar? Muitas vezes, a complexidade das permissões de sistema e a curv

5 Podman Features You Should Know: Kubernetes & Containers SimplifiedRead More

Create AWS S3 bucket to backup OpenShift projects using IBM Storage Fusion

  • 03 Apr, 2025

To create an AWS S3 bucket to use as a backup location for IBM Storage Fusion, you need to configure the bucket in AWS and ensure that it is properly configured for compatibility with IBM Storage Fusion. Below are the steps to achieve this: Step 1: Sign in to the AWS Management Console 1. Sign in aws.amazon.com(https://aws.amazon.com) and sign in to your AWS account using your credentials. 1. After you sign in, navigate to the AWS Management Console. Step 2: Access the S3 service 1. In the AWS Management Console, use the search bar at the top and enter S3. 1. Select S3 from the results to open the Amazon S3 dashboard. Step 3: Create an S3 bucket 1. From the S3 dashboard, click the Crea

Create AWS S3 bucket to backup OpenShift projects using IBM Storage FusionRead More

Error when login using CP4Data CLI command line

  • 06 Mar, 2023

Today i got the following error when i try to run the command :
./cpd-cli manage login-entitled-registry ${IBMENTITLEMENTKEY} Run command: podman run -d --name olm-utils-play --env CMD\PREFIX=manage -v /opt/cpd-cli-linux-EE-12.0.2-39/cpd-cli-workspace/olm-utils-workspace/work:/tmp/work icr.io/cpopen/cpd/olm- utils:latest\ERROR\ 2023-03-06T12:41:55.991666Z Command exception: Failed to start the olm-utils-play container: Error: runc: container\linux.go:370: starting container process caused: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied (exit status 126)\ERROR\ 2023-03-06T12:41:55.998354Z RunPluginCommand:Execution error: exit status 1 This

Error when login using CP4Data CLI command lineRead More