Title: 404 error with new WP module, ok Legacy WP
Last modified: July 16, 2023
---
# 404 error with new WP module, ok Legacy WP
* [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* (@razonmasfe)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/)
* Since I updated the WordPress CMS to 6.2, the MAKE.COM connection with WordPress
broke, and cannot get information through the Rest API for the WordPress Make
modules (new version).
* > [404] No se ha encontrado ninguna ruta que coincida con la URL y el método
> de la solicitud. (error code: rest_no_route).
* 
* Nevertheless, the old Make **Legacy **Wordpress are partially working, at least
they can post on the site:
* 
* So it seems it may have something to do with the structure of the info that cannot
get parsed correctly
* 
* I have disabled most of the plugins (just left make and Content Studio plugins),
but the problem continues…
* Any idea about what to do?
* I´ve been in contact with Make.com service desk and they have tried to solve
this, but eventually suggested to post it here…
- This topic was modified 2 years, 9 months ago by [razonmasfe](https://wordpress.org/support/users/razonmasfe/).
- This topic was modified 2 years, 9 months ago by [razonmasfe](https://wordpress.org/support/users/razonmasfe/).
* The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2F404-error-with-new-wp-module-ok-legacy-wp%2F%3Foutput_format%3Dmd&locale=en_US)
to see the link]_
Viewing 12 replies - 1 through 12 (of 12 total)
* [davidgurr](https://wordpress.org/support/users/davidgurr/)
* (@davidgurr)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16899735)
* We’ve tested the Make plugin with versions up to 6.2.2 (June 2023) so it should
work.
* I’d suggest first disabling the Content Studio plugin too to see if that has
an effect.
* If not, it’s likely to be something in your .htaccess file. The exact cause (
and hence solution) might vary, but one user has found that adding the following
to their .htaccess file resolved a similar problem:
* ```wp-block-code
SecRuleRemoveById 400011
SecRuleRemoveById 400012
```
* Please let us know what you find!
* Thread Starter [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* (@razonmasfe)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16902172)
* Thanks David for your quick reply!
* I did deactivate all the plugins but make, and the result is the same.
* Yes, I updated the .htaccess with those lines and it allowed me to pass from
the 403 error, to the present 404 error. Before there was no connection because
of some firewall, but now the connection is made, only it is not actionable,
because of the “rest_no_route”. And you can see that it retrieves some information,
but not in the format it is required by Make.
* At least thats the conclusion that I get from the logs when I run the modules.
* Any other idea?
- This reply was modified 2 years, 9 months ago by [razonmasfe](https://wordpress.org/support/users/razonmasfe/).
* [davidgurr](https://wordpress.org/support/users/davidgurr/)
* (@davidgurr)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16902832)
* Right, now I understand! You won’t get any sensible output from the `Watch Posts`
module until we can resolve the 404 error that you’re getting in the `Type `field.
* This seems to be as a result of something you’ve set in your WordPress configuration
that’s interfering with REST API endpoints. Other plugins can do that, but one
other area is in Permalinks.
Sometimes Permalink configuration adds or removes
a trailing slash when it’s not needed. Could you check your Permalink configuration
and try it with the opposite (i.e. removing the trailing slash if it’s there,
or adding it if it isn’t)?
* Thread Starter [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* (@razonmasfe)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16913895)
* Thanks again. I did it, change it to “Simple”, eliminating the trailing slashes
and tried
* [https://nimb.ws/ND7Av4](https://nimb.ws/ND7Av4)
* But I´ve got the same 404 error. Then I put the trainling slashes back again
and tried, but nothing happened…
* Any other idea?
* [davidgurr](https://wordpress.org/support/users/davidgurr/)
* (@davidgurr)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16918275)
* The 404 error you’re getting in the Watch Posts module UI is where the UI is
trying to retrieve the available Post Types from your site, and it’s failing.
The endpoint it’s trying to reach is `https:///wp-json/wp/v2/types`
* If you’re familiar with Postman, try a GET request on that URL.
Authorization
is `API Key` with a `Header` key of `iwc-api-key` and the `Value` as your API
Key from the Make WordPress plugin.
* Thread Starter [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* (@razonmasfe)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16923004)
* I did it, and appears to be working fine:
* [https://www.razonmasfe.com/wp-content/uploads/2023/07/Posman-Rest-Api.jpeg](https://www.razonmasfe.com/wp-content/uploads/2023/07/Posman-Rest-Api.jpeg)
- This reply was modified 2 years, 9 months ago by [razonmasfe](https://wordpress.org/support/users/razonmasfe/).
* [davidgurr](https://wordpress.org/support/users/davidgurr/)
* (@davidgurr)
* [2 years, 9 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-16926491)
* Sorry for the delay in responding. Best next step is to check your WordPress
server logs for when you’re opening the Watch Posts module and getting the 404
error in the UI. It seems likely that this is triggering some other modsecurity
rule.
* If it’s not that, your hosting provider’s firewall might be blocking some access
from Make. It would be worth getting them to check that they’re not blocking
any of [our IP addresses](https://www.make.com/en/help/connections/allowing-connections-to-and-from-make-ip-addresses).
* [Rubén Alonso](https://wordpress.org/support/users/rubenalonsoes/)
* (@rubenalonsoes)
* [2 years, 8 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17021089)
* I’m having the same issue. In my case, i’ve tried with Postman and if I put the
iwc-api-key header get me the 404. But works fine without that header. 🤷♂️
* [Rubén Alonso](https://wordpress.org/support/users/rubenalonsoes/)
* (@rubenalonsoes)
* [2 years, 8 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17021155)
* In the logs I can see this. Like the api key was not save in server?
* 
* [davidgurr](https://wordpress.org/support/users/davidgurr/)
* (@davidgurr)
* [2 years, 8 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17023307)
* My note about authorization on the Types endpoint was incorrect – apologies.
Authorization isn’t needed for that endpoint.
* [@rubenalonsoes](https://wordpress.org/support/users/rubenalonsoes/) is that
log entry for when you’re getting a 404 error in the Make UI? Do you see exactly
the same as the OP in their first screenshot?
* [Rubén Alonso](https://wordpress.org/support/users/rubenalonsoes/)
* (@rubenalonsoes)
* [2 years, 8 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17023343)
* That’s it. I “solved” the problem temporarily by deleting/commenting some lines
in the plugin’s api/authentication.php file where it returned the error apparently
if it did not find the api key (abou line number 39).
Is like the token is not
saved in the $_SERVER variable.
* ```wp-block-code
if ( strlen( $token ) !== \Integromat\Api_Token::API_TOKEN_LENGTH || ! \Integromat\Api_Token::is_valid( $token ) ) {
$log && \Integromat\Logger::write( 6 );
\Integromat\Rest_Response::render_error( 401, 'Provided API key is invalid', 'invalid_token' );
} else {
/*\Integromat\User::login( $user_id );
$log && \Integromat\Logger::write( 7 );
\Integromat\Rest_Request::dispatch();*/
return $result;
}
```
* Thread Starter [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* (@razonmasfe)
* [2 years, 5 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17176431)
* After trying different things and asking for help to different people expert
in WordPress, it solved suddenly, probably some update on Make´s end…Thanks David
for your support.
Viewing 12 replies - 1 through 12 (of 12 total)
The topic ‘404 error with new WP module, ok Legacy WP’ is closed to new replies.
* 
* [Make Connector](https://wordpress.org/plugins/integromat-connector/)
* [Support Threads](https://wordpress.org/support/plugin/integromat-connector/)
* [Active Topics](https://wordpress.org/support/plugin/integromat-connector/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/integromat-connector/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/integromat-connector/reviews/)
## Tags
* [integration](https://wordpress.org/support/topic-tag/integration/)
* 12 replies
* 3 participants
* Last reply from: [razonmasfe](https://wordpress.org/support/users/razonmasfe/)
* Last activity: [2 years, 5 months ago](https://wordpress.org/support/topic/404-error-with-new-wp-module-ok-legacy-wp/#post-17176431)
* Status: not resolved