Error: No route was found matching the URL and request method

Watching this as I have the very same issue as of Monday. I am unable to save updates to records and get the ‘no route was found matching the URL and request method’ error. I have reached out to FluentCRM and and they are looking into it.

I have just checked another site at it has the the same issue.

Hello @kutatishh and @markninnims,

Thanks for sharing the details! We’ve noticed that several of our clients are experiencing similar issues with FluentCRM, particularly when updating contacts or creating campaigns. Interestingly, they are all hosted on Flywheel.

Could you please confirm which hosting provider you’re using? This will help us determine if the issue is related to specific hosting configurations.

If you’re using Flywheel or another hosting provider, I recommend reaching out to their support team to check if PUT requests are being blocked by default. FluentCRM relies on PUT requests during both campaign creation and contact updates. It’s possible that your server configuration may need to be adjusted to allow these requests for FluentCRM to function correctly.

Please let us know how it goes and what your hosting provider respond, and we’ll continue looking into this issue. Since this is an investigational matter, it would be best to continue the conversation on our official support portal.

Best Regards,

Thank you and yes, I am using Flywheel but have done for years and your plugin has worked flawlessly?

Thanks for your update, @markninnims. Since you’re using Flywheel, which has worked flawlessly for you in the past, could you share if there was any specific update or change after which you started encountering this issue? That might help us pinpoint the cause.

Please know that our developers are actively investigating this, and we are also in communication with Flywheel regarding any potential server-related factors that might be causing this. As soon as we find the exact cause, we will update you immediately.

In the meantime, I would also suggest opening a support ticket on our official portal, so we can continue working on this directly with you.

Best Regards,

Thank you.

I haven’t made any changes which is the odd thing? I think this has been isolated to a PUT or PUSH issue and I have open tickets with both Flywheel and Fluent.

Fingers crossed we get a resolution soon.

Thank you, and yes I am using Flywheel as well! I will share your message with them and hopefully we get a resolution. Similar to @markninnims, I’ve been using Flywheel for quite a long time and have not had issues on FluentCRM. Thanks for the quick reply.

With regards to submitting a ticket with FluentCRM support, do we need to have a Pro license? I’m just running the free version at the moment.

Hello @markninnims and @kutatishh,

Thank you for the updates. It’s great to hear that you’ve both reached out to Flywheel support regarding the issue, and we’re hopeful that it will be resolved soon.

@kutatishh, regarding your question about submitting a support ticket: while Pro users have access to priority support, you’re still welcome to submit a ticket even if you’re using the free version of FluentCRM. We do our best to assist all users regardless of the version. Feel free to reach out through our official support portal, and we’ll continue there.

Best regards,

Thank you!

I just received this reply from Flywheel:

“…It looks like this may be related to the X-Http-Method-Override header. This header is used to allow POST requests to override the method type. This header [has recently been] disabled across our platform as it opens up potential vulnerabilities. I would recommend reaching out to Fluent Form’s development team to confirm if they use this header – if they do, they may need to implement an alternative method of achieving this, so the plugin remains compatible with our platform.”

Would love to hear if there’s any workaround? Wouldn’t want to switch plugins or host at this stage.

Hello?@kutatishh ,

Thank you for your detailed response and for bringing this to our attention.

We would like to clarify that there is no security vulnerability in our code. The usage of the X-HTTP-Method-Override header is quite common and widely accepted in web applications and WordPress plugins that work with REST APIs. This issue appears to be specific to Flywheel, as none of our users on other servers are encountering it.

We recommend enabling the X-HTTP-Method-Override header specifically for your website at the server level and configuring a Web Application Firewall (WAF) to restrict access to the FluentCRM API endpoints. This approach will help maintain security while addressing Flywheel’s concerns.

Additionally, if possible, we suggest excluding the FluentCRM REST API routes from Flywheel’s caching layer to prevent any potential issues.

We appreciate you sharing Flywheel’s response. In the meantime, please consider opening a support ticket with us so we can continue the conversation and address this matter more directly.

Thank you again for your cooperation and understanding.

Hello @kutatishh and @markninnims,

Could you please confirm if this has resolved the problem on your end? If the issue persists, we recommend contacting Flywheel to clear the server-side cache again and see if that helps. Once you’ve done that, please let us know if the problem is resolved or further assistance is needed.

Best Regards,

Thank you for following up. My issue seems to have been resolved with a different version of Fluent CRM but Flywheel have also confirmed that they have made changes their end too.

Hello @markninnims,

Thank you for the update! It’s great to hear that the issue was resolved after trying a different version of FluentCRM and that Flywheel has also made changes on their end.

If further assistance is needed, feel free to reach out, and we’ll be happy to help!

Best Regards,