German AWS but need US IP address?

Questions
1

:bullseye: What is your goal?

U.S. IP to access U.S. websites via Custom JS and Puppeteer.

:thinking: What is the problem & what have you tried?

Make uses German AWS servers even for U.S. customers trying to access U.S. websites. Dumb! It’s caused me days of delays and there seems to be no way to change it outside or inside of my scenario. Has anyone found a way to use U.S. IPs w U.S. websites so they don’t redirect?

:clipboard: Error messages or input/output bundles

Redirects to German landing page :confused:

6

I believe this depends on the region of your Make instance, what region are you in? e.g.
Scherm­afbeelding 2026-01-08 om 10.28.13

Cheers,
Henk

1 Like
7

Hello,

as @Henk-Operative just said, it depends on where your Organization is deployed. if your URL starts with eu1, eu2, it’s located in Europe (Dublin, or Frankfort if you are in the Enteprise plan), hence the european Egress IPs.

If it starts with us1 or us2, the Data Center is based in USA, so the Egress IP addresses will be in USA.

Check here for the list of Egress IPs for each location: Allow connections to and from Make IP addresses - Help Center.

Can you let us know the url of your Organization.

Kind regards,

Benjamin

1 Like
8

I consulted for days with AI and today we finally identified the cause of the “Germany” U.S. redirect problem (and yes my Region Org setting in Make are U.S, and org URL is U.S. too):
[
{
“output”: “<meta name="color-scheme" content="light dark"><meta charset="utf-8">

{"ip_version":4,"country":"DE","asn":{"asnum":16509,"org_name":"AMAZON-02"},"geo":{"city":"Frankfurt am Main","region":"HE","region_name":"Hesse","postal_code":"60313","latitude":50.1169,"longitude":8.6837,"tz":"Europe/Berlin","lum_city":"frankfurtammain","lum_region":"he"}}
<div class="json-formatter-container">”
}
]

Germany is coming from Puppeteer on CustomJS.Space’s servers :confused:

How do we consistently make Make tell CustomJS to use U.S. only IPs?

AI just says I need to pay for another service, proxies, to get U.S… but this is dumb to keep adding a band-aid on top of CustomJS rather than CustomJS respecting me, Make, and letting us define U.S. without needing to pay more to override it.

9

So if I understand you correctly, your Make instance is US based but the egress IP is German because of the CustomJS servers on which you run puppeteer? There is no blame on Make then.

Make has its own app to run custom JS, although you can only add custom libraries on the Enterprise plan: Make Code - Apps Documentation

AI is a not a very good consultant, it is only moderately ok with guessing the next word to return. If CustomJS cannot offer you an egress IP choice, look for an alternative to host your script. Xano is an option, although the setup might be more complex.

Cheers,
Henk

10

But why doesn’t make just host JS natively to run it on US servers rather than force us to use external
JS hosting, pay another subscription, and not only do they have zero region selection features, they also have zero customer support. So I spent my whole day ripping out all dependency on crappy CustomJS and replacing it with much easier to use Axiom, which they also say on their website has integration issues with Make since they switched from Integromat. So yup Make has some massive improvements to do too: fix the Axiom integration, boot the CustomJS integration and make it native to preserve and respect region selection.

11

Make does allow you to run JS natively, and does it in whatever region your Make account is. That is what the Make Code app is for, this is built by Make. CustomJS is a third party app running code on their own servers, fully separated from Make. So it hasn’t anything to do with Make, honestly. If CustomJS is a suboptimal experience, CustomJS is the service that should improve.

1 Like