POS Globalpay Terminal Payment DocumentationPOS Globalpay Terminal Payment Documentation
Buy Now
View Demo
  • Getting Started

    • Overview
    • Key Features
    • Installation
  • Configuration

    • Admin Settings
    • Node Server & SSL
  • Hardware & App

    • Mobile Terminal App
    • UPA Java Emulator
  • Operations

    • Checkout Workflow
    • Order Metadata
  • Support

    • Troubleshooting
    • FAQ
Core POS System
Buy Now
View Demo
  • Getting Started

    • Overview
    • Key Features
    • Installation
  • Configuration

    • Admin Settings
    • Node Server & SSL
  • Hardware & App

    • Mobile Terminal App
    • UPA Java Emulator
  • Operations

    • Checkout Workflow
    • Order Metadata
  • Support

    • Troubleshooting
    • FAQ
Core POS System
  • Getting Started

    • POS Globalpay Terminal Payment Documentation
    • System Overview
    • Detailed Features List
    • Plugin Installation
  • Setup & Configuration

    • Admin Gateway Configuration
    • Node.js Socket Server & Security Setup
  • Hardware & Emulator Setup

    • Globalpay Android Terminal App Setup
    • UPA Java Terminal Emulator Setup
  • Store Operations & Checkout

    • POS Checkout Workflow & Interactive Prompts
    • Order Fulfillment & Metadata Audit Logging
  • Help & FAQ

    • Troubleshooting Guide
    • Frequently Asked Questions (FAQ)

Troubleshooting Guide


1. "Confirmation Error: Read time out" or Disconnected Terminal Alert

Symptom

The cashier sees an alert modal in WooCommerce POS: Confirmation Error: Read time out or Client is not connected.

Root Causes & Solutions

  1. Node Server Stopped: Navigate to Point of Sale → Settings → Node Server in WordPress admin and check the server status button. Click Start Server if stopped.
  2. IP / Port Mismatch: Verify that the Node Server Address and Port match the server hosting the socket bridge (e.g. 192.168.15.127 and port 8081).
  3. Firewall Port Block: Ensure firewall software on the server allows incoming TCP traffic on port 8081 (or 5055).

2. Browser Mixed Content Security Block (wss:// failure)

Symptom

Browser developer console displays Blocked loading mixed active content or WebSocket fails to connect over SSL.

Root Cause & Solution

Your WordPress store runs over HTTPS (https://), but Server HTTPS Status in POS Node Server settings is disabled or missing SSL certificates.

  • Go to Point of Sale → Settings → Node Server.
  • Set Server HTTPS Status to Enable.
  • Paste valid raw PEM certificate strings into SSL Certificate Keys and SSL Private Keys textareas.
  • Save settings and restart the Node server.

3. JWT 401 Unauthorized Session Error

Symptom

Socket bridge connection fails with Invalid authorization token message.

Root Cause & Solution

The cashier's Bearer JWT session token has expired or the user account lacks cashier privileges.

  • Verify that the WordPress user account is assigned the Point of Sale Cashier or Administrator role.
  • Log out of the POS cashier interface and log back in to refresh the JWT Bearer session token.
Next
Frequently Asked Questions (FAQ)