Are you encountering issues accessing the FME Server web interface – specifically, logging in? Please read below for some common troubleshooting tips, questions and resources.
Troubleshooting Tips
- Can you login using a different web browser? You may also consider testing in a private window or emptying the cache or deleting cookies.
- Can you login on the machine hosting FME Server? Try both http(s)://<hostname>:<port>/fmeserver and http(s)://localhost:<port>/fmeserver – is there any difference in behaviour?
- Try temporarily disabling any firewalls and observe if you can login afterwards.
- Log Files that may help identify errors include both FME Server and Tomcat – these can be accessed via file system.
<FMEServerSystemShare>\resources\logs\core\current\fmeserver.log
<FMEServerSystemShare>\resources\logs\tomcat\catalina.log - Try enabling the web developer tools for your browser. Monitor the network status and identify if there is anything failing or hanging / timing out.
Common Issues
“The web interface (login page) is not accessible.”
First verify that there are no firewall rules preventing you from accessing FME Server – see this article for suggestions. This issue may also be related to the FME Server Application Server – if you are serving the web interface from Apache Tomcat (the default in an Express installation). Verify that the FME Server Application Server (Windows Service) is running. Please take a moment to review this article and determine if it is applicable to your scenario.
If the web interface is visible, but the login button is missing or appears as a green bar without text when you access it using Internet Explorer - see this article for troubleshooting options.
“The web interface page hangs after trying to log in.”
This issue is commonly experienced when there are orphaned processes running. Orphaned – or “rogue” – processes can occur if there are any errors shutting down or restarting FME Server, or if one of the supporting applications for FME Server crashes and the FME Process Monitor starts another without gracefully removing the one at fault.
To resolve this issue, see the resolution from this article – the exact symptom may be different, but this general resolution can fix most scenarios.
“I cannot remember my password.”
If you cannot remember your password, you must have an admin user login to FME Server and manually change it for you – this is applicable to FME Server 2016.0+.
For FME Server 2018.0+, you can reset your own password if the Reset Password feature has been enabled in System Configuration.
For FME Server 2015.x and older, please see this article.
“I have entered the correct password but the response is ‘Login failed, please try again’.”
FME Server usernames are case-sensitive – please make sure that the correct combination of lowercase and uppercase characters are used. Other applications may be case-insensitive.
This error might be experienced when FME Server is connected to an Active Directory listing – please check with your IT/Security Department if uncertain that you have the correct case.
If Active Directory is enabled, please see this article for more troubleshooting information.
“After logging in, I cannot see many options in the web interface. Only Manage > Jobs is accessible.”
Has the installation of FME Server been configured to point to an existing PostgreSQL, Microsoft SQL, or Oracle Database? The post-installation configuration scripts may not have been run. Please try invoking these as an Administrator while FME Server Core is running, then restart FME Server and try logging in again.
“After logging in, the message ‘Could not connect to FME Core. Please ensure that it is running.’ is displayed.”
Has the installation of FME Server been configured to point to an existing PostgreSQL, Microsoft SQL, or Oracle Database? It is possible that the user or service account running the FME Server Windows Services does not have proper network privileges. Please see this article for more troubleshooting information.
“After logging in, some pages work, but others show a message like 'Error communicating with FME Server host... Contact your FME Server administrator...'.”
You might see this problem after setting up a distributed installation of FME Server. Some pages in the web interface use different ports to communicate with the FME Server core. For example, the jobs, projects, and repositories pages use port 7071, but the schedules page uses port 7073. So, if port 7071 was open between the web application server host and the core host, but 7073 was closed, you would see the Jobs page working properly, but the Schedules page would show an error. Please see this FME Server documentation page for a full list of the required ports.
Common Questions from FME Community Q&A
- Can you bypass or skip the login screen of the FME Server web interface?
- Why does my FME Server Web Interface not show a login button?
- Can you restrict access to the FME Server web interface to local traffic only?
Popular Ideas by the FME Community
- Enforce Password Complexity for FME Server Users
- Allow the FME Server Username to be "Case-Insensitive"
Other Resources
FME Server Database Service Does Not Start After Reboot
FME Server 'Notifier' Fails to Start
Enabling AES256 in the Java Runtime Environment for Single Sign-On
FME Server Won't Start - When using a Production Database
Are you still experiencing issues?
Please consider posting to the FME Community Q&A if you are still experiencing issues that are not addressed in this article. There are also different support channels available.
Have ideas on how to improve this?
You can add ideas or product suggestions to our Ideas Exchange.
