Skip to main content
Solved

Streaming Service Base URL Wrong in 2019.1

mmccart
Contributor
Forum|alt.badge.img+16

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

Best answer by david_r

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

 

View original
    Did this help you find an answer to your question?

    4 replies

    david_r
    Evangelist
    • david_rEvangelist
    • July 18, 2019

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

     

    mmccart
    Contributor
    Forum|alt.badge.img+16
    • mmccartContributor
    • Author
    • Contributor
    • July 18, 2019
    david_r wrote:

    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
    Evangelist
    • david_rEvangelist
    • Best Answer
    • July 18, 2019

    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
    Contributor
    Forum|alt.badge.img+16
    • mmccartContributor
    • Author
    • Contributor
    • July 18, 2019
    david_r wrote:

    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


    Helpful Members This Week

    Community Stats

    30,928
    Posts
    117,220
    Replies
    38,733
    Members

    Latest FME

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie 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.