---
title: "QR Ticket & Check-In Problems"
description: "Use this guide when an Eventixa QR ticket cannot be generated, downloaded, scanned, validated, or checked in correctly. QR ticket and check-in problems usually involve one of these areas: - QR ticket generation - Attendee or booking status - Ticket…"
url: "https://eventixawp.com/docs/qr-ticket-check-in-problems/"
updated: "2026-09-26"
category: Troubleshooting
---

# QR Ticket & Check-In Problems

Use this guide when an Eventixa QR ticket cannot be generated, downloaded, scanned, validated, or checked in correctly.

QR ticket and check-in problems usually involve one of these areas:

- QR ticket generation
- Attendee or booking status
- Ticket assignment
- QR validation
- Check-In configuration
- Camera permission
- HTTPS
- Scanner access
- Duplicate check-in
- Recurring event occurrence selection
- Manual check-in

Eventixa Pro extends attendee management with QR ticket validation and check-in workflows.

Before troubleshooting the scanner itself, confirm that the attendee and ticket record are valid.

A simplified check-in workflow is:

**Booking → Attendee → Event Ticket → QR Ticket → Validation → Check-In**

For recurring events:

**Booking → Attendee → Occurrence → QR Validation → Occurrence Check-In**

## Before You Begin

Before changing QR or Check-In settings:

1. Confirm Eventixa Core is active.
2. Confirm Eventixa Pro is active.
3. Identify the exact attendee.
4. Identify the exact ticket.
5. Confirm the related booking exists.
6. If the event is recurring, identify the exact occurrence.
7. Confirm whether the issue affects QR scanning only or manual check-in too.
8. Test using a current ticket generated by the active Eventixa installation.
9. Do not publish screenshots containing usable QR codes or sensitive attendee data.

If manual check-in works but camera scanning does not, focus on the browser/device scanner environment.

## Quick Diagnosis

| Symptom | First Check |
| --- | --- |
| QR ticket is missing | Eventixa Pro + QR/PDF ticket configuration |
| QR code does not scan | Ticket validity, camera, browser, image quality |
| Scanner cannot access camera | Browser permission + HTTPS |
| Scanner works on localhost but not production | HTTPS and browser permission |
| Ticket scans but validation fails | Attendee/ticket/booking relationship |
| Ticket is already checked in | Existing attendee check-in state |
| Wrong recurring date is checked in | Selected occurrence |
| Attendee cannot be found | Event/occurrence filters and attendee record |
| Manual check-in works but QR does not | QR/scanner environment |
| QR scan works but check-in does not complete | Permission, attendee state, occurrence |
| Resent ticket still fails | Verify newly issued QR/ticket data and attendee record |

## Check Eventixa Pro

QR tickets and check-in are Eventixa Pro features.

If the QR ticket or Check-In controls are missing:

1. Confirm Eventixa Pro is installed.
2. Confirm Eventixa Pro is active.
3. Confirm the relevant QR/Check-In feature is enabled in Eventixa settings.
4. Reload the Eventixa admin screen.

Do not troubleshoot camera or browser access until the Pro feature itself is available.

## Review QR Ticket Settings

Go to: **Eventixa → Settings → Tickets**

Review the QR/PDF ticket and QR Check-In sections available in your Eventixa Pro installation.

Confirm the required ticket-generation and check-in functionality is enabled.

If a newly completed booking does not produce the expected QR ticket, first check the ticket and attendee workflow before assuming the QR image itself is broken.

## Confirm the Booking Exists

A QR ticket belongs to an attendee registration context.

Open: **Eventixa → Bookings**

Confirm:

- Booking exists
- Correct event
- Correct ticket
- Correct quantity
- Appropriate booking/payment state for the workflow

A failed or incomplete booking can affect downstream ticket delivery or attendee records.

## Confirm the Attendee Exists

Open: **Eventixa → Attendees**

Find the attendee associated with the QR ticket.

Confirm:

- Correct attendee
- Correct event
- Correct ticket
- Correct booking
- Correct recurring occurrence where applicable

If the attendee record is missing, QR validation cannot be expected to work correctly.

## Confirm Ticket Assignment

An attendee must be associated with the intended Eventixa ticket.

If the QR ticket validates against the wrong ticket or cannot be found:

1. Open the attendee record.
2. Review ticket assignment.
3. Review booking relationship.
4. For recurring events, review the occurrence.
5. Save any supported correction.
6. Generate/resend the ticket again where applicable.

## QR Ticket Is Missing

If the attendee exists but no QR ticket is available:

- Confirm Eventixa Pro is active.
- Confirm QR/PDF ticket functionality is enabled.
- Confirm the attendee is associated with a supported ticket.
- Confirm the booking reached the appropriate state.
- Review email/ticket delivery if the ticket should have been sent.
- Use the supported resend workflow where available.

If the email containing the ticket is missing, use the **Email Delivery Problems** guide.

## QR Ticket Does Not Scan

A QR code can fail to scan even when the ticket record itself is valid.

Check:

- QR code is fully visible
- Image is not cropped
- Image is not blurry
- Screen brightness is sufficient
- Camera lens is clean
- Camera can focus
- QR code is not extremely small
- Ticket was not heavily compressed
- Browser has camera access
- Scanner page is using HTTPS where required

Try the original digital ticket before testing screenshots or compressed copies.

## Avoid Heavily Compressed QR Images

Messaging apps, screenshots, image editors, and social platforms can reduce QR image quality.

If a copied image will not scan:

1. Open the original Eventixa ticket.
2. Display the QR code at full size.
3. Increase screen brightness.
4. Scan again.

Do not assume ticket validation is broken until the original QR has been tested.

## Camera Permission Is Denied

The QR scanner needs browser permission to use the camera.

If scanning does not start:

1. Open the Check-In page.
2. Check the browser's site permissions.
3. Allow Camera access.
4. Reload the page.
5. Select the correct camera if the device has multiple cameras.

On mobile devices, use the rear camera where practical.

## HTTPS Is Required for Camera Access

Modern browsers generally restrict camera access to secure contexts.

For production sites, use:

**HTTPS**

Camera scanning can behave differently on localhost during development, but a public production scanner should be served securely.

If manual check-in works but the camera does not start, verify HTTPS before troubleshooting attendee data.

## Browser Does Not Show Camera Prompt

Check:

- Camera was previously blocked for the site
- Browser permissions
- Operating-system camera permissions
- Another application is using the camera
- Site is using HTTPS
- Browser supports camera access

Reset the site's camera permission if necessary and reload the Check-In page.

## Wrong Camera Is Selected

On phones or tablets with multiple cameras, the browser can select the front-facing camera.

If scanning is difficult:

- Switch to the rear camera
- Move the device slightly farther from the QR code
- Improve lighting
- Hold both devices steady

## Scanner Opens but Detects Nothing

If the camera works but QR detection fails:

1. Center the QR code.
2. Make the entire code visible.
3. Increase lighting.
4. Avoid glare.
5. Increase ticket-screen brightness.
6. Clean the scanner camera.
7. Try the original QR ticket.
8. Test a different device.

If multiple valid Eventixa QR tickets fail on different devices, then investigate the Eventixa validation workflow.

## QR Code Is Read but Validation Fails

If the scanner recognizes the QR code but Eventixa rejects it, check the registration record.

Review:

- Attendee exists
- Correct ticket
- Correct event
- Booking is valid
- Check-In feature is enabled
- Correct recurring occurrence
- Ticket has not already been invalidated or checked in according to the current workflow

This is different from a camera-detection problem.

## Already Checked In

If Eventixa reports that an attendee is already checked in, verify the attendee's existing Check-In state before scanning again.

Do not repeatedly scan or manually toggle attendance without confirming the actual state.

Open the attendee record and review the check-in information.

An already checked-in ticket should not be treated as a new arrival.

## Duplicate Check-In Attempt

A duplicate scan can happen when:

- The same attendee presents the ticket twice
- Two staff members scan the same ticket
- The scanner is triggered repeatedly
- The attendee was already manually checked in

Before overriding anything, confirm the attendee record.

Duplicate prevention protects the event from counting the same registration more than once.

## Manual Check-In

If QR scanning is unavailable, Eventixa can support manual check-in workflows where configured.

Manual check-in is useful when:

- Device camera is unavailable
- Browser permission is blocked
- QR code is damaged
- Attendee forgot the ticket
- Network/device conditions make scanning impractical

Always verify the attendee identity and correct event/occurrence before manually checking them in.

## Manual Check-In Works but QR Scan Does Not

This strongly suggests the attendee record and check-in permissions are valid.

Focus on:

- Camera permission
- HTTPS
- QR image quality
- Browser compatibility
- Scanner page
- Device camera

Do not edit the booking simply because camera scanning fails.

## QR Scan Works but Manual Check-In Does Not

Check the admin/user permissions and the specific manual check-in interface being used.

Also verify:

- Correct attendee
- Correct event
- Correct occurrence
- Current check-in status

## Check-In Permission Problems

If a user can open Eventixa but cannot check in attendees, verify that the WordPress account has the required permission for the Check-In workflow.

Test with an authorized administrator account to determine whether the issue is permission-related.

Do not grant broad administrator access solely as a workaround unless that role is appropriate for the user.

## Attendee Cannot Be Found

If the attendee is missing from the Check-In interface:

1. Open **Eventixa → Attendees**.
2. Confirm the attendee exists.
3. Confirm the event.
4. Confirm the ticket.
5. Confirm event/occurrence filters.
6. Confirm the booking relation.
7. Clear any search/filter values and search again.

For recurring events, make sure the correct occurrence is selected.

## Recurring Event Check-In

Recurring event check-in is occurrence-aware.

The same recurring event can have several dates, and attendance for one occurrence should not be assumed to represent another occurrence.

Always verify:

- Parent event
- Occurrence date
- Attendee booking occurrence
- Selected Check-In occurrence

## Wrong Occurrence Selected

A common recurring-event check-in problem is scanning a valid attendee while the wrong occurrence is active.

For example:

**Weekly Workshop — September 10**
and
**Weekly Workshop — September 17**

The attendee may be registered for September 17 while the scanner is currently checking September 10.

Before rejecting the ticket, verify the occurrence.

## Attendee Is Valid for Another Occurrence

If a recurring attendee's QR ticket is rejected:

1. Check their booking.
2. Confirm which occurrence they registered for.
3. Switch the Check-In interface to that occurrence.
4. Scan again.

Do not modify their ticket assignment unless the booking itself is wrong.

## Recurring Check-In Shows Wrong Attendance

If an attendee appears checked in for the wrong recurring date:

- Verify the selected occurrence.
- Review previous check-in action.
- Check the attendee's occurrence assignment.
- Correct the record only through supported Eventixa admin controls.

Avoid editing stored values directly in the database.

## Event and Ticket Mismatch

A QR ticket should be validated in the context of the correct registration.

If a ticket is presented at the wrong event, Eventixa can reject it.

Verify:

- Event name
- Ticket
- Attendee
- Booking
- Occurrence

This is expected validation behavior rather than a scanner error.

## Booking Status Can Affect Validation

QR and Check-In workflows depend on the underlying registration being valid.

If the related booking is cancelled, refunded, incomplete, or otherwise not eligible for attendance, review the booking before attempting to override QR validation.

Open:

**Eventixa → Bookings**

and confirm the current booking status.

## Payment Status and Paid Tickets

For paid registrations, also review the payment status when attendee validity appears inconsistent.

A booking record can exist without successful payment.

If the payment state is wrong, use the **Payment Problems** guide before changing Check-In data.

## Resent Ticket Still Does Not Validate

If you resend a ticket and the new email arrives but scanning still fails:

1. Confirm the attendee record.
2. Confirm the ticket assignment.
3. Confirm the event/occurrence.
4. Use the latest ticket.
5. Check whether the attendee is already checked in.
6. Test manual check-in.
7. Test another scanner device.

Repeatedly resending will not fix an incorrect attendee/ticket relationship.

## Ticket Email Arrives Without QR Ticket

If the email arrives but the expected QR/PDF content is missing:

- Confirm Eventixa Pro is active.
- Confirm QR/PDF ticket settings.
- Confirm the supported ticket workflow applies.
- Review the relevant email/ticket configuration.
- Generate a new test booking.

If the entire email is missing, use the Email Delivery troubleshooting guide instead.

## Check-In Page Does Not Load Correctly

If the scanner interface is blank or broken:

1. Clear WordPress/server/CDN/browser cache.
2. Test in a private browser window.
3. Confirm required Eventixa scripts are loading.
4. Check browser console errors.
5. Check failed AJAX/REST requests.
6. Temporarily disable aggressive script optimization on the Check-In page.

Dynamic scanner pages should not be cached in a way that interferes with real-time validation.

## JavaScript Optimization Problems

QR scanning depends on frontend JavaScript.

When troubleshooting, temporarily test without:

- JavaScript delay
- JavaScript combine rules affecting Eventixa
- Script deferral that breaks scanner initialization
- HTML optimization that changes scanner markup

If disabling optimization fixes scanning, configure a narrow exclusion for the affected Eventixa assets/page.

## Network Problems at the Venue

Check-In may require the scanner device to communicate with the WordPress site.

If scanning works before the event but fails at the venue:

- Test venue Wi-Fi
- Test mobile data
- Confirm the site is reachable
- Confirm HTTPS certificate is valid
- Avoid captive-portal Wi-Fi issues
- Keep a manual check-in fallback where practical

Do not wait until attendees arrive to test network connectivity.

## Device Preparation Before the Event

Before opening check-in:

1. Charge scanner devices.
2. Test camera permission.
3. Test HTTPS access.
4. Scan several test tickets.
5. Confirm the correct event.
6. For recurring events, confirm the correct occurrence.
7. Verify staff login/access.
8. Test manual check-in.
9. Confirm internet connectivity.

This prevents many venue-day problems.

## Cache and Scanner State

Do not use full-page caching for a dynamic check-in workflow.

If an attendee was just checked in but another device still shows old information, refresh the scanner/admin state and confirm the live attendee record.

## Example: QR Code Will Not Scan

Suppose an attendee presents a valid ticket but the scanner does not detect the code.

Check:

1. Camera permission.
2. HTTPS.
3. Camera focus.
4. QR image quality.
5. Screen brightness.
6. Original ticket instead of screenshot.
7. Another scanner device.
8. Manual check-in.

If manual check-in succeeds, focus on the scanner environment rather than the attendee record.

## Example: Valid Ticket Is Rejected at a Recurring Event

Suppose the QR code scans but Eventixa says the attendee is not valid.

Check:

1. Open the attendee record.
2. Verify the booking.
3. Confirm the registered occurrence.
4. Check the occurrence currently selected in Check-In.
5. Switch to the correct occurrence.
6. Scan again.

A valid ticket for one occurrence should not automatically be treated as valid for every occurrence in the series.

## Example: Ticket Shows Already Checked In

If Eventixa reports that the ticket has already been used:

1. Open **Eventixa → Attendees**.
2. Find the attendee.
3. Review check-in state.
4. Confirm whether another staff member already checked them in.
5. Confirm the correct occurrence.
6. Do not create a second attendee record to bypass the status.

## Recommended Diagnostic Workflow

When QR Check-In fails:

1. Confirm Eventixa Pro is active.
2. Confirm QR/Check-In features are enabled.
3. Open the attendee record.
4. Verify booking.
5. Verify ticket assignment.
6. Verify event.
7. If recurring, verify occurrence.
8. Review current check-in state.
9. Test manual check-in.
10. If manual works, inspect camera/HTTPS/browser.
11. Test the original QR ticket.
12. Test another device/browser.
13. Clear dynamic-page caches.
14. Check browser console/network errors.
15. Record the exact validation message before contacting support.

## Important Notes

- QR Tickets and Check-In require Eventixa Pro.
- QR validation depends on valid attendee, booking, ticket, and event relationships.
- Camera scanning requires browser permission.
- Production camera access should use HTTPS.
- Manual check-in can be used as a fallback where supported.
- Already checked-in attendees should not be counted again.
- Recurring-event check-in must use the correct occurrence.
- A ticket valid for one occurrence should not automatically validate for another.
- Booking/payment state can affect registration validity.
- QR image quality can affect scanning without indicating a ticket-data problem.
- Dynamic Check-In pages should not be aggressively cached.
- Never publish real QR codes or attendee personal information in documentation screenshots.

## Troubleshooting

### QR Ticket Is Missing

Check Eventixa Pro, QR/PDF ticket settings, attendee record, ticket assignment, and booking state.

### QR Code Does Not Scan

Check camera permission, HTTPS, image quality, brightness, focus, and the original ticket.

### Scanner Cannot Access the Camera

Allow camera access in the browser and operating system, verify HTTPS, then reload the page.

### QR Code Scans but Is Rejected

Verify attendee, booking, ticket, event, and recurring occurrence.

### Ticket Says Already Checked In

Review the attendee's current check-in status before scanning again.

### Attendee Is Missing from Check-In

Check attendee filters, event, ticket, booking, and occurrence.

### Manual Check-In Works but Scanner Does Not

Focus on camera permission, browser, HTTPS, device, QR quality, and frontend script loading.

### Wrong Recurring Date Is Checked In

Verify the occurrence selected in the Check-In interface and the attendee's booking occurrence.

### Ticket Email Is Missing

Use the **Email Delivery Problems** guide.

### Paid Attendee Is Not Valid

Check the associated booking and payment status before overriding check-in validation.

## Related Documentation

- [Troubleshooting Overview](https://eventixawp.com/docs/troubleshooting-overview/)
- [QR Tickets](https://eventixawp.com/docs/qr-tickets/)
- [Event Check-In](https://eventixawp.com/docs/event-check-in/)
- [QR Scanner](https://eventixawp.com/docs/qr-scanner/)
- [Check-In for Recurring Events](https://eventixawp.com/docs/check-in-recurring-events/)
- [Managing Attendees](https://eventixawp.com/docs/managing-attendees/)
- [Resend Event Tickets](https://eventixawp.com/docs/resend-event-tickets/)

## Frequently Asked Questions

### Why does the QR code scan but Eventixa reject the ticket?

The camera can successfully read the QR code while Eventixa validation rejects the underlying attendee, ticket, event, booking, or occurrence context.

### Does QR scanning require HTTPS?

For production browser camera access, HTTPS is generally required by modern browsers.

### Can I check in an attendee without scanning the QR code?

Where supported, use Eventixa's manual check-in workflow after verifying the attendee identity and registration.

### Why does a recurring-event ticket fail on one date?

Recurring check-in is occurrence-aware. Confirm the attendee registered for the occurrence currently selected in the Check-In interface.

### Why does Eventixa say the attendee is already checked in?

The attendee record already contains a check-in state for the relevant context. Verify whether another staff member or a previous scan completed the check-in.