Solved

Streaming Service Base URL Wrong in 2019.1

mmccart
Rank
Badge +13

I upgraded FME Server to 2019.1 and my streaming services are failing. It appears that 'FME_SERVER_WEB_URL' in the request did not pick up the change when I enabled HTTPS during the install. It is still showing the original HTTP url with Port 8080 (http://SERVERNAME:8080). Is there another file besides fmeServerConfig.txt that needs to be modified?

I have a distributed architecture deployment: All components are on a single machine except the Web Services component, that is on a separate machine. I upgraded from 2019.0.1 to 2019.1 and now my streaming services are not providing an output.

Thanks in advance.

-Mark

icon

Best answer by david_r 18 July 2019, 17:25

View original

4 replies

david_r
Rank
Userlevel 4

You probably need to update the service URLs in the FME Server GUI, under the Services section.

 

mmccart
Rank
Badge +13

You probably need to update the service URLs in the FME Server GUI, under the Services section.

 

Sorry @david_r, I should have included that in my post. That piece is done. All of the match the correct base URL.

david_r
Rank
Userlevel 4

I can only recommend that you read through all the steps here and check that you didn't miss anything:

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

 

mmccart
Rank
Badge +13

I can only recommend that you read through all the steps here and check that you didn't miss anything:

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

 

Thanks. I missed one step.

Reply


Community Stats

28,724
Posts
109,518
Replies
36,564
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.