KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Rebecca Jonas — Thu, 18 Jun 2020 20:03:55 GMT

Current Revision posted to Appian Knowledge Base by Rebecca Jonas on 6/18/2020 8:03:55 PM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has trusted IPs configured fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger -  class="error">[ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

The following PKIX error may also be present in the application server log:

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Cause

There are two potential causes that could result in this issue:

If the PKIX error is present, then there is an issue with the certificate for the remote environment attempting to establish a Devops: Infrastructure connection. The web server certificates on both the first site and secondary site must be valid, and must be trusted by the other site respectively.
The second cause relates to trusted IPs and will differ based on installation type:

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP allow list and connection attempts are being blocked.

Self-managed

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

To address any issues with the certificates for each site, follow the steps outlined in KB-1187 to have the web server certificates for each site added to the other site's default JDK trust store.
To address the issue with trusted IPs, follow the below steps based on installation type:

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Self-managed

Ensure that any URL starting with the following pattern is exempt from any allow list on both servers involved with the Devops: Infrastructure operation:

https://<other_site_URL>/suite/devops-infrastructure/

Affected Versions

This article applies to Appian versions 19.1 and later.

Last Reviewed: June 2020

Tags: connected environment, DevOps, integration, admin console, web services

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Rebecca Jonas — Wed, 06 Nov 2019 17:01:27 GMT

Revision 18 posted to Appian Knowledge Base by Rebecca Jonas on 11/6/2019 5:01:27 PM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger -  class="error">[ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

The following PKIX error may also be present in the application server log:

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Cause

There are two potential causes that could result in this issue:

If the PKIX error is present, then there is an issue with the certificate for the remote environment attempting to establish a Devops: Infrastructure connection. The web server certificates on both the first site and secondary site must be valid, and must be trusted by the other site respectively.
The second cause relates to IP whitelisting and will differ based on installation type:

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

On-Premise

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

To address any issues with the certificates for each site, follow the steps outlined in KB-1187 to have the web server certificates for each site added to the other site's default JDK trust store.
To address IP whitelisting, follow the below steps based on installation type:

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

On-Premise

Ensure that any URL starting with the following pattern is exempt from any whitelisting on both servers involved with the Devops: Infrastructure operation:

https://<other_site_URL>/suite/devops-infrastructure/

Affected Versions

This article applies to Appian versions 19.1 and later.

Last Reviewed: November 2019

Tags: connected environment, DevOps, integration, admin console, web services

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Mon, 19 Aug 2019 06:28:44 GMT

Revision 17 posted to Appian Knowledge Base by Parmida Borhani on 8/19/2019 6:28:44 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

On-Premise

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

On-Premise

Ensure that the following URLs are exempt from any whitelisting on both servers involved with the Devops: Infrastructure operation:

Enable Generic Devops: Infrastructure

https://<other_site_URL>/suite/devops-infrastructure/request
https://<other_site_URL>/suite/devops-infrastructure/handler
https://<other_site_URL>/suite/devops-infrastructure/public-key

Enable Compare App Functionality on 19.2

https://<other_site_URL>/suite/devops-infrastructure/com_appiancorp_designobjectdiffs_functions_application_DodConnEnvCallSystemRuleHandler

Enable Compare App Functionality on 19.3

https://<other_site_URL>/suite/devops-infrastructure/dod:callSystemRule
https://<other_site_URL>/suite/devops-infrastructure/dod:getProcessModelFromCE

Affected Versions

This article applies to Appian versions 19.1, 19.2, and 19.3.

Last Reviewed: August 2019

Tags: connected environment, DevOps, integration, admin console, web services

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Mon, 19 Aug 2019 06:27:44 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 8/19/2019 6:27:44 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

On-Premise

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

On-Premise

Ensure that the following URLs are exempt from any whitelisting on both servers involved with the Devops: Infrastructure operation:

Enable Generic Devops: Infrastructure

https://<other_site_URL>/suite/devops-infrastructure/request
https://<other_site_URL>/suite/devops-infrastructure/handler
https://<other_site_URL>/suite/devops-infrastructure/public-key

Enable Compare App Functionality on 19.2

https://<other_site_URL>/suite/devops-infrastructure/com_appiancorp_designobjectdiffs_functions_application_DodConnEnvCallSystemRuleHandler

Enable Compare App Functionality on 19.3

https://<other_site_URL>/suite/devops-infrastructure/dod:callSystemRule
https://<other_site_URL>/suite/devops-infrastructure/dod:getProcessModelFromCE

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Mon, 19 Aug 2019 06:26:08 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 8/19/2019 6:26:08 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

On-Premise

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

On-Premise

Ensure that the following URLs are exempt from any whitelisting on both servers involved with the Devops: Infrastructure operation:

Enable Generic Devops: Infrastructure

https://<other_site_URL>/suite/devops-infrastructure/request
https://<other_site_URL>/suite/devops-infrastructure/handler
https://<other_site_URL>/suite/devops-infrastructure/public-key

Enable Compare App Functionality on 19.2

https://<other_site_URL>/suite/devops-infrastructure/com_appiancorp_designobjectdiffs_functions_application_DodConnEnvCallSystemRuleHandler

Enable Compare App Functionality on 19.3

https://<other_site_URL>/suite/devops-infrastructure/dod:callSystemRule
https://<other_site_URL>/suite/devops-infrastructure/dod:getProcessModelFromCE

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Mon, 19 Aug 2019 06:25:13 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 8/19/2019 6:25:13 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

Cloud

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

On-Premise

Certain URL paths under /suite that are used by the Devops: Infrastructure connection are being blocked.

Action

Cloud

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

On-Premise

Ensure that the following URLs are exempt from any whitelisting on both servers involved with the Devops: Infrastructure operation:

Enable Generic Devops: Infrastructure

https://<other_site_URL>/suite/devops-infrastructure/request
https://<other_site_URL>/suite/devops-infrastructure/handler
https://<other_site_URL>/suite/devops-infrastructure/public-key

Enable Compare App Functionality on 19.2

https://<other_site_URL>/suite/devops-infrastructure/com_appiancorp_designobjectdiffs_functions_application_DodConnEnvCallSystemRuleHandler

Enable Compare App Functionality on 19.3

https://<other_site_URL>/suite/devops-infrastructure/dod:callSystemRule
https://<other_site_URL>/suite/devops-infrastructure/dod:getProcessModelFromCE

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Tue, 06 Aug 2019 05:16:41 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 8/6/2019 5:16:41 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian Cloud environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

KB-1973 Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Tue, 06 Aug 2019 05:16:41 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 8/6/2019 5:16:41 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian Cloud environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

DRAFT KB-XXXX Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Tue, 06 Aug 2019 03:26:25 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 8/6/2019 3:26:25 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian Cloud environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, Cloud

DRAFT KB-XXXX Adding a connected environment fails with "URL did not return valid public key" error

Parmida Borhani — Tue, 06 Aug 2019 03:26:10 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 8/6/2019 3:26:10 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian Cloud environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: integration, admin console, web services, application design, Cloud

DRAFT KB-XXXX Adding a connected environment fails with "URL did not return valid public key" error

Tom Ryan — Tue, 06 Aug 2019 03:15:32 GMT

Revision 9 posted to Appian Knowledge Base by Tom Ryan on 8/6/2019 3:15:32 AM

Symptoms

Adding a connected environment in the Admin Console for an Appian Cloud environment that has IP whitelisting enabled fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX Adding a connected environment fails with "URL did not return valid public key" error

Rebecca Jonas — Mon, 05 Aug 2019 19:24:20 GMT

Revision 8 posted to Appian Knowledge Base by Rebecca Jonas on 8/5/2019 7:24:20 PM

Symptoms

Adding a connected environment that has IP whitelisting enabled in the Admin Console fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: August 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX Adding a connected environment fails with "URL did not return valid public key" error

Zach Puderbach — Mon, 05 Aug 2019 18:13:30 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 6:13:30 PM

Symptoms

Adding a connected environment that has IP whitelisting enabled in the Admin Console fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 05 Aug 2019 18:11:48 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 6:11:48 PM

Symptoms

Adding a connected environments in the Admin Console fails with the following error:

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Additionally, IP whitelisting has been configured on the environment that is being added as a connected environment.

Cause

The Appian Cloud region IP addresses have not been added to the other environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the environment being added as a connected environment. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 05 Aug 2019 18:08:06 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 6:08:06 PM

Symptoms

Adding a connected environments in the Admin Console fails with the following error

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: https://<other_site_subdomain>.appiancloud.com/suite]

Cause

The Appian Cloud region IP addresses have not been added to the affected environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the affected environments. See KB-1582 for specific IP addresses to add based on region.

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 05 Aug 2019 18:07:08 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 6:07:08 PM

Symptoms

Adding a connected environments in the Admin Console fails with the following error

The following error is also observed in the application server log:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, https://<other_site_subdomain>.appiancloud.com/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key:

https://<other_site_subdomain>.appiancloud.com

/suite]

Cause

The Appian Cloud region IP addresses have not been added to the affected environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the affected environments. See KB-1582 for specific IP addresses to add based on region.

Workaround

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 05 Aug 2019 17:52:54 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 5:52:54 PM

Symptoms

Trying to setup connected environments in the Admin Console fails with the following error:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, <SITE_URL>/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: <SITE_URL>/suite]

Cause

The Appian Cloud region IP addresses have not been added to the affected environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the affected environments. See KB-1582 for specific IP addresses to add based on region.

Workaround

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 05 Aug 2019 17:50:35 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 8/5/2019 5:50:35 PM

Symptoms

Trying to setup connected environments in the Admin Console fails with the following error:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, <SITE_URL>/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: <SITE_URL>/suite]

Cause

The Appian Cloud region IP addresses have not been added to the affected environment's IP whitelist and connection attempts are being blocked.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the affected environments. See KB-1582 for specific IP addresses to add based on region.

Workaround

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud

DRAFT KB-XXXX URL did not return valid public key when adding a connected environment

Zach Puderbach — Mon, 08 Jul 2019 22:24:19 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 7/8/2019 10:24:19 PM

Symptoms

Environments are unable to be connected with the following error:

ERROR com.appiancorp.connectedenvironments.logging.DevOpsInfrastructureAuditLogger - [ERROR, null, null, <SITE_URL>/suite, OUTGOING, null, null, null, null, null, null, null, null, null, URL did not return a valid public key: <SITE_URL>/suite]

Cause

The Appian Cloud region IP addresses have not been added to the affected environment's whitelist.

Action

Open a case with Appian Support to add the Appian Cloud region's IP addresses to the affected environments. See KB-1582 for specific IP addresses based on region.

Workaround

Affected Versions

This article applies to Appian Cloud 19.1 and later.

Last Reviewed: July 2019

Tags: admin console, web services, Cloud