Skip to main content

FME Server 2017.0.1 - Build 17288 - win64

Setup with https

When using any workspace - and RUN button - it seems to fail.

However if I copy the Direct URL directly - it seems to work fine.

Using Chrome and debuggingtools and log of the post and response below

Response:

HTTP Status 500 - Connection refused: connect

type Exception report

message Connection refused: connect

description The server encountered an internal error that prevented it from fulfilling this request.

exception

<!DOCTYPE html><html><head><title>Apache Tomcat/8.5.5 - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 500 - Connection refused: connect</h1><div></div><p><b>type</b> Exception report</p><p><b>message</b> <u>Connection refused: connect</u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>exception</b></p><pre>java.net.ConnectException: Connection refused: connect
java.net.DualStackPlainSocketImpl.connect0(Native Method)
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
java.net.Socket.connect(Socket.java:589)
sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
COM.safe.web.client.SelfSignedSSLSocketFactory.connectSocket(SelfSignedSSLSocketFactory.java:52)
org.apache.http.conn.scheme.SchemeSocketFactoryAdaptor.connectSocket(SchemeSocketFactoryAdaptor.java:66)
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:117)
COM.safe.web.client.HTTPClientFacade.execute(HTTPClientFacade.java:254)
COM.safe.fmeserver.webui.jobrun.JobRunnerHelper.runJob(JobRunnerHelper.java:256)
COM.safe.fmeserver.webui.servlet.rest.JobRunnerFormREST.handleRequest(JobRunnerFormREST.java:181)
COM.safe.fmeserver.webui.servlet.rest.JobRunnerFormREST.doPost(JobRunnerFormREST.java:67)
javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
COM.safe.fmeserver.webui.sitemap.SiteMapFilter.doFilter(SiteMapFilter.java:40)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:120)
COM.safe.web.servlet.CharsetEncodingFilter.doFilter(CharsetEncodingFilter.java:538)
COM.safe.webservices.security.FMEServerAuthFilter.doFilter(FMEServerAuthFilter.java:234)
org.ebaysf.web.cors.CORSFilter.handleNonCORS(CORSFilter.java:640)
org.ebaysf.web.cors.CORSFilter.doFilter(CORSFilter.java:173)
</pre><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/8.5.5 logs.</u></p><hr><h3>Apache Tomcat/8.5.5</h3></body></html>

Hi @sigtill

 

 

What do you see in the web UI after you press run?

 

If you copy and paste the direct URL into a new tab without the ? or parameters after it does that work?

 

Have you been able to look at the tomcat logs or FME Server logs to see if there is any more information? You could look at the fmeserver.log, fmeprocessmonitorcore.log, service logs as well as the tomcat logs.

 


Hi @sigtill,

 

try to run this command:
keytool -importkeystore -srckeystore tomcat.keystore -destkeystore <FMEServerDir>\Utilities\jre\lib\security\cacerts

(Note: run it as administrator from <FMEServerDir>\Utitilies\jre\bin\)

This is part of our SSL documentation for self-signed certificates to make sure FME Server trusts the certificate, but it might also help with a CA issued certificate.


The certificate in question is a GoDaddy certificate, and that root CA seems to be present in cacerts already.


Reply