Forminator webhook - failed to process request

Sam_Mubie · January 1, 2025, 1:59pm

Finally I got the workflow running successfully after modifying the workflow as following…

But when activating the workflow, trying to save the Webhook URL as https://lizenfdt.app.n8n.cloud/webhook/xxxx; in stead of https://lizenfdt.app.n8n.cloud/webhook-test/xxxx; , got error…Failed to process request : Internal Server Error.

Had consulted the plugin Forminator provider, also our WordPress hosting provider, suggested…

“we’ve observed that the production URL is failing during our debugging, it seems to be a compatibility issue on the webhook side. Could you please bring this to the attention of the n8n support team and check if they can offer any insights on the issue?”

Thanks

Sam_Mubie · January 9, 2025, 9:14am

It has been 8 days already for this simple question, is anybody there?

Jon · January 14, 2025, 9:37am

Hey @Sam_Mubie,

Sorry for the delay, Community support can sometimes take a while depending on what we are doing and how many other support requests come in but we will eventually always get back to the question.

Have you checked the execution log for your workflow to see if it is failing to start or manually making a post request with curl to see if it is working? I know we have other customers using Forminator with no issues so it should be working.

Sam_Mubie · January 15, 2025, 12:25am

Hi @Jon

Thanks for response.

There is nothing in the execution log, since production workflow never happen.

As mentioned above, test url was working correctly, but the production url in postman will get 500 Internal Server Error, message": “Error in workflow”

Forminator provider, also our WordPress hosting provider, suggested…

“we’ve observed that the production URL is failing during our debugging, it seems to be a compatibility issue on the webhook side. Could you please bring this to the attention of the n8n support team and check if they can offer any insights on the issue?”

Thanks

Sam_Mubie · January 21, 2025, 10:54pm

It’s 7 days again, we are still paying for your service, BUT YOU LEAVE US IN THE MIDDLE OF NOWHERE !!!

Can you just tell us what is the difference in between your test URL and Production URL in term of server environment?

Thanks

Sam_Mubie · January 21, 2025, 11:06pm

As you can see there are some areas where the production URL is failing that the test URL is not failing.

Jon · January 22, 2025, 3:23am

Hey @Sam_Mubie

In terms of the url there should be no difference between the test and production url as it will point to the same server and the same instance of n8n the only difference is a production run is ran in the background and will run the full workflow instead of one node.

It looks like your tests are using a GET method but I would expect it to be a POST request, if you can get the actual response it will be useful as that will tell us a lot more.

The “error in workflow” message would suggest that for some reason there is an issue with the workflow that is calling a failure so I would expect those to be logged.

Can you share your tests I can run them against another cloud instance and see if we get the same results, I will then also be able to debug it by comparing it against the instance logs.

Sam_Mubie · January 22, 2025, 3:40pm

Hi @Jon

Found in debug.logs…

For saving the test URL, it shows some fields are included successfully.
[22-Jan-2025 14:58:33 UTC] [Forminator] [“[ADDON]”,”Forminator_Webhook_Form_Settings::setup_webhook_url”,{“name”:”Forminator2n8n4certificate”,”webhook_url”:”https://lizenfdt.app.n8n.cloud/webhook-test/cbaa024d-61bf-42e6-99f4-84cf8adbb796″}]
[22-Jan-2025 14:58:33 UTC] [Forminator] [“[ADDON]”,”Forminator_Webhook_Settings_Trait::validate_and_send_sample”,”https://lizenfdt.app.n8n.cloud/webhook-test/cbaa024d-61bf-42e6-99f4-84cf8adbb796″]
[22-Jan-2025 14:58:35 UTC] [Forminator] [“[ADDON]”,{“headers”:{“host”:”lizenfdt.app.n8n.cloud”,”user-agent”:”WordPress/6.7.1; https://see.architdz.com ForminatorWebhook/1.0″,”content-length”:”922″,”accept”:”application/json”,”accept-encoding”:”gzip, br”,”cdn-loop”:”cloudflare; loops=1; subreqs=1″,”cf-connecting-ip”:”66.42.62.238″,”cf-ew-via”:”15″,”cf-ipcountry”:”SG”,”cf-ray”:”9060672487928959-SIN”,”cf-visitor”:”{\”scheme\”:\”https\”}”,”cf-worker”:”n8n.cloud”,”content-type”:”application/json”,”x-forwarded-for”:”66.42.62.238, 172.70.147.86″,”x-forwarded-host”:”lizenfdt.app.n8n.cloud”,”x-forwarded-port”:”443″,”x-forwarded-proto”:”https”,”x-forwarded-server”:”traefik-prod-users-gwc-4-644c4bcdb9-zt652″,”x-hook-test”:”true”,”x-is-trusted”:”yes”,”x-real-ip”:”66.42.62.238″},”params”:{},”query”:{},”body”:{“text_1″:”\u670d\u52d9\u55ae\u4f4d”,”text_2″:”\u8077\u7a31″,”select_3″:”\u5317\u5340\u6240\u5728\u7e23\u5e02″,”select_4″:”\u4e2d\u5340\u6240\u5728\u7e23\u5e02″,”select_5″:”\u5357\u5340\u6240\u5728\u7e23\u5e02″,”text_4″:”\u6d77\u5916\u570b\u5bb6″,”name_1″:”\u4e2d\u6587\u59d3\u540d”,”radio_3″:”\u6027\u5225″,”email_1″:”Email”,”text_3″:”LINE ID”,”phone_1″:”\u624b\u6a5f\u865f\u78bc”,”select_2″:”\u5b78\u7a0b”,”select_1″:”SEE\u63a8\u5ee3\u5340\u57df”,”date_1″:”SEE 101\u5165\u9580\u8ab2\u7a0b\u5b8c\u6210\u65e5\u671f”,”upload_1″:{“name”:”\u8acb\u4e0a\u50b3SEE 101\u7d50\u696d\u8b49\u66f8\uff08\u4e2d\u6587\u6216\u82f1\u6587\u7248\u7686\u53ef\uff09″,”type”:”image/png”,”size”:0,”file_url”:”https://see.architdz.com”,”file_path”:”/var/web/site/public_html/wp-content/uploads/sites/17″},”hidden_2″:”Submitted Date”,”hidden_1″:”Submitted Time”,”form_title”:”Course Enrollment Form”,”entry_time”:”2025-01-22 22:58:33″},”webhookUrl”:”https://lizenfdt.app.n8n.cloud/webhook-test/cbaa024d-61bf-42e6-99f4-84cf8adbb796″,”executionMode”:”test”}]
But for saving the Production URL, no field included, not sure this “WordPress database error” are related or not?
[22-Jan-2025 14:58:47 UTC] WordPress database error Unknown column ‘id’ in ‘field list’ for query SELECT COUNT(id) ‘FROM wp_9_nxs_query WHERE timetorun<\’2025-01-22 22:58:47\” made by do_action_ref_array(‘nxs_querypost_event’), WP_Hook->do_action, WP_Hook->apply_filters, nxs_checkQuery
[22-Jan-2025 14:58:51 UTC] [Forminator] [“[ADDON]”,”Forminator_Webhook_Form_Settings::setup_webhook_url”,]
[22-Jan-2025 14:59:12 UTC] [Forminator] [“[ADDON]”,”Forminator_Webhook_Form_Settings::setup_webhook_url”,{“name”:”Forminator2n8n4certificate”,”webhook_url”:”https://lizenfdt.app.n8n.cloud/webhook/cbaa024d-61bf-42e6-99f4-84cf8adbb796″}]
[22-Jan-2025 14:59:12 UTC] [Forminator] [“[ADDON]”,”Forminator_Webhook_Settings_Trait::validate_and_send_sample”,”https://lizenfdt.app.n8n.cloud/webhook/cbaa024d-61bf-42e6-99f4-84cf8adbb796″]]

Sam_Mubie · January 22, 2025, 3:50pm

Not quite sure what tests to share, can you elaborate more…

Thanks

Jon · January 22, 2025, 11:29pm

The error in the debug log is referencing a Wordpress database and table this is not something we would have control over it could also be unrelated to the post not working.

With the tests you shared a screenshot of what I assume to be postman tests, can you share them?

Sam_Mubie · January 23, 2025, 4:30am

Hi @Jon

I installed another plugin “Log HTTP Requests” recommended by Forminator provider, got the logs as following:

When saving the test URL, it got response 200 with all the fields name in the body.
When saving the Production URL, got response:

{
  "headers": {},
  "body": "{\"message\":\"Error in workflow\"}",
  "response": {
    "code": 500,
    "message": "Internal Server Error"
  },
  "cookies": [],
  "filename": null,
  "http_response": {
    "data": null,
    "headers": null,
    "status": null
  }
}

and the Request

{
  "method": "POST",
  "timeout": 5,
  "redirection": 5,
  "httpversion": "1.0",
  "user-agent": "WordPress/6.7.1; https://see.architdz.com ForminatorWebhook/1.0",
  "reject_unsafe_urls": false,
  "blocking": true,
  "headers": {
    "Accept": "application/json",
    "Content-Type": "application/json",
    "X-Hook-Test": "true"
  },
  "cookies": [],
  "body": "{\"text_1\":\"\\u670d\\u52d9\\u55ae\\u4f4d\",\"text_2\":\"\\u8077\\u7a31\",\"select_3\":\"\\u5317\\u5340\\u6240\\u5728\\u7e23\\u5e02\",\"select_4\":\"\\u4e2d\\u5340\\u6240\\u5728\\u7e23\\u5e02\",\"select_5\":\"\\u5357\\u5340\\u6240\\u5728\\u7e23\\u5e02\",\"text_4\":\"\\u6d77\\u5916\\u570b\\u5bb6\",\"name_1\":\"\\u4e2d\\u6587\\u59d3\\u540d\",\"radio_3\":\"\\u6027\\u5225\",\"email_1\":\"Email\",\"text_3\":\"LINE ID\",\"phone_1\":\"\\u624b\\u6a5f\\u865f\\u78bc\",\"select_2\":\"\\u5b78\\u7a0b\",\"select_1\":\"SEE\\u63a8\\u5ee3\\u5340\\u57df\",\"date_1\":\"SEE 101\\u5165\\u9580\\u8ab2\\u7a0b\\u5b8c\\u6210\\u65e5\\u671f\",\"upload_1\":{\"name\":\"\\u8acb\\u4e0a\\u50b3SEE 101\\u7d50\\u696d\\u8b49\\u66f8\\uff08\\u4e2d\\u6587\\u6216\\u82f1\\u6587\\u7248\\u7686\\u53ef\\uff09\",\"type\":\"image\\/png\",\"size\":0,\"file_url\":\"https:\\/\\/see.architdz.com\",\"file_path\":\"\\/var\\/web\\/site\\/public_html\\/wp-content\\/uploads\\/sites\\/17\"},\"hidden_2\":\"Submitted Date\",\"hidden_1\":\"Submitted Time\",\"form_title\":\"Course Enrollment Form\",\"entry_time\":\"2025-01-23 12:08:35\"}",
  "compress": false,
  "decompress": true,
  "sslverify": true,
  "sslcertificates": "/var/web/site/public_html/wp-includes/certificates/ca-bundle.crt",
  "stream": false,
  "filename": null,
  "limit_response_size": null,
  "_redirection": 5
}

Jon · January 23, 2025, 2:41pm

Hey @Sam_Mubie,

That is error is n8n saying there is a problem in your workflow, As a quick test I have set up a simple workflow with just a Webhook node set to Accept Post requests, I have then aken the Body from your request and converted it to JSON and popped it into Postman.

Here we have the /webhook-test/ endpoint

and in n8n running in our Cloud

and for a production url

in my execution log I have this

Based on this testing and your error message I don’t think the issue is with the n8n environment itself and I suspect it is an issue with your workflow somewhere.

As a test can you try the same workflow and see if it works that will then either confirm this is an issue with the workflow and we can start looking there or it will tell me it is an issue with your cloud instance.

Sam_Mubie · January 23, 2025, 3:20pm

Hi @Jon

The workflow has been running successfully in Test URL since I reported this issue.
Please see the screen recording 23.01.2025_23.14.39_REC

Sam_Mubie · January 23, 2025, 3:25pm

Actually, same issue with this workflow autoWP.json same using Forminator form.

Jon · January 23, 2025, 3:50pm

Hey @Sam_Mubie,

The problem is this video is not trying a more simple workflow as requested. I want to rule out anything odd that may be happening, As an example when you run a workflow using the test button some of the expression evaluations are done in the frontend and not the backend so there can at times be differences.

That second workflow you have shared has the webhook set to respond with a respond to webhook node but you don’t have one of these for a successful completion, This means you will likely get a 524 status back because it will time out.

Sam_Mubie · January 23, 2025, 4:28pm

Hi @Jon

I copied the workflow to make it only 2 nodes, still same issue.

Test URL ran successfully, but saving production url got Internal Server Error.

Sam_Mubie · January 24, 2025, 1:53pm

The support team of Forminator provided some information as following…

The HTTP requests provided above, helped both sides to see that the request type is POST, as opposed to their initial finding as GET.

The above further entails that an unknown aspect is likely causing the issue brought about by the Production env in contrast to testing/staging env.
…

They will provide the copy of the Postman testing JSON file later.

Jon · January 25, 2025, 5:15am

Hey @Sam_Mubie

As previously mentioned there is no difference between the prod and test url in terms of environment or routing they both point to the same n8n instance the only difference is one url triggers the front end and the other triggers the backend.

Can you share the output when you tried the run the workflow with only the webhook node using the production url? You have added an http request node to the mix as well which is not what I suggested as I want to rule out other nodes causing an issue.

If this is not something you can do can you send an email to [email protected] saying you give permission for support to access your instance and I will test your instance directly and share the results.

Sam_Mubie · January 25, 2025, 3:13pm

Hi @Jon

You are right, I tried a workflow with 2 nodes only, no more “Internal Server Error” when saving the production url.

So the problem is inside the workflow. I will send an email to [email protected] for permission to have your help to find out which node is the cause of problem.

Thanks

Sam_Mubie · January 25, 2025, 3:35pm

Hi @Jon

It seems getting clear that the problem should cause by HTTP Request, since the difference in between autoWP2 and Forminator2moodle2ai is Settings node against HTTP Request node.

I will do some more test tomorrow, but if you have any suggestion, it is appreciated.

Have a nice weekend.