45
Views
6
Comments
Communication Error
Application Type
Reactive
Platform Version
11.18.1 (Build 37828)

Hi Everyone,

When i try to publish on on premise environment, i'm getting the "Communication Error" as below

There was an error connecting to "our domain name"

The HTTP request was forbidden with client authentication scheme 'Anonymous'.

I attached the screenshot of the error. Please anyone can help to resolve  this error ?

Thanks,

Suriyakala



2025-04-08 13-09-23
Shubham Shrivastava

Hi Suriyakala,

Can you please share the error screenshot and include the OML file? 

2019-01-07 16-04-16
Siya
 
MVP

Please logon to Service Center and see if any detailed log available about the error reported. This information might help community to provide some answers. Besides you can raise a ticket with OutSystems.

UserImage.jpg
Md Mansur

Hi @Suriyakala - EONE

Can you Please share error log or Screenshot so we will Indentifify your problme and Provide any working solution 

Thanks

Md Mansur

2025-03-05 10-16-14
Suriyakala S

Hi masur,

I attached the screenshot of the error in service center. Can you check it. It is a communication error. My network is good. In which other cases we will get the this communication error?

Thanks,

Suriyakala





serror.jpg
2023-10-31 07-36-11
Marlies Quaadgras
Champion

Hi @Suriyakala - EONE 


It looks like you are not logged in into any environment.  That situation gives this error.


Best regards, Marlies

2024-03-23 18-16-49
Bryan Villalobos

Hi @Suriyakala - EONE ,


The screenshot you attached is not an error in Service Center but in Service Studio.

Are you able to access service center? https://YOUR_DOMAIN_NAME/servicecenter

Is your OutSystems environment in CLOUD or ON PREMISE? It does seem to be on-premise. It is possible that the network you are in when you encounter this issue cannot reach your domain. 

e.g. You are at home connected to your wifi, but your domain in your OS environment server is not accessible publicly or restricts access to external connections. 

Try to access service center or ping/telnet to your server network and see if you are allowed to access where you are connected.

Regards,

Bryan

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.