Resolving Ignition Edge Login Failures on groov EPIC

Two different faults produce the same complaint, and they have opposite fixes. If Ignition Edge has never been successfully enabled on the EPIC processor, no gateway account exists yet — the work is to finish enablement and commissioning, and the log viewer in groov Manage will name whatever blocked startup. If the gateway is running and the administrative username or password is lost, there is no recovery path inside the device: a factory reset of the EPIC is the only way back in, and that reset erases everything else on the processor. Classify the symptom before touching anything.

Symptom Classification Before Any Reset

What the browser shows tells you which of the two faults you have. Read the row that matches exactly — a status page is not a login page, and a login page that rejects credentials is a different problem from one that never appears.

Credential Domains on the EPIC Processor

The EPIC processor hosts several independent applications, and each keeps its own account store. groov Manage authenticates device-level users against the controller's own account database. Ignition Edge authenticates against a user source — the term here means the credential store the gateway checks at login, which by default is an internal database held with the gateway's configuration. The two stores are never synchronized. A valid groov Manage administrator has no standing at the gateway login form, and the reverse is equally true.

Commissioning is the one-time setup exchange the gateway serves the first time its web page is reached. It creates the first administrative account in the internal user source. Until that exchange completes, the gateway has no credential to check, so it serves the setup page rather than a login prompt — which is why "my password does not work" and "I never get a password prompt" are separate diagnoses. Which form the setup takes depends on the Ignition version bundled with your EPIC firmware; read the version reported on the gateway page or in the Opto 22 documentation for that firmware rather than assuming a default account exists.

On a conventional server installation, a forgotten gateway password is repaired with the gateway command-line utility running on the host OS. The EPIC's embedded deployment does not expose that path to the user. That is the mechanism behind the hard rule: an unknown Ignition Edge administrator password on an EPIC is unrecoverable, and the only remaining lever is a factory reset of the whole processor.

Diagnostic Sequence in groov Manage

1. Check 1 — application state. Open groov Manage and read the Ignition Edge entry. Expect an enabled, running state. Anything else makes the password question irrelevant; fix the service first.
2. Check 2 — reach the page by link, not by typing. Follow the Ignition link from the EPIC's own landing page and accept the device certificate warning once. Expect either a commissioning page or a login form.
3. Check 3 — the log files. In the groov Manage log viewer, open the Ignition Edge logs and scroll to the timestamp at which you enabled it. Expect an ordered startup sequence ending with the gateway reporting a running state. Faults worth finding: module load failures, internal database errors, out-of-memory kills, and activation errors.
4. Check 4 — storage and memory headroom. Expect free space on the processor. A gateway that cannot write its internal database stalls before it ever serves a login form, and it does so quietly.
5. Check 5 — browser hygiene. Retry in a private window with autofill disabled and type the credentials manually. Expect the same result as before. If the result changes, the browser had been submitting stored groov Manage credentials to the gateway.
6. Check 6 — documented accounts. Try every account recorded in your commissioning notes for this unit. Expect one to succeed. If none does, and Check 3 shows a clean startup with repeated authentication failures at your attempt times, the account is lost and Procedure B applies.

Procedure A: Completing First-Time Enablement

1. Log into groov Manage with a device administrator account.
2. Open the Ignition Edge application entry and enable it. Give the service time to start; the first launch is the slowest.
3. Refresh the log viewer and confirm the startup sequence completes. Resolve any fault it names before opening the browser again — a stalled gateway will not fix itself on a page reload.
4. Open the gateway web page from the EPIC landing page and run the setup sequence to completion in one sitting. Set the administrative username and password, and write both into your device record before clicking through the last step.
5. Log in with the account you just created. If the gateway reports a trial or unlicensed condition, treat activation as a separate task; licensing state does not gate the login form.
6. Create a second administrative account in the internal user source, then download a gateway backup and store it off the device.

Procedure B: Factory Reset After Lost Gateway Credentials

A factory reset returns the entire processor to its out-of-box state — network configuration, device users, control strategy, groov View project, Node-RED flows, tag database, and the Ignition configuration. Export first; the reset is not selective.

1. Confirm the lockout is real: Check 6 exhausted, and no other administrative account responds.
2. Take a full device backup from groov Manage and copy it off the unit.
3. Export the control strategy source, the groov View project, and Node-RED flows separately, using each application's own export function. Verify each file opens on the workstation before you proceed.
4. Locate any existing Ignition gateway backup. If one exists from a working configuration, it is the fastest route back to the same tag and device configuration after the reset.
5. Plan for local access. Network settings return to factory defaults, so the address you have been using will not survive the reset.
6. Perform the reset by the procedure in the EPIC user's guide for your unit. If groov Manage credentials are also lost, request the device-level procedure from Opto 22 product support rather than improvising.
7. Re-commission: set the groov Manage administrator, restore network settings and application backups, then enable Ignition Edge and run Procedure A.

Recurring Pitfalls and Post-Recovery Verification

• Submitting groov Manage credentials at the gateway login form. Separate stores, separate accounts, no fallback between them.
• Assuming the reset touches only Ignition. It returns the whole processor to factory state, including the control strategy.
• Abandoning a half-finished commissioning page. The gateway stays uncommissioned until the account is actually created; reload and run the sequence through.
• Reading a trial or activation banner as a login failure. Those are independent conditions.
• Commissioning without recording credentials or downloading a gateway backup. That single omission converts a future lockout from a restore into a full device reset.

Verify the recovered system in this order:

1. Check 1: groov Manage reports Ignition Edge enabled and running after a controller power cycle, not just after a manual start.
2. Check 2: the log viewer shows a clean startup at the reboot timestamp with no module or database faults.
3. Check 3: the gateway serves a login form, not a setup page, and both administrative accounts authenticate in a private browser window.
4. Check 4: tags and device connections report connected on the gateway status page, matching the pre-reset configuration.
5. Check 5: download a gateway backup and confirm the file completes and opens on the workstation — a completed download is the last confirmation that the gateway's internal configuration database is intact.

FAQ