Webhooks have been running successfully for over a year with only a few hickups. Last week we noticed failures with 502 Bad Gateway and asked the client (they manage their server) to restart the server after hours and while they were at it update OttoFMS to the latest version.
This took place over the weekend. This morning I restarted the business process to trigger those web hooks and 115 were received/processed successfully in 18 minutes and then we started receiving 502 Bad Gateway errors again.
What could be causing this?
Thanks!
Colleen
Do you see errors in the otto-receiver.log? If there is nothing in the otto-receiver.log then it could be an issue with OttoFMS. If you see the incoming calls in the otto-receiver.log and either no success message or an error, then it is likely a FileMaker Data API issue. What do you see in the log?
-Kyle
In the otto-receiver log file I would like to see this pattern
|2026-04-02T23:46:51.777Z|info|receiving webhook for channel: channel_outlookemail|
|2026-04-02T23:46:51.819Z|info|webhook published to channel: channel_outlookemail|
|2026-04-02T23:47:01.470Z|info|receiving webhook for channel: channel_parseemail|
|2026-04-02T23:47:01.680Z|info|webhook published to channel: channel_parseemail|
However, for more recent entries I’m seeing this:
|2026-04-06T18:26:20.295Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:26:45.461Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:27:18.842Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:27:27.532Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:27:45.749Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:28:10.737Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:28:38.009Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:28:46.922Z|info|receiving webhook for channel: channel_parseemail|
|2026-04-06T18:29:00.646Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:29:10.392Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:29:20.514Z|info|receiving webhook for channel: channel_dbemail|
|2026-04-06T18:29:47.281Z|info|receiving webhook for channel: channel_dbemail|
In the otto-info log after yesterday’s OttoFMS restart I’m seeing this:
|2026-04-06T17:58:44.448Z|info|hard restart requested|
|2026-04-06T17:58:45.449Z|info|shutting down now.|
|2026-04-06T17:58:45.783Z|info|otto internal database up to date|
|2026-04-06T17:58:45.784Z|info|Debug logging disabled|
|2026-04-06T17:58:45.797Z|info|Listening on http://localhost:3061|
|2026-04-06T17:58:45.797Z|info|environment production|
|2026-04-06T17:58:45.797Z|info|version 4.16.2|
|2026-04-06T17:58:45.797Z|info|node version v22.21.1|
|2026-04-06T17:58:45.811Z|info|started watching offsite backup|
|2026-04-06T17:58:45.812Z|info|started watching for hostname changes|
|2026-04-06T17:58:45.815Z|info|Reverse Proxy already installed|
|2026-04-06T17:58:46.905Z|info|License status: valid|
|2026-04-06T17:59:34.981Z|info|web app login successful|
|2026-04-06T18:28:45.955Z|error|BadRequestError: AxiosError: Request failed with status code 502. code:-2 - {service:express-error-handler}|
|2026-04-06T18:28:48.442Z|error|BadRequestError: AxiosError: Request failed with status code 502. code:-2 - {service:express-error-handler}|
|2026-04-06T18:28:50.192Z|error|BadRequestError: AxiosError: Request failed with status code 502. code:-2 - {service:express-error-handler}|
|2026-04-06T18:28:54.993Z|error|BadRequestError: AxiosError: Request failed with status code 502. code:-2 - {service:express-error-handler}|
Thanks Kyle!
Hey @chammersely ,
That Axios error you’re seeing means that the calls are getting to the OttoFMS server and then when they call to the Data API they’re getting a 502. It could mean the Data API is hung or the FileMaker Server process is broken somehow. IF you make a call directly to the Data API when it is failing like this does it fail? You can also check some of the FileMaker log files to see what might be happening to the FileMaker processes at the time this starts failing.
-Kyle
Thanks Kyle!
Will followup with the client and review the FileMaker log files to see what that might reveal.
-Colleen