Setting up Reverse Proxy Server - not seeing errors, but unable to connect to application servers
![](http://jazz.net/_images/myphoto/6be9c2002cd73f62b822399f2d0e2953.jpg)
Have been using a combination of these document to setup / create IHS plugins for Liberty on a distributed environment
Both documents do basically the same but one has more details than the other.
I have done this on another installation and its working just fine, but we did use the self extracting "trial" ihs serve version
In the install I have right now I've installed IBM HTTP server from IM
The installation is configured and HTTPServer is running and I can from the proxy server get the http logo using http and https with the port address, servername and its fqdn. However, when I attempt to get to an applicaiton server I first get a browser certificate error (from firefox) which I accept the risk - then it returns the URL cannot be found on this server.
From a regular browser login, I can also get to the proxy without issues - but again when I expand the proxy server parametet to include an applicaiton server it again fails as above.
I've compared to the other install and everything is pretty much identical the exception being one was trial IHS the other is IM installed.
Any ideas ? I raised a PMR but they only provide support for full blow WAS install with IHS - where we don't have full blow WAS
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 18 '22, 7:53 a.m.WAS Liberty is a supported application server. It is even the default.
1. Ask why your configuration would not be supported.
2. Ask for what is supported with WAS Liberty.
Karen Steele
Jan 18 '22, 8:57 a.m.Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 18 '22, 9:09 a.m.For me not having deployed RELM still makes it an enterprise topology.
How can you reach the applications, if the URI root is hosted on the proxy? Without proxy the host they are on would not be in the URI, right? The Hostname would not he the FQN used in the public URI, the IHS would run in the host with that FQN.