Contact Form Suddenly Not Working

[EinfachChris]

Our contact form worked perfectly for weeks and months. Around noon, we started getting reports that it was no longer working.

Firmenevents, Teamevents und Betriebsausflüge - CG Events

I'm absolutely certain I haven't changed anything in the last few weeks.

I then updated the project to the latest version using Wappler Updates.

Unfortunately, that didn't change anything either.

My first thought was that it might be related to reCAPTCHA. But that's not it either; even if I remove it completely, the form still won't submit.

Request URL
https://cg-events.de/api/public/anfrage/adAnfrage
Request Method
POST
Status Code
302 Found

Request URL
https://cg-events.de/404
Request Method
GET

For some reason, the request is returning a 404 error.

I have two forms that are absolutely identical.

One is accessed via the model, which is called through the button in the header.

And the other is directly at the bottom of the page.

Since it's peak season right now, I absolutely need the form to work properly, because that's when we do our business. If the form doesn't work, well, we simply can't.

Therefore, I would be extremely grateful for any quick help.

[franse]

Assuming this exist, I'm pretty sure it's a route problem, or a server problem:
https://cg-events.de/api/public/anfrage/adAnfrage:

Returns 404.

This is not only on your homepage form, saw it on partner page:

[franse]

BACKUP FIRST

Until someone appears here with a better idea, I suggest you to delete the /404 and check again: location under response headers

[EinfachChris]

Hi guys, I'm really at my wit's end here. I’ve done some deep-dive testing and the issue is still occurring.

What I've done for troubleshooting:

1. Fresh Environment: I created a completely new Layout page, a new Content page, and a brand-new Form.

2. Minimalist Server Action: The form points to a simple Server Action.

3. The Result: Even with this "barebone" setup, I get the exact same error: 302 Found redirecting to 404.

Current Observations:

• This happens on a POST request to the API.

• Since it's a 302, something in the Node.js middleware or routing is intercepting the request before it even processes the action logic.

• I've checked my Security Provider settings and Routing rules, but I can't find the trigger for this redirect.

Screenshot from the Network Tab (Fresh Setup):

Has anyone experienced a 302 redirect to 404 on a standard API POST? It feels like the server "sees" the route but then decides to bail out. Could this be a specific Wappler Node.js routing bug or a hidden setting in the routes.json?

Any fresh eyes on this would be a lifesaver.

[Cheese]

What version of Wappler are you running? There were fixes to address some routing issues in the most recent release.

One fix that may resolve your issue is that if you have a catch all route such as a wildcard '*' in your routes then API requests were being routed incorrectly in some circumstances. You can test this if you do have such a route then you can try and remove it and see if that alleviates the issue..? At least you can pinpoint it down to this. ALWAYS REMEMBER TO BACKUP your Project first though!

[TMR]

Think this may be related to the issue I’m having ….

[EinfachChris]

I'm using version 7.7.7.

For testing purposes, I removed all routes except for /, and then the form worked again.

Now I have a lot of routes, and as far as I know, I need them all.

I don't understand what an API has to do with the routes.
It worked before.

I have no idea how to proceed here...

[EinfachChris]

I found the error.

It was this four-level parameter route: /:p1/:p2/:p3/:p4