- Importing an Existing Config
- Using Beacon with Ark Single Player
- Updating Your Nitrado Server
- Updating Your Server With FTP
- Updating Your Server Manually
- Ark Config File Reference
- The Difference Between Deploy and Export
- Using Config Sets
- Using Presets to Automate Item Set Creation
- Adding Unsupported Engrams, Creatures, or Spawn Points to Beacon
- Preset Selectors Guide
- Breeding Multipliers
- Crafting Costs
- Creature Adjustments
- Creature Spawns
- Custom Config
- Day and Night Cycle
- Decay and Spoil
- Engram Control
- Harvest Rates
- Item Stat Limits
- Levels and XP
- Loot Drops
- Stack Sizes
- Stat Multipliers
- Create or Recover Your Account
- Sign Into Beacon
- Activating Beacon Omni
- Sharing Beacon Documents with Other Users
- About User Privacy
- Item Quality Is Different Than Expected
- Loot Drops Are Not Working As Intended
- How to Stop Using the Custom Config Editor
- Solving Connection Problems to Beacon or Nitrado
- Beacon System Status
Solving Connection Problems to Beacon or Nitrado
Connection problems can present themselves as "unable to download user details" errors at login or "failed to establish secure connection" errors while importing from Nitrado.
First, try Windows Update
Both Beacon and Nitrado's servers require TLS 1.2 at the time of this writing. In some versions of Windows, these security protocols are disabled by default. Windows Update KB3140245 enables support for these protocols. Follow the instructions in the linked article to either run Windows Update or install the update directly. If installing the update manually, make sure to choose the version appropriate for your computer. Most users are running a 64-bit version of Windows, so should choose an option for x64-based systems.
Even though the linked support article is specific to Windows 7, try Windows Update anyway. The KB3140245 update will not apply to Windows 8 systems, but Windows Update often fixes the issue anyway.
If that doesn't solve the problem
Some Antivirus software can be particularly aggressive and block Beacon's connection to servers outside the user's country. Check your antivirus software for notices. Try whitelisting Beacon so your antivirus software will not interfere. For instructions, do a web search for "whitelist name of your antivirus" and it will hopefully be the top result.
Try installing for all users
Admin permission is required to install for all users, and that admin permission will allow Beacon's installer to run more tasks. In this mode, the installer will attempt to install the KB3140245 update, change the registry keys required to enable TLS 1.2 support, and install the Visual C++ runtime. If the previous steps didn't help, reinstalling for all users might solve the problem.
First uninstall Beacon. Your data will be safe. Then run the installer again. When asked wether to install for just you or all users, make sure to choose all users. If Beacon is already installed, the installer will not ask about installing for all users, so it is important to uninstall Beacon first.
As of September 30th 2021, Beacon's online features can no longer function on macOS 10.11 El Capitan. Apple no longer issues security updates for the system, so when Let's Encrypt's root certificate expired, any application that relies on the system's built-in networking (like Beacon and Safari) can no longer connect to servers secured by Let's Encrypt.
Unfortunately this means options are extremely limited. The best option is to update macOS, which also supports Beacon 1.5 and all of its new features. If updating macOS is not an option, see the instructions under "Method 2: Use an activation file for a computer without internet" of https://usebeacon.app/account/#omni. Online services still won't work, but you will have access to your Omni license at least.