Run Your Own Amateur Radio Logbook with Wavelog
Amateur radio operators often maintain detailed records of the contacts they make, including callsigns, frequencies, operating modes, locations and dates. Keeping these records accessible from different computers and locations can become difficult, particularly when using software installed on a single home computer.
Wavelog is an open-source, self-hosted amateur radio logging application that lets you manage your radio contacts through a web browser. This guide explains how to run Wavelog on a Linux VPS, what equipment and knowledge you need, and why a small virtual server might be useful for an individual operator or radio club.
2 GB VPS plans to consider for Wavelog
- 2 GB KVM VPS Special2 CPU · 2 GB RAM · 35 GB disk · 5 TB bandwidth · New York, Los Angeles, Dallas$35.99/yrabout $3.00/moView at RackNerd
- Ryzen-2GB (Linux)2 CPU · 2 GB RAM · 20 GB disk · 2 TB bandwidth · New York, Chicago, Seattle$222.37/yrabout $18.53/moView at RackNerd
- KVM-2GB3 CPU · 2 GB RAM · 75 GB disk · 2 TB bandwidth · Los Angeles, Dallas, New York$247.08/yrabout $20.59/moView at RackNerd
In stock when this page loaded. See every plan
What is in this guide
- What is Wavelog?
- Why use a VPS for your logbook?
- What you need before starting
- Choosing a suitable VPS
- Installing and accessing Wavelog
- Security and backups
- Limits
- When to step up
What is Wavelog?
Wavelog is a web-based amateur radio logging application. It provides a central place to record and manage your radio contacts, commonly called QSOs. A QSO is simply a completed contact between two amateur radio stations.
Rather than keeping your logbook tied to one computer, Wavelog runs on a web server. You access it through a browser, using an internet connection. This means you can work with the same logbook from different computers and locations without needing to copy database files between devices.
Wavelog includes features for managing contacts, viewing maps of worked locations and entities, checking awards, managing QSL information and analysing your logging activity. It also supports multiple users, making it relevant to clubs and shared station operations.
The software is open source and can be installed on infrastructure that you control. You are responsible for maintaining the server, keeping the software updated and protecting the information stored in your logbook.
Wavelog is not a radio transceiver control system or a replacement for every piece of software used in an amateur radio shack. Its main purpose is managing your contact records. Additional integrations may be available for operators who want to connect other equipment or applications.
Why use a VPS for your logbook?
Wavelog can run on different types of computers and servers. A VPS is one option for operators who want their logbook accessible over the internet without leaving a computer running at home.
A VPS, or virtual private server, is a virtual computer hosted in a data centre. You rent its allocated resources and have administrative access to install compatible software. It behaves much like a small Linux computer that remains connected to the internet.
There are several reasons an amateur radio operator might choose this arrangement.
- Access from different locations. Open your logbook from a browser at home, while travelling or from another computer with internet access.
- No home computer required to stay running. The VPS operates independently of your personal desktop or laptop.
- Shared club logging. A radio club can investigate using a central installation where multiple authorised operators work with shared station records.
- Centralised records. Keep your logging application and database together rather than relying on separate copies on several computers.
- Control over your installation. You manage the server, application configuration and access arrangements instead of relying entirely on a third-party hosted logbook service.
A VPS is not the only option. You can also install Wavelog on a suitable computer or a small computer at your radio station. Home hosting may be preferable when you want the application available only on your local network or need direct access to equipment on the same network.
The main advantage of a VPS is having a remotely accessible server that does not depend on your home internet connection or home computer being switched on.
What you need before starting
Running Wavelog on a VPS is more involved than registering for an online account. You are installing and maintaining an application on a Linux server, so some basic technical knowledge is useful.
Before ordering a server, consider the following requirements.
| Requirement | What it means |
|---|---|
| Amateur radio log data | Existing contact records that you want to maintain or import, if applicable. |
| Wavelog | The logging application you intend to install. |
| Linux VPS | A virtual server with sufficient memory, processor resources and storage. |
| Docker and Docker Compose | Tools that allow applications and their supporting services to run in containers. |
| Internet connection | Required to access the application remotely. |
| Domain name | Optional, but useful when configuring a permanent address for your logbook. |
| Basic administration knowledge | An understanding of server access, passwords, updates and backups. |
The Wavelog documentation recommends Docker as an installation approach. Docker packages applications into containers, making it easier to manage the application and its supporting database as separate services.
You should also be comfortable connecting to your VPS using SSH. SSH is a secure method of accessing a remote Linux command line. If you have not used it before, start with your first hour on a new RackNerd VPS and learn about setting up SSH keys.
Choosing a suitable VPS
The resources required by Wavelog depend on how it is being used. An individual operator with a modest logbook has different requirements from a busy club station with several users and a large contact database.
Memory is particularly important because your server must run the operating system, Wavelog, its database and any additional services needed for your installation. Docker also uses system resources, so you should allow room for the operating system and background processes.
For an initial comparison, looking at VPS plans with 2 GB of RAM is a reasonable starting point for a small installation. This is not a guarantee that every configuration will perform adequately. Your actual requirements depend on the number of users, database size and other applications running on the server.
| Server resource | What to consider |
|---|---|
| RAM | Allow memory for Linux, Docker, Wavelog and the database. |
| CPU | More users and background activity can increase processor requirements. |
| Storage | Allow space for the operating system, application, database, uploads and future growth. |
| Bandwidth | Consider how many people will access the logbook and how frequently they use it. |
| Operating system | Choose a supported 64-bit Linux distribution that is compatible with your installation method. |
When comparing plans, avoid choosing entirely on price. A small saving is not worthwhile if the server does not have enough resources to run the application reliably.
The guide to understanding VPS specifications explains how to compare memory, CPU, storage and bandwidth before choosing a plan.
Compare 2 GB VPS plans
- 2 GB KVM VPS Special2 CPU · 2 GB RAM · 35 GB disk · 5 TB bandwidth · New York, Los Angeles, Dallas$35.99/yrabout $3.00/moView at RackNerd
- Ryzen-2GB (Linux)2 CPU · 2 GB RAM · 20 GB disk · 2 TB bandwidth · New York, Chicago, Seattle$222.37/yrabout $18.53/moView at RackNerd
- KVM-2GB3 CPU · 2 GB RAM · 75 GB disk · 2 TB bandwidth · Los Angeles, Dallas, New York$247.08/yrabout $20.59/moView at RackNerd
In stock when this page loaded. See every plan
Installing and accessing Wavelog
Once you have a suitable VPS, the next step is installing the application. Wavelog provides its own documentation covering the installation process, including a Docker Compose method.
Docker Compose allows several related containers to be configured and started together. A typical Wavelog installation uses one container for the web application and another for its MariaDB database.
MariaDB is a database system that stores the information used by Wavelog, including your contact records and application settings.
The general installation process involves the following stages.
- Prepare your VPS. Install a supported Linux operating system, update the system packages and configure secure remote administration.
- Install Docker. Install Docker Engine and Docker Compose using the appropriate instructions for your Linux distribution.
- Prepare the Wavelog configuration. Follow the official Wavelog Docker documentation to create the required configuration and Compose file. Set a strong database password before starting the containers.
- Start the application. Use Docker Compose to start the Wavelog and database containers. Check that both services are running correctly.
- Complete the installer. Open the Wavelog installation page in your browser and follow the setup instructions. You will need to provide the correct database connection details.
- Configure access. Once installation is complete, configure a permanent address and secure access to your logbook.
Wavelog can initially be accessed using the server address and the port configured in its Docker setup. For a more convenient arrangement, you can configure a domain name and a reverse proxy.
A reverse proxy accepts incoming web requests and forwards them to the application running on the server. It can also be configured to provide HTTPS, which encrypts the connection between your browser and the logbook.
Follow the current Wavelog installation documentation carefully. Configuration details can change between software releases, so do not assume an older tutorial will match the version you are installing.
Security and backups
Your amateur radio logbook may contain years of contact history and information that you do not want to lose. Because a VPS can be accessed over the internet, security and backup arrangements should be part of the initial setup rather than something added later.
- Use strong passwords. Protect your Wavelog accounts, database and server administration access with unique passwords.
- Secure SSH. Use SSH keys where possible and avoid unnecessarily exposing administrative services to the internet.
- Configure HTTPS. Use an appropriately configured certificate so browser connections to your logbook are encrypted.
- Keep software updated. Apply appropriate updates to Linux, Docker and Wavelog. Check release information before making application changes.
- Limit account access. Only give other operators the permissions they need, particularly when operating a shared club installation.
- Back up your information. Maintain copies of the database and relevant application files outside the VPS.
Do not assume that a hosting provider's server backups replace your own application backups. You should have a separate recovery plan and periodically check that your backup files can actually be restored.
Wavelog is a logbook application, not a dedicated backup service for your radio records. If you want to keep another copy of your information separately from the main server, see using a storage VPS for backups.
Before making significant upgrades or configuration changes, create a fresh backup. A working backup is particularly important when your logbook contains years of accumulated contacts.
Limits
A VPS can be a useful way to host Wavelog, but it is not suitable for every amateur radio installation.
- Technical knowledge is required. Installing and maintaining Wavelog involves Linux administration, Docker, databases and web server configuration.
- Hardware requirements vary. There is no single VPS configuration that is guaranteed to suit every logbook, club or operating environment.
- Internet access is necessary. A remotely hosted logbook will not be available through the internet when your connection is unavailable.
- Local radio equipment is separate. Hosting Wavelog remotely does not automatically provide a connection to radios and equipment located at your home or club station.
- You remain responsible for your data. Incorrect configuration, software problems or missing backups can result in lost information.
Think carefully about whether you need a remotely accessible logbook. An installation on a computer at your radio station may be more appropriate if you only need local access or require close integration with equipment on your own network.
Also remember that RackNerd VPS plans, configurations, operating system options and ordering terms can change. Check the current order page before making a decision.
When to step up
A small VPS may be adequate for an individual operator with a relatively modest logbook. However, consider moving to a larger configuration if you are adding multiple users, maintaining a club logbook, storing a growing database or running additional services alongside Wavelog.
More memory and CPU resources can provide additional room for the application, database and operating system. Storage requirements may also increase as your contact records and uploaded files grow.
Before upgrading, check actual resource usage and investigate whether the application has been configured correctly. A larger server is not always the answer to a software configuration or database problem.
4 GB VPS plans for larger Wavelog installations
- 4 GB KVM VPS Special3 CPU · 4 GB RAM · 60 GB disk · 7 TB bandwidth · New York, Los Angeles, Dallas$59.99/yrabout $5.00/moView at RackNerd
- Ryzen-4GB (Linux)2 CPU · 4 GB RAM · 30 GB disk · 3 TB bandwidth · New York, Chicago, Seattle$265.57/yrabout $22.13/moView at RackNerd
- KVM-4GB4 CPU · 4 GB RAM · 130 GB disk · 3 TB bandwidth · Los Angeles, Dallas, New York$295.08/yrabout $24.59/moView at RackNerd
In stock when this page loaded. See every plan
Running Wavelog on your own VPS gives you control over an online amateur radio logbook that you can access from different locations. Start with a configuration suited to your expected workload, take backups seriously and expand as your installation grows. To compare what is available now, start with the cheapest RackNerd VPS guide and check the sales page.