---
title: 'Charger won’t start: the seven causes we see most'
description: 'Session start failed, timeout, or authorization rejected? What usually went wrong — and what to try before you leave the bay.'
author: easyplug_team
date: '2026-02-03'
categories:
  - charging
  - product
tags:
  - drivers
  - troubleshooting
  - sessions
  - chargers
imgSocial: charger-wont-start-session.webp
imgThumb: charger-wont-start-session.webp
toc_depth: 3
---

Nothing kills trust like standing at a charger that refuses to start. You are low on battery, the bay is full behind you, and the app is still spinning.

Below is the short list of causes we see most often in production — written for drivers first, with a note on what we do product-side so the same failure is clearer next time.

## 1. The charger is offline

The map can still show a pin if status is cached or the CPO stopped updating. Live telemetry should say **unavailable** or **offline**.

**What to try:** pick another unit nearby and report the fault so the operator can recover it. If every bay on the site is offline, leave — the site is down, not your account.

## 2. Connector occupied or faulted

The cable is locked from a previous session, or the EVSE reports a hardware error. From your side it just looks like “start failed.”

**What to try:** unplug fully, wait ten seconds, try again. If the latch never releases, move one bay over and open a support ticket with the station ID.

## 3. Authorization or roaming timeout

Your eMSP asked the roaming hub (or CPO) for permission, and nobody answered in time. This is classic “works at home network, fails on the highway.”

**What to try:** retry once. If it keeps failing, that path is degraded — switch to a different network on the map if you can.

## 4. Payment not ready

Some sessions need a card on file or a minimum prepaid balance before remote start is allowed. The error is easy to misread as a charger problem.

**What to try:** check payment method in the app, then start again.

## 5. Vehicle not ready

Car locked, charge port closed, or battery already full. Many chargers report **no EV connected** even when the cable looks seated.

**What to try:** unlock the car, open the flap, confirm the inlet latched, then start.

## 6. RFID vs app mismatch

You tapped a card that is not linked to the same account as the app session you just started — or the station only accepts another scheme.

**What to try:** use one method only. If you use RFID, wait for the station to authorize before assuming the app also needs a remote start.

## 7. Local station rules

Max power tiers, fleet-only access, membership requirements, or time-of-day restrictions. These should be visible before you drive over; they often are not.

**What to try:** read site notes in the app, or ask the agent to filter for public + your connector + min power.

## What we do on the product side

Every failed start should leave a **clear reason** in the app, not a generic error. When the network is at fault, we want to re-route you to the nearest working charger and open a ticket with the right OCPP / OCPI IDs automatically.

That work is ongoing. Honest errors and re-routing beat a prettier spinner.

## What’s next

More on [stuck cables and stop failures](/blog/session-stuck-cable-wont-unlock) and [roaming authorization](/blog/roaming-failed-authorization).

→ [Talk to the agent](/#features)