Subject: Bug report – HTTP & WordPress modules cannot reach my domain (trendixdigital.com) from Make Europe region
Hi Make Support,
I’m opening this ticket again because the previous replies only stated that my website URL “does not open”, which is not accurate and does not address the actual problem.
This is not an issue with my website being down.
It is a very specific connectivity/validation issue between the Make Europe environment and my domain trendixdigital.com.
I’ll summarize first, and then give all the detailed tests I’ve done.
1. TL;DR (summary)
-
From any browser or external tool (outside Make), my domain trendixdigital.com works normally:
-
website loads,
-
WordPress REST API at https://trendixdigital.com/wp-json/ works,
-
static files (including .ogg files) are accessible.
-
From Make (Europe region), whenever I use the hostname trendixdigital.com in the URL, I get errors such as:
-
However, from Make I can reach the same server by using its raw IP 166.0.186.20 and setting the Host: trendixdigital.com header manually. In that case, requests return 200 OK and the file/API responds correctly.
-
DNS on my side is simple (A record only, no AAAA), SSL certificate is valid for trendixdigital.com, and the hosting provider confirms the site is working.
-
This strongly suggests a bug or misconfiguration on Make’s side (in host/IP validation or DNS resolution in the Europe region) for this specific hostname.
I kindly ask that you escalate this to engineering/infra instead of just checking the website from a browser and saying it doesn’t open.
2. Environment / region
3. Problem 1 – HTTP module with audio file URL
I have a scenario where I need to download audio files from:
https://trendixdigital.com/audios/AC62F8FDB4F0D7B942AFB935C378623F.ogg
(and similar files in the same folder).
3.1. Failing configuration
HTTP module:
-
Method: GET
-
URL:
https://trendixdigital.com/audios/AC62F8FDB4F0D7B942AFB935C378623F.ogg
-
No headers, no body, Parse response = No.
Result in Make:
InvalidConfigurationError – IP address is not valid
Origin: Make
Important:
The same error appears if I switch to:
http://trendixdigital.com/audios/...
So, both HTTP and HTTPS using the hostname fail with InvalidConfigurationError – IP address is not valid.
3.2. URL correctness validated
To make sure the URL itself was not malformed:
-
I added a Tools > Set variable module right before the HTTP module.
-
I built the URL exactly as used in the HTTP module.
-
The variable output shows a well-formed URL, for example:
https://trendixdigital.com/audios/AC62F8FDB4F0D7B942AFB935C378623F.ogg
-
In the same HTTP module, if I only change the URL to a public test endpoint, like:
https://jsonplaceholder.typicode.com/posts
the request works and returns 200 OK.
So the HTTP module and scenario configuration are correct; the error happens only when the hostname trendixdigital.com is used.
4. Problem 2 – WordPress module connection
I also tried to create a connection using the official WordPress app in Make, with:
The connection test fails with:
EAI_AGAIN: The service https://trendixdigital.com/wp-json/wp/v2/users/me is temporarily unavailable.
Again, this is not an API/authentication issue:
-
The endpoint https://trendixdigital.com/wp-json/wp/v2/users/me works correctly when called from a browser.
-
The Make Connector plugin is installed and configured.
-
The error EAI_AGAIN is a DNS / host resolution error from Node, which indicates Make is having trouble resolving or reaching the hostname trendixdigital.com.
5. Server / DNS side (hosting checks)
On my hosting side:
-
trendixdigital.com and www.trendixdigital.com both have an A record pointing to 166.0.186.20.
-
There is no AAAA (IPv6) record for the domain.
-
SSL certificate is valid for trendixdigital.com and *.trendixdigital.com.
-
The web interface (DirectAdmin) and logs show normal activity.
-
When Make returns InvalidConfigurationError or EAI_AGAIN, no request for /audios/... or /wp-json/... appears in the webserver logs.
I have also asked the hosting provider to check for:
and so far they confirm there is no explicit block for Make’s IP ranges and that the site is reachable from the internet in general.
6. Tests from Make using the raw IP
To isolate the problem, I ran several tests using the raw IP 166.0.186.20 from the same scenario in Make.
6.1. HTTPS with IP
URL:
https://166.0.186.20/audios/AC62F8FDB4F0D7B942AFB935C378623F.ogg
Result:
ERR_TLS_CERT_ALTNAME_INVALID: Hostname/IP does not match certificate's altnames: IP: 166.0.186.20 is not in the cert's list
This is expected, because the certificate is issued for trendixdigital.com, not for the IP.
The important point is:
6.2. HTTP with IP (no SSL)
URL:
http://166.0.186.20/audios/AC62F8FDB4F0D7B942AFB935C378623F.ogg
Result:
- Make receives 404 Not Found with the default LiteSpeed 404 page.
This indicates:
-
The connection is working.
-
The request is hitting the default virtual host (which is typical when using only the IP, without the proper Host header).
6.3. Working workaround – IP + Host header
Finally, I tried:
With this configuration, the HTTP module returns:
So, from Make:
The only configuration that consistently fails is when the hostname trendixdigital.com is used directly in the URL (http or https), where Make returns:
InvalidConfigurationError – IP address is not valid
or, in the WordPress module, EAI_AGAIN,
before any request reaches my server.
7. Why this looks like a Make-side bug
Based on all the tests:
-
HTTP module works with other domains in the same scenario.
-
HTTP module works with this same server when using the IP + Host header.
-
WordPress module fails only when using https://trendixdigital.com/wp-json/.
-
DNS for trendixdigital.com is a simple A record (no AAAA), SSL is valid.
-
The hosting provider confirms that the site and REST API are reachable from the internet.
-
Errors InvalidConfigurationError – IP address is not valid and EAI_AGAIN occur only from Make, not from browsers or other tools.
This strongly suggests an issue in:
-
how the Make Europe region resolves or validates the hostname trendixdigital.com, or
-
an internal rule/filter affecting this specific hostname/IP combination.
8. What I’m asking from you
Please:
-
Escalate this to your engineering/infra team for deeper investigation.
-
Specifically check, from the Europe region:
-
how trendixdigital.com is being resolved (DNS resolvers used, cached records, etc.);
-
whether there is any internal validation that could wrongly classify the IP as “not valid”;
-
whether there are any firewall / security rules on Make’s side affecting this hostname or IP.
-
Let me know if you need:
In the meantime, I am using the workaround (HTTP module with http://166.0.186.20/... + Host: ``trendixdigital.com), but I would very much like to use the normal HTTPS URLs with the hostname directly, and the official WordPress module.
Thank you for your attention, and I appreciate a detailed, technical reply rather than just a generic “the website does not open” answer.
Best regards,
Wellington Descrove
What is the problem?
What have you tried so far?
Screenshots: scenario setup, module configuration, errors
)