Vrex Network Requirements: How to Allow-List Vrex in Bitdefender
Vrex is a secure, cloud-based application using AWS and Google Speech-to-Text. Sometimes, Bitdefender (antivirus/firewall/security software) may block parts of Vrex, causing features to stop working. This guide shows you, or your IT administrator, exactly how to configure Bitdefender to ensure Vrex runs smoothly.
🛡️Why Is This Important?
- Bitdefender sometimes blocks trusted cloud apps by mistake.
- Blocked connections or files will prevent Vrex from logging in, updating, synchronizing, or running meetings.
- Proper allow-listing (exclusion) guarantees Vrex works reliably.
Step 1: Add Vrex Domains to Bitdefender Web Exclusions
NOTE: Vrex is not associated with Bitdefender, and our instructions may be outdated. Consider this a general guide for what actions to take. Please refer to the Bitdefender documentation for the latest detailed documentation.
Open Bitdefender GravityZone or your Bitdefender central management console.
Navigate to Policies ➡️ Antimalware ➡️ Traffic Scan or Network Protection ➡️ Exclusions/Exceptions.
Add the following domains and subdomains to the list of exclusions:
app.vrex.no api.vrex.no eu1.com.vrex.vixel.no speech.googleapis.com cognito-idp.eu-central-1.amazonaws.com 2uhv8tme94.execute-api.eu-central-1.amazonaws.com 5n4hoaxzr1.execute-api.eu-central-1.amazonaws.com 8uslevf82e.execute-api.eu-central-1.amazonaws.com szpdew7g70.execute-api.eu-central-1.amazonaws.com qcymfi5l22.execute-api.eu-central-1.amazonaws.com uvn1nqbtvh.execute-api.eu-central-1.amazonaws.com vrex-projects-production.s3.eu-central-1.amazonaws.com vrex-projects-release.s3.eu-central-1.amazonaws.com
Tip: If possible, use *.vrex.no as a wildcard to cover future Vrex domains.
Step 2: Allow Required Ports in Bitdefender Firewall
- Go to Policies ➡️ Firewall ➡️ Rules (or “Network Attack Defense” in some versions).
- Add rules to allow:
- All TCP port 443 (HTTPS) traffic to the above domains.
- UDP ports 5055 and 5056 to
eu1.com.vrex.vixel.no(IP:18.194.34.130).- This is required for Vrex’s real-time audio and sync features.
Step 3: Exclude Vrex from SSL/HTTPS Scanning
- In your Bitdefender policy, locate Network Protection ➡️ SSL Scanning (sometimes under “Content Control”).
- Add all the Vrex domains/subdomains above, plus
speech.googleapis.com, to the SSL/HTTPS scan exceptions.
Why? Bitdefender’s HTTPS scanning can block secure app connections, causing login or feature failures.
Step 4: Exclude Vrex Software Files from Bitdefender Scanning
Bitdefender’s behavioral and advanced threat protections can block or quarantine Vrex during installation, updates, or usage. You must allow-list these exact files to ensure reliable operation:
Go to Policies ➡️ Antimalware➡️ Settings ➡️ Exclusions or Advanced Threat Control/Behavioral Scanning ➡️ Exclusions.
Add these two file paths to your exclusions list:
%localappdata%\Programs\VrexLauncher2.0\VrexLauncher.exe %localappdata%\Programs\VrexLauncher2.0\Vrex\Vrex.exe
%localappdata%resolves toC:\Users\[username]\AppData\Localon each PC.- Apply to all users/workstations that use Vrex.
If this step is missed, Vrex may not start, update, or function correctly.
✅Step 5: Apply and Save Your Policy Changes
- Ensure all settings are saved and applied to every computer that will run Vrex.
- If needed, push a policy update or restart computers to activate the new settings.
📶How to Test
- Open Vrex and test: login, meetings, audio, sync, and speech-to-text.
- If problems persist, check Bitdefender’s logs for blocked connections or files.
- Confirm that all the domains, ports, and file paths above are correctly allowed.
- Contact your IT administrator or Vrex support if issues remain.
🧾Quick Reference Table
| Type | Destination or Path | Port(s) | Purpose |
|---|---|---|---|
| HTTPS | All Vrex domains (above) | TCP 443 | Admin, authentication, app data |
| UDP | eu1.com.vrex.vixel.no (18.194.34.130) | UDP 5055/5056 | Audio & real-time sync |
| HTTPS | speech.googleapis.com | TCP 443 | Speech-to-text (Google) |
| Local File | %localappdata%\Programs\VrexLauncher2.0\VrexLauncher.exe | - | Vrex Launcher |
| Local File | %localappdata%\Programs\VrexLauncher2.0\Vrex\Vrex.exe | - | Main Vrex Application |
❓Frequently Asked Questions
Do I need to repeat this for every user? Yes, if exclusions are set per user. For company-wide policies, set them for all users’ AppData folders.
Will this make my network less secure? No. The exclusions are strictly limited to Vrex and Google speech services, which are secure and necessary for the app to function.
What happens if we skip any step? Vrex may fail to start, update, synchronize, or provide meetings/audio. Are you sure I cannot even skip Google Speech? This can be skipped, but it will block users from using their voice to type. Instead, they must use a keyboard, which can be time-consuming in VR.
Need help? Contact your IT administrator or Vrex Support for assistance.