contact@linuxtpoint.com
Linuxtpoint
Candid photograph of a Linux server terminal with a soft olive-green glow against a dark slate background, conveying a calm technical atmosphere.

Step-by-step guides for system administrators — covering command-line basics, web server setup, and preparation material for technical interviews.

Browse Tutorials

Installing And Configuring phpMyAdmin On Fedora

phpMyAdmin provides a browser-based interface for administering MySQL-compatible databases. On Fedora, it can simplify tasks such as creating schemas, importing SQL dumps, reviewing indexes, and managing user privileges without replacing the command line.

A secure installation still requires careful configuration. phpMyAdmin is a powerful front end, so exposing it broadly to the internet can turn a convenient tool into an attractive target. The following setup uses Fedora packages, Apache HTTP Server, MariaDB, firewalld, and SELinux.

The commands suit a Fedora workstation or small server. Australian administrators should also account for local time zones, privacy obligations, and hosting arrangements. A database hosted in Sydney, Melbourne, or Perth may be subject to different operational constraints than an overseas development machine, even when the software configuration is identical.

Component Fedora package or setting Purpose
Web server httpd Serves the phpMyAdmin interface
Database mariadb-server Stores application data
PHP connector php-mysqlnd Connects PHP to MariaDB
Administration tool phpMyAdmin Browser-based database management
Protection firewalld, SELinux, HTTPS Limits exposure and protects credentials

Prepare Fedora And MariaDB

Update the host and install the required packages:

sudo dnf upgrade --refresh
sudo dnf install httpd mariadb-server php php-mysqlnd phpMyAdmin policycoreutils-python-utils

Enable MariaDB and Apache at boot, then start them immediately:

sudo systemctl enable --now mariadb
sudo systemctl enable --now httpd

Administrators who need a refresher on service startup, dependencies, and unit overrides can consult this guide to systemd services.

Run the MariaDB hardening utility:

sudo mariadb-secure-installation

Remove anonymous accounts, test databases, and remote administrative logins when prompted. Create a dedicated database user for each application rather than allowing a website to connect as root.

Verify PHP And Enable The Alias

Check the installed PHP version and confirm Apache can execute PHP:

php --version
sudo systemctl restart httpd

Fedora’s phpMyAdmin package normally supplies an Apache configuration file and an alias. Inspect it before opening the interface:

rpm -ql phpMyAdmin | less
sudo grep -R "phpMyAdmin\|Require" /etc/httpd/conf.d/

On many Fedora releases, the interface is available at:

http://server-address/phpMyAdmin

The capitalisation in the path can matter because the configured alias may use /phpMyAdmin. If Apache reports a configuration error, validate the complete configuration:

sudo apachectl configtest
sudo journalctl -u httpd -xe

For a server in Brisbane or Melbourne, schedule maintenance using the host’s configured local time rather than assuming UTC. Confirm it with timedatectl, particularly when administrators in Perth or overseas teams share the same maintenance calendar.

Apply Firewall And SELinux Controls

Opening HTTP and HTTPS is preferable to exposing database port 3306. Allow web traffic through firewalld:

sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https
sudo firewall-cmd --reload
sudo firewall-cmd --list-services

Keep MariaDB bound to local or private interfaces unless remote database access is genuinely required. A typical application server should connect through 127.0.0.1 or a protected internal network, not through a publicly reachable address.

SELinux should remain enforcing:

getenforce
sudo ausearch -m AVC -ts recent

If phpMyAdmin can connect to MariaDB but an application cannot read its files, inspect the file labels before applying broad permissions. Use restorecon after moving web content:

sudo restorecon -Rv /var/www/html

Avoid disabling SELinux to resolve a single denial. Fedora’s security model is valuable on an internet-facing host, including one running behind an Australian NBN connection or a cloud firewall.

Restrict Browser Access

The default alias should be protected with more than a strong password. If the interface is only needed from an office or VPN, restrict access in the phpMyAdmin Apache configuration. For example:

<Directory /usr/share/phpMyAdmin/>
    DirectoryIndex index.php
    AllowOverride None
    Require ip 127.0.0.1 10.20.0.0/16
</Directory>

The permitted network must match the administrator VPN or private subnet. Reload Apache after editing:

sudo apachectl configtest
sudo systemctl reload httpd

Use HTTPS before entering database credentials. A certificate from Let’s Encrypt is suitable for a public DNS name, while an internal certificate authority may be more appropriate for a private management network. Do not rely on an obscure URL as the primary defence.

Mixed Linux and Windows environments may require separate endpoint investigation when suspicious activity appears. Background on Windows hook behaviour can help distinguish an endpoint issue from a server-side phpMyAdmin problem, but it should not replace log analysis on Fedora.

Maintain The Installation Safely

Keep Fedora, PHP, MariaDB, Apache, and phpMyAdmin updated through the package manager:

sudo dnf upgrade --refresh
rpm -q phpMyAdmin mariadb-server httpd php

Review Apache and MariaDB logs after updates:

sudo journalctl -u httpd --since "24 hours ago"
sudo journalctl -u mariadb --since "24 hours ago"

Export databases before structural changes, and test restoration rather than assuming a backup is usable. On busy systems, monitor memory and CPU pressure; guidance on CentOS resource control also applies conceptually to Fedora because both use systemd and cgroups.

Australian organisations handling customer or employee information should consider the Privacy Act 1988 and the Australian Privacy Principles when choosing database locations, backups, and administrator access. Local data residency may be a contractual requirement even where legislation does not mandate a particular region.

The key points are simple: install from trusted Fedora packages, use a dedicated MariaDB account, keep port 3306 private, enforce HTTPS, preserve SELinux, restrict the phpMyAdmin path, and maintain tested backups. A browser interface is convenient, but its safety depends on the surrounding Linux controls.