[closed] ERR_CONNECTION_REFUSED after server rename
The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Jul 21 '21, 6:58 a.m.
3 answers
I would start with the JTS log.
Comments
JTS log and WAS logs show connection errors for local host (jts-dsv) I've connection refused from the server jts-dsv which my local server.
This is the error from SystemOut.log:
[2/27/18 18:24:35:282 WET] 000000a8 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[equinoxbridgeservlet]: c om.ibm.team.jfs.app.util.urlmapping.URLMappingException: org.apache.http.conn.HttpHostConnectException: Connection to https://jts-dsv refused at com.ibm.team.jfs.app.util.urlmapping.internal.URLMappingService.getUrlMappingEventFeedStatus(URLMappingService.java:447) at com.ibm.team.jfs.app.util.urlmapping.URLMappingServiceFactory.getMappingEventFeedStatus(URLMappingServiceFactory.java:80)
You should just treat it as a new server and check connectivity to IP address and port. I suspect your application server may not even start up properly.
Comments
the App Server (WebSphere) starts ok , I've ccm and jts running in "green status" I can ping the server and I have port 9443 listenning . Is there a way to disable SSL ?
Disabling SSL is not the right way to resolved the issue. If the WAS profile is listening at port 9443 and the public URI uses 443 (default SSL port), it means that there is a reverse proxy in your environment. Have you verified that the reverse proxy is up and running? Can you connect to jts-dsv:443 using telnet or openssl?
hmm my network skills don't permit me to check if reverse proxy is up and running... I need to talk with AIX admin guy. Meanwhile can I do anything else?
Your test result proves that port 443 is not open, and that is exactly why you got the ERR_CONNECTION_REFUSED message in the first place. You should check how the production is configured. There should be a reverse proxy, or the application server (Tomcat?) is listening at port 443 instead of 9443. In either case, you need to make necessary changes to allow the applications to be accessed via port 443.
1 vote
