Solved

Unable to access FME Web Interface from any machine other than the server itself

  • 3 September 2021
  • 7 replies
  • 47 views
J

Hi all, we've just installed FME server, on a standalone machine. All components on one server. We are able to access the fme web interface from the server itself (it's configured for https) and all looks great. However we're unable to access the site from any workstations. Our network team says they have allowed traffic through port 443 (https) so we should be ok there. When trying to load the site on Chrome, we get the following error: The Site can't be reached.... took to long to respond....ERR_CONNECTION_TIMED_OUT. Any thoughts? Not sure what else to try at this point. Our network team is still working on this, and trying to determine where the traffic is being blocked but thought I'd see if anyone else has had this issue. Is 443 the only port needed to be open in this case? -Thanks in advance.

 

icon

Best answer by david_r 3 September 2021, 08:29

View original

7 replies

hkingsbury
Rank
Userlevel 5
Badge +29

Just checking you've worked your way through this - specifically the part about change the tomcat config files?

https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/configuring_for_https.htm

Check out the Abley FME Firesides on Youtube: https://www.youtube.com/@ableyltd
J

Just checking you've worked your way through this - specifically the part about change the tomcat config files?

https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/configuring_for_https.htm

Yes, I did make sure to update the tomcat config files and restarted the FME server as well. Get Outlook for iOS
hkingsbury
Rank
Userlevel 5
Badge +29
Yes, I did make sure to update the tomcat config files and restarted the FME server as well. Get Outlook for iOS

are you going through IIS, or connecting straight to tomcat?

Check out the Abley FME Firesides on Youtube: https://www.youtube.com/@ableyltd
J
Yes, I did make sure to update the tomcat config files and restarted the FME server as well. Get Outlook for iOS
Straight through tomcat. No IIS involved. Get Outlook for iOS
david_r
Rank
Userlevel 4

If you've properly configured FME Server with SSL, opening port 443 should suffice.

However, the error message makes me think that there's an issue with a firewall somewhere, but of course there could be a number of other issues as well. Can you ping the server? How about doing a traceroute?

 

redgeographics
Rank
Userlevel 5
Badge +25

Here's the relevant FME Server Troubleshooting guide.

J

Thank you all for the great feedback! We are up and running now. It appears that we either just needed some time for the firewall rules to propagate, or the final fme restart I did last night did the trick. Either way, we're up and running now. We only did need port 443 like was mentioned, and the configuration was ok. So I'm assuming it was just the firewall rules, or the network routing that needed to get worked out. Thanks again all, I didn't expect so many answers so fast. Great community here!

Reply


Community Stats

28,731
Posts
109,530
Replies
36,565
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.