5. Setup Troubleshooting (v1.0.3)
If you are having technical issues getting Olympus to work, follow this troubleshooting guide as it will help fix most common issues.
It is important to ensure you've followed all the steps below before asking for help.
99% of the time, your issue will be solved by one of the following. If you are still having issues after reading this guide, please post a detailed description (description, log files, screenshots etc) of your issue in the Community Support section of our Discord.
If your web browser looks like this:
Then you have an extension which is affecting your web pages. You need to either:
a. Use incognito mode; OR
b. Disable extensions
Additionally, some password managers or other apps may present an alert bar across the top of the page which may also cause this issue. Dismiss or close the alert to see if that resolves the problem.
Yes, yes, but the meme has plenty of truth. Try restarting your server, DCS or computer.
- Run the client version for standalone/local
- Run the server version for dedicated servers
Is the DCS part working? When starting a mission you should see a debug notice similar to this:
There are two key places to get information. Examining these may give you a clue as to what might be the issue.
- Your Olympus log file
- Your DCS log file
Which are both located in <DCS Saved Games folder>\Logs
Note that whenever changing ports in olympus.json directly or via the configurator then you must restart DCS and the Olympus server if they're running.
Unless you have an SSL certificate, you will not be running under HTTPS. Ensure you are running under HTTP by manually typing in the whole address (e.g. http://localhost:3000.) Some browsers default to HTTPS and so need to be told to use HTTP.
A firewall rule may be required for inbound TCP ports 3000 (or whatever port you've chosen to use). These rules should be general port rules, not application rules. Note that unlinke older versions of Olympus, from v1.0.4 onward only the frontend port must be forwarded.
Sometimes, other applications are already using the ports and so Olympus cannot use them, and so you need to find one which is not in use. For example, try changing the backend port to a different value using the Manager.
From a command line run the following command line when you believe Olympus is running and see if the ports are open:
netstat -an | findstr 3000
You may need to setup Port Forwarding for port 3000 (or whichever you are using).
-
Open "Windows Defender Firewall"
-
Navigate to "Advanced settings"
-
Go into "Inbound Rules" and create a "New Rule...". Select "Port"
-
Select "TCP" and specify the port that will be used for Olympus.
-
Select "Allow the connection".
-
Select all the options for "Domain", "Private" and "Public".
-
Give it a name and click "Finish".
Now you've added the rules for the ports.
Adobe CC uses Node, which can cause issues with a newer installation of Node. You may be able to run Olympus and Adobe by removing one version of Node. We're yet to get to a full solution on this one, so please stay tuned.
If all failed, ask for help in the Community Support channel of our Discord. To help us understand what might be the issue, be ready with:
- A detailed description of your issue
- Your Olympus log file -
<DCS Saved Games folder>\Logs\Olympus_log.txt - Your DCS log file -
<DCS Saved Games folder>\Logs\dcs.log - Screenshots of the issue if it is useful.
Without these we will struggle to help you. (It also shows you have read this document and tried as much as you could.)