Arma 3 Epoch expects Redis to be running before the Epoch server starts. The reliable setup is to use the Redis files included in the Epoch server package, set a password in DB/redis.conf, then copy the same connection details into the [Redis] section of @EpochHive/EpochServer.ini. A single Redis process can serve several Epoch servers, but every server must have its own InstanceID or their character data can overlap.
Godlike.Host offers hosted Arma 3 servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What Redis does in an Epoch server
Redis is the persistence database used by the Epoch server package. It stores the information that must survive a server restart, including player and character data. Redis is not an optional add-on that can be started later: Epoch installation guidance states that the database must be running for the server to start correctly.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11For a conventional Windows installation, Redis and Arma 3 run on the same machine. In that arrangement, Redis listens on the local address 127.0.0.1, normally on port 6379, and the Epoch server connects to database number 0. Those values are common examples, not requirements. If you deliberately place Redis on another machine, the address, firewall rules, and security model all change.
Before you begin
Files you should have
Obtain and extract the Epoch server package rather than assembling Redis from unrelated downloads. The release contains the database files and the Epoch configuration needed for the server:
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
DB/redis.conf— the Redis configuration file.DB/start-redis.cmd— the package start script.DB/redis-server.exe— the Redis executable.@EpochHive/EpochServer.ini— the Epoch server configuration, including its[Redis]section.
The exact surrounding folders can vary with the release archive, but the database directory and @EpochHive directory should remain in the relative locations expected by the package. Do not move only the executable and leave the configuration behind; Redis must be started with the configuration file that contains your password and persistence settings.
Run with an account that can keep both processes alive
Use a Windows account with permission to read the extracted files, write Redis persistence or log files, and run the Arma 3 server. If the server is hosted under a service account later, that account needs the same file-system permissions. Avoid putting the installation in a location where the service account cannot create or update database files.
Recommended Free Tools
Choose the architecture first
Decide whether Redis will be local or remote before editing the files. A same-machine installation is the simplest and safest starting point: bind Redis to localhost, use the local IP in EpochServer.ini, and expose no database port to the Internet. A remote design can be useful when several game servers share a database host, but it requires deliberate firewall rules, a reachable IP, authentication, and a plan for latency and backups.
Step 1: Extract and inspect the Epoch package
- Extract the complete Epoch server release to the directory from which you will run Arma 3.
- Confirm that the extracted directory contains
DBand@EpochHive. - Inside
DB, confirm thatredis.conf,start-redis.cmd, andredis-server.exeare present. - Inside
@EpochHive, openEpochServer.iniand locate the[Redis]section before starting either program.
If one of these files is missing, stop and re-extract the archive. Starting with a partial package commonly produces a Redis process that cannot find its configuration or an Epoch server that has no matching database settings.
Step 2: Configure Redis in redis.conf
Keep a local installation bound to localhost
Open DB/redis.conf in a plain-text editor. For a Redis process on the same computer as Arma 3, keep the bind address restricted to localhost unless you have a specific reason to accept remote connections. The documented local example is 127.0.0.1. A localhost-only listener reduces the number of systems that can reach the database and avoids exposing Redis directly to the public network.
If Redis is intentionally remote, use the server address that the Arma host can reach and restrict the Redis port at the firewall to the required source addresses. Do not treat changing the bind address as a complete remote-security plan: the network path, Windows firewall, upstream firewall, authentication, and administrative access all need to be considered together.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Set a strong password
Set the requirepass value in redis.conf to a strong, unique password. Do not reuse the Arma administrator password, the BattlEye password, or a Windows account password. The value is case-sensitive and must be copied exactly into EpochServer.ini.
Redis authentication is a two-file configuration. Changing only one file will leave the server unable to authenticate. Keep the password free of accidental leading or trailing spaces, and make sure your editor does not replace or remove the configuration line.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Preserve the package’s persistence directives
The community installation guidance places Redis persistence directives in this file. Leave the supplied persistence configuration intact unless you understand the operational consequence of changing it. Persistence is what allows stored character data to survive a Redis or Arma process restart; disabling or misdirecting it can make a server appear to work while putting saved data at risk.
Save the file in plain text
Save redis.conf without a rich-text format or an added filename extension such as .txt. If Windows hides known extensions, verify that the file is still named exactly redis.conf. Keep a private copy of the password and record any intentional changes so a later service migration reproduces the same settings.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Step 3: Start Redis from the correct directory
Redis must be started with redis.conf. The package provides two equivalent approaches:
- Open a command window in the
DBdirectory and runstart-redis.cmd. - From that same directory, run
redis-server.exe redis.conf.
Starting from DB matters because relative paths in the package configuration and start script are expected to resolve from that directory. If you double-click an executable from another working directory, the window may close immediately or Redis may not use the configuration you edited.
What a successful start looks like
Leave the Redis console open during initial setup and inspect its output for errors. It should remain running instead of closing immediately. The process must be accepting connections before you launch Arma 3. If Redis reports a configuration, port, permission, or persistence error, fix that error first; an Epoch server cannot compensate for a database that failed to start.
Do not start multiple Redis processes on the same port unless you have intentionally assigned separate ports and configuration files. For the standard package layout, one Redis process is enough for the box.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteStep 4: Point Epoch at Redis
Open @EpochHive/EpochServer.ini and edit the [Redis] section. The four values must describe the Redis process that is actually running:
| Setting | What it controls | Typical same-machine example | Qualification |
|---|---|---|---|
IP |
The address where Redis listens | 127.0.0.1 |
Use the reachable Redis host address for a remote design. |
Port |
The TCP port Redis accepts | 6379 |
This is a common default, not a universal requirement. |
DB |
The Redis logical database selected by Epoch | 0 |
It must match the database arrangement you chose. |
Password |
The Redis authentication secret | Your requirepass value |
Match redis.conf character for character. |
A local configuration therefore resembles the following pattern. Replace the password with your own value and keep the option names and syntax used by your Epoch release:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
[Redis]
IP = 127.0.0.1
Port = 6379
DB = 0
Password = replace-with-your-redis-passwordThe example is illustrative rather than a promise that every Epoch build uses identical spacing. Preserve the syntax already present in your file and change the values, not the section name.
Check both sides before launching
- The IP in EpochServer.ini is the address configured for Redis.
- The port in EpochServer.ini is the port on which Redis is listening.
- The selected DB value is intentional and consistent across the servers that should share that logical database.
- The password is identical to
requirepass, including capitalization and punctuation.
Step 5: Separate multiple Epoch servers with InstanceID
One Redis instance can serve more than one Epoch server. Epoch’s official installation notes describe the operational rule clearly: only one Redis instance is needed per box, but servers connecting to the same Redis share character data by default. The setting that prevents an accidental collision is a unique InstanceID in the [EpochServer] section of each server’s EpochServer.ini.
Example layout
| Server | Redis process | Redis DB | InstanceID |
Result |
|---|---|---|---|---|
| Altis Epoch | Same process | 0 |
1 |
Uses the Altis data namespace. |
| Bornholm Epoch | Same process | 0 |
2 |
Uses a separate Epoch namespace. |
| Test server | Same process | 0 |
3 |
Isolated from the two live servers by its identifier. |
The numbers in this example are arbitrary identifiers; the important condition is uniqueness among servers sharing the Redis service. If you instead run separate Redis processes, assign each process its own port and configuration, then point each Epoch server to the matching process. Separate processes can provide stronger operational isolation but require more memory, ports, service definitions, and backup handling.
When a shared Redis instance is appropriate
- Several Epoch servers run on one box and you want one database service to supervise.
- You can maintain a clear inventory of each server’s
InstanceID. - You understand that a Redis outage affects every server using that process.
Use separate Redis processes or hosts when you need independent restart schedules, maintenance windows, resource limits, or failure domains. The package guidance establishes that sharing is supported; it does not remove the need to design backups and recovery for all servers together.
Step 6: Finish the surrounding Arma 3 configuration
Redis is only one part of an Epoch deployment. Before launching, configure the remaining server files supplied by the package:
- Set the BattlEye path and password used by your server.
- Complete
server.cfg, including the server identity and administrator settings. - Review logging and signature-verification options.
- Set the required-build value appropriate for the Arma 3 version you intend to run.
The official template includes server identity, administrator passwords, logging, signature verification, BattlEye, and required-build fields. Keep those credentials distinct from the Redis password. A BattlEye authentication failure and a Redis authentication failure are separate problems even though both may appear during startup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Step 7: Launch in the right order
- Start Redis from
DBwithstart-redis.cmdorredis-server.exe redis.conf. - Confirm that the Redis process remains open and has not reported a fatal configuration or port error.
- Start the Arma 3 Epoch server.
- Watch the Arma console and log for a successful Redis connection before testing a player login or character save.
- Stop both programs cleanly when changing configuration, then restart Redis before Arma after each change.
Redis must be available before Epoch starts. Starting Arma first can produce connection errors even when the files are correct, because the database endpoint did not yet exist when Epoch attempted to connect.
Making the setup survive reboots
Why a service restarter helps
A manually opened Redis console stops when the session closes, the machine reboots, or the process crashes. Epoch’s official notes recommend using a service restarter to keep Redis and the Arma 3 server running. A service manager can launch both programs unattended, restart a failed process, and start Redis before Arma.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Define the dependency order
Configure the service manager so the Redis service starts first and the Arma service starts only after Redis is available. If both services launch simultaneously, Arma can win the race and fail its initial connection. A restart policy for Arma should not repeatedly launch it while Redis is still down; correct ordering is more reliable than rapid blind retries.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use a controlled restart schedule
The official installation notes recommend restarting the Arma 3 server every four hours. Treat that as an operational recommendation, not a measured performance guarantee. If you adopt the schedule, warn players, allow the server to shut down cleanly, and restart Redis only when your persistence and backup procedure supports it. A routine Arma restart does not justify deleting Redis data or rebuilding the database.
Service-account checks
- Grant the service account read access to the Epoch and Redis binaries and write access to Redis data and log locations.
- Use absolute paths in the service definition when possible so the working directory is not ambiguous.
- Record the exact command, including
redis.conf, that starts Redis. - Test a full reboot and confirm Redis is listening before the Arma process begins.
Security and network decisions
Localhost is the default for a single box
When Redis and Arma share a machine, binding Redis to 127.0.0.1 keeps the database off the external network. You still need a strong password because local processes and administrators may access the machine, but you avoid exposing the Redis port to every host that can reach the server.
Remote Redis requires more than an IP change
If Redis runs on a different host, set the Epoch IP to the address reachable from the Arma machine, open only the required port between those hosts, and restrict inbound sources with a firewall. Verify that the selected port is not blocked or already used. Never expose a password-protected Redis endpoint broadly to the public Internet as a substitute for network controls.
Keep credentials separate
Store the Redis password, Arma administrator password, and BattlEye password as different secrets. Limit access to redis.conf and EpochServer.ini, because both contain connection credentials. When changing the Redis password, plan a coordinated edit and restart rather than changing one file while the server is live.
Troubleshooting Redis and Epoch connection failures
Redis window closes immediately
- Open a command prompt directly in the
DBdirectory. - Run
redis-server.exe redis.confso the error remains visible. - Confirm that
redis.confexists in that directory and was not renamed with a hidden.txtextension. - Inspect the console or configured log for a port, permission, or persistence error.
Launching the executable without passing the configuration can make Redis ignore the password and persistence settings you intended to use. Correct the command or the package start script before trying Epoch again.
Authentication failure
Compare requirepass in DB/redis.conf with Password under [Redis] in EpochServer.ini character by character. Check capitalization, punctuation, spaces, and which copy of EpochServer.ini the running server actually loads. Restart Redis after editing redis.conf, then restart Arma so both processes use the new value.
Connection refused
- Verify that Redis is still running and did not exit after launch.
- Check that Epoch’s
IPmatches the Redis bind address. - Check that both files use the same port.
- For a same-machine setup, test the documented local address
127.0.0.1rather than a public or unrelated network address. - For a remote setup, inspect Windows and upstream firewall rules and confirm the host is reachable from the Arma machine.
The server starts but players or characters appear to collide
When several Epoch servers use one Redis process, inspect the InstanceID in each server’s [EpochServer] section. Every server sharing that process must have a distinct identifier. Changing the Redis port or DB number alone does not correct an accidental duplicate identifier in an otherwise shared setup.
It works manually but fails after a reboot
Check the service manager’s working directory and command line first. Redis should be launched from its DB directory with redis.conf, and its service must start before Arma. Then verify that the service account can read the configuration and write persistence files. A manual test run under an administrator account can succeed even when the unattended service lacks those permissions.
Only one of several servers fails
Compare that server’s complete [Redis] section and InstanceID with a working server. A shared Redis outage would normally affect every dependent server; a single failure more often points to a typo, a different configuration file, an invalid service path, or a duplicate identity. Correct the affected server without changing the shared Redis process until you have ruled out those local differences.
Changing the Redis password safely
- Choose a new unique password and record it in a secure password manager.
- Stop the Arma 3 server cleanly so it will not continue making failed authentication attempts.
- Stop Redis and edit
requirepassinDB/redis.conf. - Save the file, then start Redis again with the package command.
- Update
Passwordin every affected server’s[Redis]section. - Start each Arma server only after Redis is accepting connections.
- Check the logs and test a character save before returning the server to players.
All Epoch servers that use that Redis process must be updated during the same maintenance window. Leaving one server with the old password produces an authentication error for that server while the others continue to work, which can make the change look inconsistent.
Local Redis versus a separate Redis host
| Decision area | Redis on the Arma host | Redis on another host |
|---|---|---|
| Configuration control | Direct control of the packaged configuration and local files. | Control is split across the Redis host, network, and Arma host. |
| Firewall exposure | Can remain bound to localhost with no external database port. | Requires narrowly scoped firewall rules and a reachable address. |
| Latency | Local process communication avoids network distance. | Depends on the network path and geographic placement. |
| Failure scope | A host failure affects both Redis and Arma. | Separate hosts can provide a different failure boundary, but the network becomes another dependency. |
| Operations | One machine to patch, back up, and restart. | Redis updates, backups, monitoring, and firewall administration are separate responsibilities. |
| Multiple Epoch servers | One Redis process can serve several servers with unique InstanceID values. |
Can centralize several Arma hosts, provided authentication, latency, and isolation are acceptable. |
| Cost | No separate Redis host is required; hardware and administration remain your responsibility. | May require another machine or a managed service; current provider pricing is not established here. |
For a first server, local Redis is usually the least complicated architecture. Move Redis elsewhere only when the operational benefit outweighs the additional network and security work.
Final pre-launch checklist
- The complete Epoch package is extracted, including
DBand@EpochHive. redis.confhas the intended bind address, a strongrequirepass, and the supplied persistence directives.- Redis is started from the
DBdirectory withredis.conf. - Redis remains running and is available before Arma launches.
IP,Port, andDBin EpochServer.ini identify the running Redis instance.- The Epoch password matches Redis’s
requirepassexactly. - Every server sharing a Redis process has a unique
InstanceID. - BattlEye,
server.cfg, logging, signature verification, identity, administrator credentials, and required-build settings are complete. - A service manager or restarter starts Redis before Arma and has permission to read and write the required files.
- You have tested startup after a reboot and know where Redis and Arma logs are stored.
Frequently Asked Questions
Can I use one Redis instance for multiple Epoch servers?
Yes. Keep one Redis process if desired, but assign a different InstanceID in each server’s [EpochServer] section so their character data remains separated.
Where do I change the Redis password?
Change requirepass in DB/redis.conf and change Password in every affected [Redis] section of EpochServer.ini. Restart Redis before restarting Epoch.
What should I do if Epoch says Redis connection refused?
Confirm Redis is running with the intended configuration, then compare the Epoch IP and Port with Redis’s bind address and listening port. Remote installations also require matching firewall rules.
Does Redis have to start before Arma 3?
Yes. Epoch expects the Redis database to be available during startup; configure any service manager to launch Redis first.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
