Another member posted the same content before, but I didn’t get a reply, so I’m going to repost it.
Previously, we were able to access our Pega application by connecting directly to the server without going through the load balancer (ex. http://nn.nn.nn.nn/prweb/), but we got a timeout error when trying to access it through the load balancer (ex. https://xxxxx.com/prweb/).
As a countermeasure, we set up DSS referring to the following page and enabled the reverse proxy. https://docs-previous.pega.com/sites/default/files/help_v62/definitions/l/loadbalancing.htm
However, as a result, even if we connect directly to the server and access the Pega application without going through the load balancer, it will automatically communicate over https.
In this case, for example, when using multiple servers via a load balancer, after restarting a specific server, if we want to directly connect to that server over http and check the operation, we will not be able to check correctly.
Is there a workaround other than enabling reverse proxy?
Edited by Moderator Marissa to add Capability tags
@ShunsukeM6155
Does the server.xml file for the server have configured connectors for both http and https?
Can you confirm that the app server is listening on port 80 and 443 (or whichever ports the http and https connectors are configured to use in server.xml)?
@shanp
Thanks for the reply. I’ll try to find out.
@shanp
Thank you for your reply. Respond to the results you have confirmed.
＞Does the server.xml file for the server have configured connectors for both http and https?
Yes, exactly.
＞Can you confirm that the app server is listening on port 80 and 443 (or whichever ports the http and https connectors are configured to use in server.xml)?
Yes, exactly.
@shanp
Do you have both http and https connectors configured in your server.xml file?
Excuse me. When I checked again, there was an http setting. There was no https setting.
@ShunsukeM6155
Thanks for getting back to me. We have similar situations, and we always have http and https connections configured and we are able to connect directly to the server outside of load balancer on 80 and 443 so you might be using a different load balancer. Sorry that I couldn’t help with your exact situation.
