Firwall / Proxy issue when installing


We wish as part of a project to install on windows PCs, the unreal engine

Unfortunately we are blocked by our proxy and firewall during installation.

Can you tell us the ports, ip and protocols to open to ensure the correct installation and operation of the software?

Thanks in advance.

Hey there @Ybrault! Welcome to the community! When you start the installation you’ll be prompted by User Access Control to allow it’s installation. If your firewall is still blocking UE, you can make an exception to allow UE full access (as long as you aren’t running custom versions of the engine).

The ports I do know of though are: Swarm requires ports 8008 and 8009 to function properly.

Thank you for these answers.
As it is not me who performs the permissions but the IT department of the company. I need to provide them with all the necessary information because they won’t investigate.

What are the access protocols? UDP/TCP on ports? https? Do you have the EU server url?

Thanks very much !

I’ve been digging a bit and I found that UE itself uses port 11111 during operation, I’m still trying to find official documentation instead of sniffing the ports out manually. I’m trying to see if I can get a specific document to aid enterprise installations, but in the meantime we have a couple of resources below.

Protocol: UDP 
Foreign Address: *:*               
PID: 39784

Then here’s a list that are associated with the Epic Games Launcher (but also fortnite).

This post has a list of domains that should cover the installation/store side fine, even the UE CDNs are listed.

1 Like

Good morning,

I have some news on my installation attempt.
With our DSI I made a request to open the proxy in Whiliste, then an authorization of url (Epic Games) in order to be able to continue the installation of the Unreal engine.
But I am again blocked when logging into the account (see pj).
Can you help me ?
Thank you so much

Looks like the auth uses a TCP handshake with a different server or through port that wasn’t listed. I’ll have to go back and use the sniffer on it again to see.

Hey there @Ybrault! Sorry about the wait! It looks like there’s a couple more TCP handshakes going on.

TCP - Foreign Address - accessing port: 57523
TCP - Foreign Address - accessing port: 57524
TCP - Foreign Address - accessing port: 57669

I’m no network engineer, but I think these are the last of them. Let me know if those entries help out!

1 Like