NOL Ticket "예매 정보가 올바르지 않습니다" (Invalid Booking Information) Error — How to Fix It

🇰🇷 Read in Korean NOL 티켓 예매 오류 해결 (한국어, Naver) ›

When you book Doosan or Kiwoom tickets and switch accounts even once, the ticketing can suddenly break. You get force-quit out of the queue, or you press the booking button and a warning pops up — "예매 가능한 경기가 없습니다" (No games available for booking) or "예매 정보가 올바르지 않습니다" (Invalid booking information) — and you're bounced back to square one.

The short answer: this happens because the old session gets tangled when you switch accounts. Accessing each account from a different browser (or an incognito window) clears it up.

What the symptom looks like

Here's the exact order it happened to me.

• I was already logged in with my presale account, and
• when I tried to log in again for the general sale → the moment I entered ticketing,
  • I'd get force-quit out of the queue, or
  • while the booking screen was loading, a warning would appear — "예매 가능한 경기가 없습니다" or "예매 정보가 올바르지 않습니다" — and bounce me back to the start.

At first it threw me — the "Book now" button was clearly active, so why would it say there were no games to book? But my first account always loaded fine; it only broke at the same spot whenever I switched accounts.

My case started with a presale account, but this has nothing to do with presale access. It can hit anyone who logs out and logs back in with a different account in the same browser — even during the regular sale. The real trigger is switching accounts within one browser.

It happened even when I moved from Doosan to Kiwoom, too. Those are completely different sites with different addresses, yet the same thing happened.

Seeing it on the actual screen (Doosan vs KT, June 9, 2026)

I ran into it while booking Doosan vs KT (June 16, at Jamsil). On the official Doosan Bears site, pressing "ticket booking" hands you off to the Interpark (NOL) queue.

Press "예매하기" (Book now) and it just keeps spinning on "예매 화면을 불러오는 중입니다" (Loading the booking screen).

Then this alert appeared.

"예매 정보가 올바르지 않습니다. 다시 예매를 진행해 주시기 바랍니다."
(The booking information is invalid. Please start the booking again.)

Pressing "확인" (OK) just bounces you back to the Doosan calendar — square one. Pressing it again bounced me at the same spot, over and over.

Kiwoom is a separate site, but it did the exact same thing

Kiwoom got blocked the same way. The official Kiwoom Heroes site (heroesbaseball.co.kr) has a completely different address from Doosan,

yet when I went into the general sale there, I got the exact same error, word for word.

The reason two different sites threw the same error is that both run on Interpark NOL. The NOL session left in your browser follows you across sites. In the end I closed the original Chrome and logged in again on the Whale browser (a Korean browser), and it worked on the first try. Any browser you weren't already using works the same way — Edge, Safari, or Firefox. And if installing another browser is a hassle, opening an incognito window in the same browser clears it too. I confirmed both myself.

Going in through an incognito window worked

When I reconnected through an incognito window, the screen that had been blocking me went straight through to the seat-selection step. The queue and the captcha passed cleanly too.

Below is why this happens and the exact steps to fix it.

Why this happens

Doosan and Kiwoom both run on Interpark NOL (놀티켓). So when you log out and log back in with a different account in the same browser, the previous account's session and cookies stay behind in that browser.

Go into the queue or booking in that state, and the system decides the leftover session conflicts with the new account info — so it force-quits you, or fails to load the booking screen properly and throws a misleading message like "No games available for booking."

In other words, that warning doesn't mean there really are no games — it's a glitch from a tangled session. (It showed up during the general-sale window, after all.)

How to fix it

1. Use a different browser for each account. For example, account A on Chrome, account B on Edge, Safari, or Firefox (or a Chrome incognito window). Different browsers keep the sessions fully separated, so they don't conflict. I was stuck on Chrome and it cleared the moment I switched to Whale.
2. If you want to stay on one browser, clear cookies and cache before switching accounts. Just note that clearing cookies logs you out of other sites too, so it's a bit of a hassle. That's why option 1 (separate browsers) is easier.
3. When possible, keep it clean with one account = one browser.

One thing to watch out for. An incognito window is only clean the moment you open it fresh. If you log out inside that same incognito window and log in with another ID, the same error can come back. So close the incognito window completely and open a new one each time you switch accounts.

Also, incognito windows occasionally throw an error at the payment step. If you're worried about payment, I'd go with bank transfer (무통장입금) rather than card. You just need to deposit within the deadline, which lowers the chance of losing a held seat to a payment error.

One more tip, this one for prevention: you can check for a tangled session before the real ticketing. If there’s another game whose booking is already open, click into its booking once beforehand — if it loads normally, your session is clean; if the same error pops up, switch to a different browser or a fresh incognito window ahead of time. The catch: if nothing is open to test with (like on a day with no pre-opened games), you can’t run this check.

Frequently asked questions (FAQ)

Does "예매 가능한 경기가 없습니다" really mean there are no games?

If it shows up during the general-sale window, it’s usually not that there are no games — it’s a session glitch. Try reconnecting with a different browser.

I keep getting bounced by "예매 정보가 올바르지 않습니다."

If this shows up while the booking screen is loading even though you didn’t refresh, it’s usually a tangled session left in your browser. Close the browser you first connected with, and log in again on a different browser you don’t normally use for booking — Edge, Safari, or Firefox all work. For me, switching from Chrome to Whale (a Korean browser) fixed it on the first try.

Does an incognito window work too?

Yes. An incognito window starts without your existing cookies and session, so it’s effective for separating accounts. When I went in through incognito, the booking that had been blocked went all the way to seat selection. Just note that if you log in with another ID inside the same incognito window, the same error can return — so close it and open a new one when you switch accounts. If payment feels shaky in incognito, bank transfer is another option.

I cleared the cache but it still happens.

Clearing the cache alone often doesn’t fix it. The tangled session lives in your cookies and login info, not the cache — so if you wipe the cache but keep the cookies, the same error stays. Either clear cookies too (you’ll get logged out of other sites), or more simply, open a different browser or a fresh incognito window. Incognito starts cookies from scratch, so it’s the most reliable.

Do other teams have this too?

If they run on the same NOL (놀티켓) platform, it can be similar. Separating browsers when you switch accounts is the safe move.

---

Source: First-hand experience + how browser sessions work.