404 error with new WP module, ok Legacy WP

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:

<IfModule mod_security.c> 
SecRuleRemoveById 400011 
SecRuleRemoveById 400012 
</IfModule>

Please let us know what you find!

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 1 year, 8 months ago by razonmasfe.

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)?

Thanks again. I did it, change it to “Simple”, eliminating the trailing slashes and tried

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?

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://<yoursite>/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.

I did it, and appears to be working fine:

https://www.razonmasfe.com/wp-content/uploads/2023/07/Posman-Rest-Api.jpeg

• This reply was modified 1 year, 8 months ago by razonmasfe.

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.

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. ???♂?

In the logs I can see this. Like the api key was not save in server?

My note about authorization on the Types endpoint was incorrect – apologies. Authorization isn’t needed for that endpoint.

@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?

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.

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;
			}

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.