Skip to main content
Question

HTTP 503 Service Unavailable scheduled backupConfiguration.fmw

  • May 31, 2017
  • 1 reply
  • 151 views

Forum|alt.badge.img

We run SSL and use a CNAME of gisdata.launceston.tas.gov.au

FME Server 2017.0 is throwing:

HTTPCaller(HTTPFactory): Received HTTP response header: 'HTTP/1.1 503 Service Unavailable' from 'http://papfme1.launceston.tas.gov.au:80/fmerest/configuration/migration/export'

Terminator(TestFactory): Terminator: Termination Message: 'Unable to retrieve backup from FME Server `http://papfme1.launceston.tas.gov.au:80'. Please ensure that the credential are correct and that user `fmeadmin' has fmesuperuser role. The error was: HTTP/1.1 503 Service Unavailable - http://papfme1.launceston.tas.gov.au:80/fmerest/configuration/migration/export.'

fmeadmin is in the fmesuperuser role and I have changed all hosts to use https and the CNAME above.

The schedules>Backup Configuration form does keep reverting the password to 3 characters (which it isn't). If I paste

http://papfme1.launceston.tas.gov.au:80/fmerest/configuration/migration/export into a browser it takes me to the FME Rest Service web UI and if I enter the fmeadmin token I do get a ServerConfigPackage.fsconfig download.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

Forum|alt.badge.img+2

Hi @richardtriesfme

 

Did you have any luck with this?

 

 

The 3 characters with the password is OK, I believe it does this in multiple places throughout the web ui, to hide how many characters are in the password.

 

 

I did test the backup configuration on one of our servers that does have SSL enabled, and it calls the configuration/migration/export service with a url with HTTPS, not HTTP. In the log you've copied above, it looks like the service is trying to call the url with HTTP, whereas if you've configured your FME Server for SSL I would have expected it to have HTTPS.

 

Do you know whether SSL has been correctly configured on your machine?