span8
span4
span8
span4
The configuration for HTTPS is done on the underlying web server for FME Server.By default Tomcat is shipped with FME Server,and our configurationdocumentationis based on the documentation provided by Tomcat.
To find the version of Tomcat that's installed,you can check in the RELEASE-NOTES file at
You can check the documentation for your version of Tomcat here:
http://tomcat.apache.org/
Current FME Server Release Documentation Link
If you're using a pfx certificate,pleasethis article.
If you're in the process of configuring,or have configured FME Server for HTTPS and you encounter errors here are some troubleshooting tips:
1.Check the tomcat logs for errors.
These can be found at
The first log to check should be the catalina log,then the localhost log.If you open the log file in a text editor (rather than the FME Server web interface),you can search for any WARN or ERROR.
2.Have you used the correct password?
The correct password needs to be used for the keystore file and the server.xml file.It's easy to add in a typo here.
3.When generating the keystore,have you used the correct domain name?
When you generate the certificate signing request it will ask for your first and last name.Here you need to specify the fully qualified domain name.
4.Have the certificates been installed correctly?
You will need to make sure the certificates are installed correctly (and in the right order): Root,Issuing,Host/Full Name.This may depend on what certificates you have been issued to the number and type of certificates.
5.Was the same keystore in tomcat used to generate the certificate signing request?
Make sure when you're requesting the certificate it's using the same keystore that you generated for the correct domain name of your FME Server.
6.Are the correct ports open?
Depending on what ports were specified in the server.xml file for tomcat configuration,you will need to ensure these are configured in your firewall settings.By default these are 8443/443.If you are getting tomcat errors relating to ports,you can check the reported Process ID (PID) and cross reference this against the process in Task Manager.This should tell you what application/process it is conflicting with.You will need to find a port that is not in use and update the server.xml tomcat configuration file.
7.Have you checked the certificate?
You can use the developer tools to look at the installed certificate.In Google Chrome this is under the security option when looking at the developer tools.Ensure the certificate has been generated or provided for the correct address.
8.Ciphers and Protocol versions:
You can usehttps://www.ssllabs.com/ to see what protocols and ciphers your browser supports and compare against the server.xml configuration.
9.Where are you storing the keystore file?
Ensure the FME Server Application and Core servicesLog on Asuser has access to the keystore file location.
You may also want to store the keystore in a location that does not have spaces in the filepath.
10.What type of keystore and implementation are you using?
The FME Server HTTPS configuration documentation refers to JKS keystore format and the JSSE implementation.For PKCS12 or APR implementation please refer to thetomcat documentationfor your version.
11.Are you using anti-virus software?
If so,check your anti-virus configuration to see if it is scanning SSL connections.If it is,try disabling SSL scanning and try connecting to FME Server again.
FME Server Administration Guide - HTTPS/SSL
Are you still experiencing issues?
Please consider posting to theFME 亚搏国际在线官网Community Q&Aif you are still experiencing issues that are not addressed in this article.There are alsodifferent support channelsavailable.
If you are still experiencing issues,including as much detail about the issue will help you get an answer sooner.Things to include:
What version of FME Server you're using.
What type of certificate you're working with: Self-Signed,CA-issued (public/private).
Any errors you're seeing,in the tomcat logs,FME Server logs or in the developer information tools window.
Any more information that you can share that might help someone troubleshoot the issue.
Have ideas on how to improve this?
You can add ideas or product suggestions to ourIdeas Exchange.
Unable to Run Workspaces Registered to Notification Service When SSL is Configured
FME Server Troubleshooting: Email
FME Server Troubleshooting: Log Files
Part 5 - Deploy changes (delete)
FME Server Troubleshooting Guide: Additional Resources
FME Server Troubleshooting Guide
FME Server Troubleshooting: Tokens
FME Server Troubleshooting Guide: Initial Troubleshooting
© 2019 亚搏在线Safe Software Inc |Legal