Common problems
Symptoms, likely causes and fixes for the problems most often seen when installing and running HWD POS.
Before you start
- Read the final summary the installer printed. Each ✗ points at a component. A ✗ on
sodium, Chrome/Chromium or the time zone does not prevent you from continuing; a ✗ onpdo_mysql, MariaDB or the port does. - Run the diagnostics:
sudo bash /var/www/HWDPOS/deploy/check.sh(see Diagnostics with check.sh). - Remember that rerunning the installer is safe: it does not delete data, and it puts permissions, web server configuration, services and firewall back in place.
Web access
Likely cause: the port is not listening, or the firewall is blocking it.
Check that something listens on the port and that the web server is running:
sudo ss -ltn | grep :80
sudo systemctl status apache2 # or httpd, or nginxIf you use a port other than 80, replace it in the command. Also make sure you type the port in the address (for example http://192.168.1.50:8080/).
Likely cause: the web server is not passing PHP requests to PHP-FPM.
Rerun the installer; it writes the correct web server configuration.
Nothing is wrong: the site is on another port, and the check reads that port from the configuration. If it persists, check that the web server's Listen directive includes that port. See Web server configuration.
Database
Likely cause: wrong host. localhost forces a socket connection.
Use 127.0.0.1 as the host in step 2 of the setup wizard.
Likely cause: wrong password.
Read the password generated by the installer:
sudo cat /var/www/HWDPOS/deploy/DB-CREDENTIALS.txt
# On a database-only server:
sudo cat /root/HWDPOS-DB-CREDENTIALS.txtIf the file does not match the database, rerun the installer: it applies the password from the configuration (or the credentials file) to the database user, so both match again. See Upgrade and reinstall.
Likely cause: the database connection quota is full.
Adjust it in System → Connection capacity, or with sudo hwdpanel → option 19.
Permissions and SELinux
Likely cause: file permissions, or SELinux on AlmaLinux.
-
Ubuntu/Debian: give the folder to the web user:
sudo chown -R www-data:www-data /var/www/HWDPOS -
AlmaLinux/Rocky/RHEL: rerun
install-almalinux.sh, which applies the SELinux contexts.
Likely cause: SELinux is not configured. No error message mentions SELinux, which makes this hard to spot.
Confirm it with:
sudo ausearch -m avc -ts recentThen rerun install-almalinux.sh. See AlmaLinux.
Activation
Likely cause: the server cannot reach the internet. Activation needs outbound internet access from the server.
Test it from the server:
curl -sI https://3r.com.pa/pos | head -1If there is no response, check the server's DNS, gateway and firewall. On AlmaLinux, also check SELinux (see above).
Printing
Likely cause: the print service is not running.
sudo systemctl status hwpos-print
sudo journalctl -u hwpos-print -fReinstall the background services with sudo hwdpanel → option 16. See Printing.
Likely cause: there is no working Chrome/Chromium. On Ubuntu, chromium-browser is only a bridge to Snap and does not start without snapd: sudo -u www-data chromium-browser --version answers “requires the chromium snap”.
-
Ubuntu/Debian (amd64): install Google Chrome from its official package, or use
check.sh→ “Chrome/Chromium”:curl -fsSLO https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo apt-get install -y ./google-chrome-stable_current_amd64.deb -
AlmaLinux:
sudo dnf install -y chromium
Verify it runs as the web user:
sudo -u www-data google-chrome-stable --versionIf you use a different browser, set its path in Settings → chrome_path in HWD POS.
Likely cause: the A4 printer is configured as a thermal printer.
In System → Printers, set the paper to “A4 document”.
Installer scripts
Typical message:
Repository '…ondrej/php…' changed its 'Label' value … must be accepted explicitlyThe scripts already use --allow-releaseinfo-change. To fix it by hand:
sudo apt-get update --allow-releaseinfo-changeType the path without quotes:
/root/HWDPOS-v1.5.0.zipThe script also tries to remove quotes pasted by mistake.
The process stopped before finishing. Read the error message shown earlier and run the script again. The scripts are idempotent: rerunning them does not needlessly reinstall components that already work.
The scripts detect the PHP-FPM version actually in use and check packages with:
dpkg -s phpX.Y-<extension>The check does not depend on the php version configured in the terminal. Make sure the extension is installed for the PHP-FPM version the site uses.
Likely cause: install-workers.sh or hwdpanel.sh could not be obtained (the .zip package does not include them).
Contact your provider, or copy those files to /var/www/HWDPOS/deploy/ and rerun the installer.
You are using an old version of the script, which looked for the installer inside the .zip. Download bootstrap.sh again; the current version downloads the installer from the distribution server.
You are using an old version of the script (it called apt-get, which does not exist there). Download it again:
curl -fsSL https://3r.com.pa/hwdpos_inst/bootstrap.sh | sudo bashIf the installer for this family is still unavailable, set INSTALLER_URL=… to its location or copy install-almalinux.sh to the server and run it directly.
Old version: it queried packages with dpkg, which does not exist there. Download it again; the current version queries with rpm and repairs by running install-almalinux.sh.
Still stuck?
See the FAQ, or contact your HWD POS provider with the installer's final summary and the output of CHECK_ONLY=1 bash /var/www/HWDPOS/deploy/check.sh.