This content has been archived.

Table of Contents

What do you do if Updater's git folder cannot connect to the proxy server?

When attempting to upgrade, if you see the following error in the OpenSpan.Updater.RuntimeLauncher logs, it typically indicates that the git folder cannot connect to the proxy server:

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at OpenSpan.UpdaterService.Remoting.UpdaterRemoting.InvokeStaticMethod(String assemblyPath, String typeName, String methodName, Type[] parameterTypes, Object[] parameters, String& domainReference)
   at OpenSpan.Updater.RuntimeLauncher.UpdateLogic.Fetch(String repo)
   at OpenSpan.Updater.RuntimeLauncher.UpdateLogic.DoUpdate()
Inner exception #1: ApplicationException: Failed to fetch
Fatal: False
DetailLog: Error:
fatal: unable to access 'https://[RegionalDeploymentPortalURL]/[tenant]/git/rt_RC_8/': Failed connect to [RegionalDeploymentPortalURL]:443; No error

To make sure that the connection to the proxy server is working, add the proxy server address to the RuntimeConfig.xml file of the user who is trying to upgrade. This setting is best updated in the Pega Robotic Automation Deployment Portal Runtime settings configuration of the user.

The following is an example of the setting that is found in the RuntimeConfig.xml file:

<Proxy url="PROXYADDRESS"/>

For more information, see Runtime Configuration Settings.

Suggest Edit

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.