vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain that is not proxied.







 Error 525: SSL handshake failed 

525 errors are often caused by a configuration issue on the origin web server. Error 525 occurs when these two conditions are true:



1. The SSL handshake fails between CIS and the origin web server
2. Your TLS setting is End-to-end flexible, End-to-end CA Signed or HTTPS only origin pull





 Error 525 resolution 

Check your origin web server error logs to eliminate these common causes at your origin web server:



* No valid SSL certificate installed
* Port 443 (or other custom secure port) is not open
* No SNI support
* The cipher suites accepted by Cloudflare do not match the cipher suites supported by the origin web server



If 525 errors occur intermittently, review the origin web server error logs to determine the cause. Configure Apache to log mod_ssl errors. You might be able to get SSL errors in your NginX standard error log, but might need an increased log level.







 Error 526: invalid SSL certificate 

Error 526 occurs when the following two conditions are true:



1. CIS cannot validate the TLS certificate at your origin web server
2. Your TLS setting is End-to-end CA Signed or HTTPS only origin pull





 Error 526 resolution 

Set your TLS to End-to-end flexible instead of End-to-end CA Signed or HTTPS only origin pull to see if that fixes the error.

Review the origin web server’s TLS certificates and verify that:



1. The certificate is not expired
2. The certificate is not revoked
3. The certificate is signed by a Certificate Authority (not self-signed)
4. The requested or target domain name and hostname are in the certificate's Common Name or Subject Alternative Name
5. Your origin web server accepts connections over port 443
6.
(https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_lb_healthcheckvpc_lb_healthcheck)

[VPC clusters: Why can't my app connect via load balancer?](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_ts_lbvpc_ts_lb)

[VPC clusters: Why does a Kubernetes LoadBalancer service fail with no IPs?](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_no_lbvpc_no_lb)

[Why do I see SyncLoadBalancerFailed errors when creating a VPC cluster?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-loadbalancer-sync-failedts-loadbalancer-sync-failed)





 Ingress and routers 

[Checking the status of Ingress components](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statusingress-status)



* [Getting the status and message](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statuscheck_status)
* [Ingress statuses](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statusingress_status)
* [Ingress messages](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-statusingress_message)



[Debugging Ingress](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4ingress-debug-roks4)
If you are still experiencing problems after the node is up, [check your node logs](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-manage-console-node-logs) for errors.





 Why does my peer or ordering node fail to start? 

It is possible to experience this error under a variety of conditions.

 What’s happening 

The peer log includes:

[main] InitCmd -> ERRO 001 Cannot run peer because cannot init crypto, folder “/certs/msp” does not exist

or the ordering node log contains:

Failed to initialize local MSP: admin 0 is invalid [The identity does not contain OU CLIENT], MSP: orderermsp],The identity does not contain OU ADMIN], MSP: orderermsp]]

 How to fix it 



* This error can occur under the following conditions:



* When you created the peer or ordering service organization MSP definition, you specified an enroll ID and secret that corresponds to an identity of type peer and not client or admin. It must be of type client or admin.
* When you created the peer or ordering service organization MSP definition, you specified an enroll ID and secret that does not match the enroll ID or secret of the corresponding organization admin identity.
* When you created the peer or ordering service, you specified the enroll ID and secret of an identity that is not type 'peer' or 'orderer'.
* When you created the peer or ordering service, you associated an identity that does not have the admin role.



* Open your peer or ordering service CA node and view the registered identities listed in the Registered Users table.
* Delete the peer or ordering service and recreate it, being careful to specify the correct enroll ID and secret of a user that has the peer or orderer role and associate an identity that has a role of admin with the node.
* Note that before you create the peer or ordering service, you need to register an organization admin user, with a type admin. Be sure to specify that same id as the enroll ID when you create the organization MSP definition.
When you spread your workload across multiple machines, consider using a load balancer. A load balancer provides a well-known destination to your application. It also provides redundancy and scaling.

For more information about the different types of LBaaS and capabilities, see [Load balancers for VPC overview](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb). To increase resiliency across regions, you can use the global load-balancing functions of [Cloud Internet Services (CIS)](https://cloud.ibm.com/docs/cis?topic=cis-configure-glb).





 Using snapshot for backups 

Some occurrences or events can put your business continuity at risk such as ransomware, data loss or corruption, accidental deletion, or catastrophic events. Make backup a part of your data resiliency plan to recover from these types of events. Backup is a point-in-time copy of your data from either your boot or data volumes. For more information about using IBM Cloud snapshot backup capabilities, see [Creating Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-createsnapshots-vpc-create).





 High Availability components and tutorials 

For more information about High Availability solutions, see:



 Topic Links 

 High Availability Reference Architecture solutions <br><br> * [High Availability infrastructure on IBM Classic](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-introduction)<br> * [Building a highly available 3-tier web application in VPC](https://test.cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-components-three-tier-architecture)<br> * [Building a highly available 3-tier infrastructure in VPC](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-3-tier)<br><br><br>
Initiating the conversion 

Existing IBM Cloud customers can [open an IBM Support case](https://cloud.ibm.com/unifiedsupport/cases/add) through the IBM Cloud console, requesting to be migrated to a VRF. The IBM Support case should state: “Private Network Question” and include the following text:

"We are requesting that account your account number is moved to its own VRF. We understand the risks and approve the change. Reply with the scheduled window(s) of time where this change will be made so we can prepare for the migration."

Migration is completed by the IBM Cloud Network Engineering team. No other information is required from you, except an agreed-to schedule. Typically, packet loss might last 15 - 30 minutes, depending on the complexity of your account. It might be longer if your account has legacy Direct Link connections. The process is highly automated, requiring minimal interaction by the IBM team, and it should be transparent.

When you're opening the case, it's recommended to select the "Technical" support type option, with category Networking > Direct Link.
If you want to send multiple devices, you must create a request for each device.
* If the device is to be returned, provide a pre-paid shipping label, and export documents as needed in the package so that the device can be returned after the transfer period.
* If you're shipping the device internationally, you're responsible to obtain all licensing, shipping, and customs clearance for the Device. Your responsibilities include paying any duties, taxes, and shipping costs to and from (if applicable) the IBM Cloud data center.
* You need to provide the name of the carrier and the tracking number for the shipment to the data center when you complete the request. Create the shipping label with the appropriate data center address before you submit the data transfer request.



Follow these steps to submit a data transfer request.



1. Access the Data Transfer Service screen in the [IBM Cloud console](https://cloud.ibm.com/login).
2. Click Order Data Transfer Request.
3. Complete each field in the Device Information section according to the following table.



Table 1 describes the fields that are required for creating a data transfer request.

 Field Device Type 

 Device Type The type of device that is sent to the destination. If the device type is not listed, select Other. 
 Serial Number The serial number for the device. 
 Description A brief description of the device, such as color, labels, stickers, or other characteristics that identify the device. 
 Note Any additional notes about the device or the transfer. 
 Destination The data center that is to receive the device. 
 Carrier The post or express carrier that is used to ship the device to its destination. 
 Tracking Number The full tracking number for the shipment. 



4. Complete each field in the Return Address section or select the Company Address checkbox to automatically populate the fields with the company address on file.

Remember to include the prepaid return label and any needed export documents in the package.
5. Review your order, and click the link to read the terms and conditions.
6. Click the checkbox if you agree with the terms.
7. Click Submit Service Request.



After you submit the request, the status for the request ticket appears as Sent to SoftLayer.
Open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) for the following situations:



* You do not see a build update that you are expecting
* You have problems with HCX
* You want to have the most recent HCX build pushed to your system immediately







 Related links 



* [HCX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerationshcx_considerations)
* [Glossary of HCX terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_glossary)
* [VMware Hybrid Cloud Extension overview](https://cloud.vmware.com/vmware-hcx)
* [VMware Hybrid Cloud Extension documentation](https://cloud.vmware.com/vmware-hcx/resources)
The host experienced a precheck setup failure and cannot SSH to the private IP for the other node's host. Refer to [Correcting connectivity errors](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errors) for information on how to resolve SSH connectivity check errors.





 Error 1107 

The host experienced a precheck setup failure due to an invalid password. Correct the password and try again. Refer to [Correcting connectivity errors](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errors) for information on how to resolve SSH connectivity check errors.





 Error 1108 

The gateway experienced a precheck setup failure due to an invalid password. Correct the password and try again. Refer to [Correcting connectivity errors](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errors) for information on how to resolve SSH connectivity check errors.





 Error 1109 

The gateway experienced a precheck setup failure, and is unable to check the vSRX disk capacity. Remove any unnecessary files from /var and try again.





 Error 1110 

The gateway experienced a precheck setup failure because the vSRX file system reached capacity. Remove any unneecessary files from /var and try again.





 Error 1111 

The gateway experienced a precheck setup failure due to a general failure in the JunOS RPC call. Try again or contact [IBM Support](https://cloud.ibm.com/docs/vsrx?topic=gateway-appliance-getting-help).





 Error 1112 

The gateway experienced a precheck setup failure due to a cluster error. Ensure redundancy group 0 is online and has no monitor-failures.





 Error 1113 

The host experienced a precheck setup failure and is unable to determine the status of the host VM using virsh.
Step 3: Do not rate-limit or throttle requests from IBM CIS, we need the bandwidth to assist you with your situation.

Step 4: Block specific countries and visitors, if necessary.
* I got a 522 error, what do I do now?

A 522 error indicates we weren't able to establish a connection with your origin server (that is, your host). After about 15 seconds of connection failure, we close the connection and display a 522 error page.

This issue usually is caused by firewall or security software that accidentally blocks our IP addresses. Because CIS acts as a reverse proxy, connections to your site appear to come from a range of CIS IPs. This behavior can cause certain firewalls to block these connections, which prevents us from serving content to your site visitors properly.

To fix this issue, ask your host to allowlist all of the CIS IP ranges, listed [here](https://cloud.ibm.com/docs/cis?topic=cis-cis-allowlisted-ip-addresses).

All of these IPs must be allowlisted to avoid 522 errors. It's also worth checking to see if any IPs in these ranges are blocked.

522 errors can also be caused by network connectivity issues, so confirm that your server and network is generally healthy and not overloaded.

If after taking the above steps you still receive errors, contact IBM CIS support and confirm the following:



* You've allowlisted our IP ranges
* Your server/network is online and generally healthy



If you contact our support team, please provide a Ray ID from a recent 522 error. We can use this to determine which CIS data center you were hitting and run further tests.
* What is a proxied record and why do I need them?

Proxied records are records that proxy their traffic through IBM CIS. Only proxied records receive CIS benefits, such as IP masking, where a CIS IP is substituted for your origin IP to protect it:

$ whois 104.28.22.57 | grep OrgName
OrgName: IBM

If you would rather bypass CIS on a domain (we still resolve DNS), then non-proxying the record is a possible solution.
When a user attempts to sign in, your customized screen is called and the authorization and authentication process starts.

app.post("/form/submit", bodyParser.urlencoded({extended: false}), passport.authenticate(WebAppStrategy.STRATEGY_NAME, {
successRedirect: LANDING_PAGE_URL,
failureRedirect: ROP_LOGIN_PAGE_URL,
failureFlash : true // allow flash messages
}));



Table 1. Sign-in parameters

 Parameter Description 

 successRedirect The URL that you want to redirect the user after a successful authentication. 
 failureRedirect The URL that you want to redirect the user to if authentication fails. Users are redirected to the specified URL when the following authentication failures occur:<br><br><br><br> * The user inputs an incorrect username or password.<br> * The plan limit for the App ID instance was reached.<br><br><br> 
 failureFlash When set to true an error message is returned from the Cloud Directory service. By default, the value is set to false. 



If you submit the request in HTML, you can use [body parser](https://www.npmjs.com/package/body-parser) middleware. To see the returned error message, you can use [connect-flash](https://www.npmjs.com/package/connect-flash). To see it in action, check out the [web app sample](https://github.com/ibm-cloud-security/appid-serversdk-nodejs/blob/master/samples/web-app-sample.js).









 Branding your app with the API 

You can display your own customized screens and take advantage of the authentication and authorization capabilities of App ID. With Cloud Directory as your identity provider, your users are able to interact with your app with less help from you. They're able to sign in, sign up, reset their password, and more without asking for help.

To make this experience possible, App ID exposes REST APIs.
(https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-cleanup)
* [How can I view my smart contract container logs?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-smart-contracts-troubleshoot-entry2)
* [Why is my CA, peer, or ordering node that is configured to use HSM not working?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-hsm-proxy)
* [Why are my transactions returning an endorsement policy error: signature set did not satisfy policy?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-endorsement-sig-failure)
* [Why are the transactions I submit from VS Code failing with a No endorsement plan available error?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-anchor-peer)
* [Why are the transactions I submit from VS Code failing with an endorsement failure?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-endorsement)
* [Why is my peer unable to communicate with my ordering node?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-peer-bad-connection)
* [When I hover over my node, the status is red, what does this mean?]
To inquire about the status of your ticket, follow the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).







 What to do next 

Manage your instances from the VMware Solutions console or the VMware vSphere Web Client.

You must log in to the VPN portal of the IBM Cloud data center before you click vCenter console on the instance summary page to start managing your VMware ESXi™ servers from the vSphere Web Client. Hover over vCenter console and follow the instructions to ensure that you meet all requirements and you completed the necessary steps before you access the vSphere Web Client.

Review the following topics for information to help you complete the login instructions:



* For the requirements and necessary steps before you access the vSphere Web Client, see [Timeout reached while connecting to the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_timeout_vc_console).
* For a list of access points to log in to the IBM Cloud infrastructure Private Network by using VPN, see [VPN access](https://www.ibm.com/cloud/vpn-access).
* If you have problems when you deploy an OVF (Open Virtualization Format) file by using the vSphere Web Client, see [Deploying an OVF file using the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_deploy_ovf).







 Related links 



* [Procedure to order Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure)
* [Adding clusters to Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingclusters)
* The Python client [Redis.py](https://github.com/andymccurdy/redis-pyconnections) produces a ConnectionError when a connection fails and another command is run. The client can also issue health checks periodically or before commands.
* The Java client [Jedis](https://github.com/xetorthio/jedis/wiki) produces a JedisConnectionException when it can't reach the database, and it tries to reconnect. However, it doesn't automatically retry a command, as not every command is safe to retry or run multiple times.
* The C# driver [StackExchange.Redis](https://stackexchange.github.io/StackExchange.Redis/Configurationconfiguration-options) has adjustable parameters for client-side timeout, reconnect, and retry logic. You can tune these parameters to suit your application requirements.



A good example of cloud-ready application development that uses the Node.js client ioredis is in the IBM Developer article [Error detection and handling with Redis](https://developer.ibm.com/articles/error-detection-and-handling-with-redis/).

For more information on connecting your applications to Databases for Redis, see the "Connecting to Databases for Redis" documentation relating to



* [Connecting to an IBM Cloud application](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-ibmcloud-app),
* [Connecting an external application](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-external-app) (including [TLS and self-signed certificate support](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-external-apptls-and-self-signed-certificate-support)), and
Figure 5. Cross-Connect Router (XCR)

Use cases:



* Additional cross connects are requested to the MMR to service ISP/Telco links, connect to other CSPs, or colocation tenants.
* DLDH customer procures services and LOA/CFA from third party.
* DLDH customer supplies third party LOA/CFA to colocation provider for cross-connect order.







 The Direct Link Exchange on Classic solution 

The Direct Link Exchange on Classic solution enables customers to use a Cloud Exchange provider to deliver connectivity to IBM Cloud locations. This offering typically provides connectivity at a reduced cost because the physical connectivity from IBM Cloud to the Cloud Exchange Provider is already in place, which is shared among other customers.

Common use cases: Best for hybrid workloads, cross-provider workloads, large or frequent data transfers with high-egress bandwidth, private workloads, and environment administration. This option is usually selected when the wanted PoP location already has the wanted Direct Link Exchange provider.

Zoom

![Direct Link Exchange on Classic](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Exchange.png)

Figure 6. Direct Link Exchange on Classic

Termination location: IBM Cloud point of presence (PoP).

Typical deployment time: For Equinix providers, typical deployment time is in hours. For other providers, 5 - 10 days after circuit reaches the exchange. Deployment time can possibly be 30 - 60 days overall, depending on your location and requirements when you order a circuit from a network service provider (NSP) or carrier.

Cross-connect details: Physical cross-connects for the secure Cloud Exchange Interconnect are maintained between IBM Cloud and the Cloud Exchange provider. Customers request a "Virtual Circuit" from the Cloud Exchange Provider, which establishes logical connectivity to IBM Cloud, after the customer is interconnected to the Cloud Exchange Provider.

Port speed options: Select 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps.