EMQX Configuration Changes Not Applied

DodaTech Updated 2026-06-26 1 min read

In this tutorial, you'll learn about EMQX Configuration Changes Not Applied. We cover key concepts, practical examples, and best practices.

The Problem

Changes to emqx.conf do not take effect after broker restart.

Quick Fix

Wrong

sudo nano /etc/emqx/emqx.conf  # Edit config

Changes lost after restart or overwritten by environment variables.

Right

# 1. Edit the config file
sudo nano /etc/emqx/emqx.conf
# 2. Verify syntax
emqx check-conf
# 3. Restart with config reload
sudo systemctl restart emqx
# Or use environment variables (Docker)
docker run -e EMQX_LISTENERS__DEFAULT__TCP__PORT=1883 emqx/emqx:latest

Config changes active after restart. Check with emqx_ctl conf get key.

Prevention

EMQX applies config from /etc/emqx/emqx.conf. Some settings require a full restart. Environment variables override file config (prefix EMQX_, use __ for dots). Use Docker env vars for container deployments. Verify with: emqx_ctl conf show listeners.

DodaTech engineers apply these same patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro for production IoT reliability.

FAQ

### Where is EMQX config file?

Linux: /etc/emqx/emqx.conf. Docker: bind mount or env vars. The file uses HOCON syntax (JSON-like).

What config format does EMQX use?

HOCON (Human-Optimized Config Object Notation). Keys use dot notation: listeners.tcp.default.port = 1883.

How do I hot-reload config?

Some settings can be changed via Dashboard or API (http://localhost:18083/api/v5). For most changes, a restart is required.

← Previous EMQX Cluster Nodes Not Connecting Next → How to Fix MQTT Broker Connection Issues

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro

Home Browse Quick Fix