Meraki MX68 — login, gateway address and status lights

Name: Meraki MX68
Brand: Cisco Meraki

Open a browser on a device connected to your Meraki MX68 and go to 192.168.128.1, or setup.meraki.com.

The password is unique to your unit and printed on it — there is no universal default.

The Meraki MX68 is a firewall router from Cisco Meraki, in UK use 2018-present. This page covers the four things people actually come looking for: its settings address, how its login works, what its lights mean and how to reset it safely.

What is the Meraki MX68 gateway address?

The Meraki MX68 settings page is at 192.168.128.1. Type that into the address bar of a browser — not into a search box, which will just search for the number instead of opening the page.

You can also use setup.meraki.com, which reaches the same page and is easier to remember.

Your device has to be connected to the Meraki MX68 itself for this to work — over its Wi-Fi or by cable. On mobile data, or connected to a different network, the address goes nowhere.

True only of a factory-default appliance that has never reached the Meraki dashboard. The MX68 starts in single-LAN mode on 192.168.128.0/24 with itself on 192.168.128.1, and replaces that with whatever the dashboard holds as soon as it checks in — so Meraki's own instruction is to connect a client to a LAN port and open that client's default gateway rather than to trust a published number. The four hostnames only resolve when your DNS queries pass through the appliance. The MX68 was named alongside the MX67 in the first MX 19.1 TLS wave, so on current firmware an HTTP request redirects to a MAC-derived hostname at devices.meraki.direct, with https://<appliance LAN IP>:8092 as the documented fallback.

What is the default username and password for the Meraki MX68?

Unique password on the device label

There is no default password for the Meraki MX68 that we could publish, because every unit has a different one.

Where to find yours. On the product label on the bottom panel — Meraki's note covers the MX67 and MX68 together.

The credentials that exist are per-unit and firmware-dependent, so there is no shared secret anyone could publish. On MX 19 firmware and later — which is where every supported MX67 and MX68 now is — the local status page takes the username admin with the appliance's own serial number as the password, in upper case with the dashes, in the form Qxxx-xxxx-xxxx. On older firmware it was the serial number as the username with no password at all. You may find Meraki's own installation guide still describing that older behaviour; the local status page documentation is the current one, and these two models were in the first wave moved to the MX 19.1 behaviour, so the installation guide's instruction would fail on a current unit. There is a third case to know about: on networks created after 1 August 2025 a password has to be set explicitly, and if an administrator never sets one then an auto-generated password is pushed to the appliance, making the local status page unreachable until somebody sets one — and Meraki is clear that neither the network administrator nor Meraki support can read that generated password. Full administration happens in the Meraki dashboard with a completely separate cloud account.

If a website offers you a single password that works on every Meraki MX68, it is wrong. Those lists copy a per-device password from one unit and republish it as though it were universal.

What do the lights on the Meraki MX68 mean?

Here is what each light on the Meraki MX68 is telling you, and what to do about it.

Light	What it means	What to do
Statussolid white	Fully operational and connected to the dashboard, using the wired WAN uplink.
Statussolid purple	Fully operational and connected, but running on the integrated cellular failover rather than the wired WAN.	The appliance is up but your fixed line is not carrying traffic. Check the WAN before the cellular allowance runs down.
Statussolid orange	Power is applied but the appliance has not connected to the Meraki dashboard.	This is the light you will see on a unit that has not been claimed into an organisation, or one whose internet path is broken. Until it reaches the cloud it will not take its configuration.
Statuscycling through colours	Cycling through colours — the appliance is trying to reach the Meraki dashboard.	Give it a couple of minutes. If it settles on orange rather than white, the uplink is the problem.
Statusflashing white	A firmware upgrade is in progress.	Do not remove power.
Portsolid green	The port has a link in both directions.
Portflashing green	Traffic is passing on that port.

How do you reset a Meraki MX68?

What you lose. Cloud management inverts the usual expectation here, and this is the most useful thing to understand about the appliance. A factory reset clears the locally cached configuration and returns the unit to single-LAN mode on 192.168.128.1. It does not destroy your firewall rules, AutoVPN tunnels or VLANs, because those live in the Meraki dashboard and the appliance downloads them again the moment it next reaches the cloud. So resetting an MX to clear a bad configuration generally does not work — you change the configuration in the dashboard. What the reset does destroy is the purely local uplink settings you entered on the local status page: a static WAN address, PPPoE credentials, VLAN tagging on the uplink. Which is exactly the information needed to get the unit online in the first place.

A reset button on the back panel, operated with a paper clip, with the same two behaviours as the MX67: a one-second press deletes the downloaded configuration and reboots, and a hold of more than ten seconds forces a full factory reset.
Hold it for More than 10 seconds for a full factory reset; about 1 second to drop the downloaded configuration and reboot..
Release, and give the unit a few minutes to restart before trying to connect.

Dashboard configuration wins over a reset, so if the setting you are chasing came from the cloud the appliance will download it again.

A reboot is not a reset. A one-second press drops the downloaded configuration and reboots, which is usually what you want rather than a full reset.

What if you cannot get into the Meraki MX68 at all?

Yes, but through the cloud rather than the device. The local status page password is set at network level under Network-wide, Configure, General, Device configuration, and it applies to every device in the network. It cannot be read back — Meraki states that "users are unable to view the existing password in Dashboard" — but it can be reset by deleting the current password and saving, after which the device returns to the default once it fetches its configuration again. Meraki is explicit that "support is not able to view or update your password". The real lockout risk is not the appliance at all: it is losing access to the dashboard organisation, which is a Meraki account recovery matter.

If that does not work, a factory reset will always get you in, at the cost of every setting on the unit.

Worth knowing about the Meraki MX68

There is no local admin login in the sense a router-password search implies. The local status page exposes uplink and WAN configuration, IP assignment, PPPoE, proxy settings, port speed and duplex, and a support data download. Firewall rules, VLANs, VPN and content filtering are configured only in the Meraki dashboard.
192.168.128.1 only applies to a factory-default appliance that has never reached the cloud. Once it checks in it takes whatever LAN addressing the dashboard holds, which is why Meraki tells you to read your own client's default gateway instead of quoting an address.
A licence is required. Meraki's install procedure needs the enterprise licence key, and the appliance is not usable as a standalone router — until it is claimed into a dashboard organisation it sits on solid orange.
An administrator can switch the local status page off entirely. Meraki warns that if it is disabled and the IP configuration also prevents the appliance reaching the cloud, "the only option will be to perform a factory reset".
MX 19.1 changed local access for this model specifically. Any guidance written before it gives the wrong access method.
Warm spare trap: connecting to a spare appliance's LAN port shows the primary appliance's local status page. The spare has to be physically disconnected from the LAN before you can reach its own.
UDP port 53 is open on the appliance, because the local status page hostnames work by DNS interception. Scanning tools will flag it and Meraki documents it as expected.
The MX68 has two dedicated internet ports rather than the MX67's convertible LAN port. Both are configured under the uplink tab in the dashboard, so do not go looking for an MX67-style LAN 2 toggle.
Two of the eight LAN ports are PoE+, each supplying up to 30W — enough to run an access point or a phone from the appliance itself.
The USB port is on the side panel on MX68 variants rather than the back, and the cellular MX68CW has non-removable hybrid Wi-Fi and LTE antennas fitted.

Where this comes from

Meraki MX67/MX68 Installation Guide — Model-specific source for the reset button behaviour, the light table and the position of the serial number label.
Using the Cisco Meraki device local status page — The current credential model, and Meraki's instruction to find the appliance by reading a client's default gateway rather than using a fixed address.
Meraki local status page — security and SD-WAN — The documented hostnames and the MX 19.1 TLS-only behaviour, including the devices.meraki.direct redirect and port 8092.
Configuring the Meraki local status page — That the password cannot be read back in the dashboard, how to reset it, and the mandatory-password regime for networks created after 1 August 2025.
Meraki end-of-life products and dates — Neither the MX67 nor the MX68 appears, and Meraki states that absence from the table means no announcement has been made.
Cisco Unified Branch design guide — Used only for the 192.168.128.0/24 single-LAN default.