I’m currently working through the N8N102 course and have run into an issue with the Webhook Assessment Tool that I haven’t been able to resolve.
After correctly configuring my webhook (details below), submitting the form causes the page to render as a completely blank white screen. I’ve tried the following to rule out a local issue:
The issue persists across all of the above.
@Lewis_Crate thats not your workflow, the N8N102 webhook tester endpoint blanking is a known academy-side bug, it got reported and marked fixed here Webhook-tester endpoint is responding blank but looks like its back. since youve already ruled out browser/cache its on their end, nothing to change in your n8n. worth flagging on that thread so the academy team knows its regressed.
look like that ticket was marked solved so i cant reply on it for now, thank you though
@jamiemadden_n8n This user is having the same issue that apparently got fixed, did it regress?
Hello,
Which step is it blanking on testing? Can you also message me your assessment_id and your workflow.
cheers,
Hi there it was step 1 in the webhook test, where you have to test the webhook set up with assessment id. i have just sent you a message
@jamiemadden_n8n Assessment ID: cecdfade24ca490151a54c15ec5e17c4
This isn’t a known bug and I’m unable to replicate it at this time. I continue to add more and more validation for edge cases as they show up.
I am unsure if my scenario is valid, but I have encountered this blank screen before when using the ‘test’ webhook URL (e.g, ``https://host.name/webhook-test/course/n8n102/new-order``) and clicking ‘execute webhook’ to listen for events. I am aware that in this mode, the system only listens and responds to the first webhook call from the tester, meaning the other 2 subsequent calls from Step 1 are going to the void. I hope this assists with your investigation.
Below is the result. But I also notice that if we check “Disable Cache” in the console, the same behaviour won’t trigger a blank page.
@Lewis_Crate can you screenshot your console when you access the page?
Their issue has been resolved.
I’ve added another note in the unit to highlight that the webhook must be published for the webhook tester to work.
