Hello,
I am an n8n user currently integrating my WordPress website with n8n workflows.
My website is hosted on IONOS, and after multiple tests and exchanges with their technical support, it has been confirmed that IONOS blocks HTTP requests when the User-Agent header is shorter than 4 characters.
Unfortunately, the WordPress node in n8n appears to use a very short or non-standard User-Agent, which causes IONOS to block the requests and return a 503 “Service unavailable” error page before WordPress even receives the API call.
When using the HTTP Request node with a custom User-Agent (for example a standard browser-like User-Agent), everything works correctly with the WordPress REST API. However, when using the native WordPress node, the requests are consistently blocked by IONOS.
After checking the n8n community forum, it seems this is a known issue that has affected other users as well, particularly on hosting providers with stricter security or WAF rules.
I would like to ask if there is any possibility on your side to:
- Allow customization of the User-Agent in the WordPress node, or
- Use a longer, more standard User-Agent by default in the WordPress integration
This would greatly improve compatibility with hosting providers such as IONOS.
Thank you very much for your time and for the great work on n8n.
Best regards,