Which Replikanto server endpoints should my firewall allow?

Yes, Replikanto has server-side endpoint URLs. If you use the Remote Copy feature to send trades from one Replikanto instance to another over the internet, that traffic goes through Replikanto's servers rather than a direct connection between the two machines.

These endpoints are not only for Remote Copy. Every Replikanto contacts api.replikanto.com each time NinjaTrader starts, to activate the license, even if you never copy trades between machines. A firewall or antivirus that blocks it affects every Replikanto user on that machine.

Endpoints

The two relevant endpoints are:

• api.replikanto.com — the API endpoint (license activation and Remote Copy)
• wss.replikanto.com — the WebSocket (WSS) endpoint (Remote Copy)

Firewall Configuration

Both endpoints use port 443 (HTTPS/WSS). If your firewall supports domain-based rules, allow the domain names directly. If your firewall requires IP addresses instead, use the current IPs below.

Notes on IP-based rules

• Allow all IPs listed for a given domain — they are load-balanced.
• These IPs are hosted on AWS infrastructure and may change during maintenance or scaling events.
• Where possible, configure your firewall to use DNS resolution (domain-based rules) instead of hardcoded IPs, for better long-term reliability.

Alternate endpoints

When a main endpoint cannot be reached, Replikanto switches to an alternate one. If your firewall only allows specific domains, also allow these on port 443:

• jol6nau3w0.execute-api.eu-west-2.amazonaws.com — alternate API endpoint, used when api.replikanto.com does not answer
• u2ngp3k7z7.execute-api.us-east-1.amazonaws.com — alternate WebSocket endpoint, used when resolving wss.replikanto.com takes too long

Replikanto also looks up the machine's public IP address at ipinfo.io. If that lookup is blocked, Replikanto keeps working.

What happens if a firewall or antivirus blocks these endpoints

Some firewalls and antivirus programs do not refuse a blocked connection; they silently drop the packets, so the connection just waits.

• Up to Replikanto 1.6.1.7: NinjaTrader could freeze at start-up, or when you opened a Replikanto tab, with no error message.
• Starting with Replikanto 1.7.0.0: NinjaTrader no longer freezes. Every call to the Replikanto servers has a time limit. If the license still cannot be activated after a few attempts (this can take a minute or two), Replikanto shows the message "Replikanto is having problems connecting to its license servers..." and closes its windows.

In that case the NinjaTrader Log tab shows:

Replikanto: [License] Could not reach the Replikanto server to activate this machine. Every Replikanto window will be closed; check the internet connection, any proxy and any firewall rule that blocks replikanto.com.

To fix it, allow the endpoints above on port 443 in your firewall and antivirus (and proxy, if you use one), then restart NinjaTrader.

If the Log shows Info [1068] ("Resolving the primary WebSocket host through DNS took longer than 2000 ms, so Replikanto did not wait and is using the alternate endpoint"), Replikanto is using the alternate WebSocket endpoint because DNS was slow. This is informational and Replikanto keeps working normally.