Phpmyadmin link from hestiacp returns 404

Hi all,

after fresh install debian 12 + hestiacp, link in hestiacp DB → phpmyadmin returns 404 for all users.

What i have observed:

  • link from https: //acp,domain1,net:54321/list/db/ goes to: http: //acp,domain1,net/phpmyadmin/ –> 404 (notice the https → http redirect)
  • acp,domain1,net is the server hostname and it exists in web → domains. It has SSL cert.
  • opening http: //acp,domain1,net shows default hestia success page
  • opening https: //acp,domain1,net redirects to http
  • opening phpmyadmin via url from another domain works (https: //domain2,net/phpmyadmin/)
  • i can not login to phpmyadmin via any of these: https: //acp,domain1,net:60001/phpmyadmin/, https: //acp,domain1,net/phpmyadmin/, https: //domain1,net/phpmyadmin/ (all return 404, last two also redirect to http before 404)

I tried to add phpmyadmin SSO in settings:

  • I enabled API, whitelisted: 164.xx.xxx.xx (digitalocean reserved IP), 142.xx.xxx.xxx (droplet IP), 127.0.0.1
  • when entering password for phpmyadmin SSO, error is: “Error: mysql host localhost doesn’t exist”

I didnt modify nginx config files.

Hesgtia was installed with these params:

bash hst-install.sh \
  --port 54321 \
  --hostname 'acp.domain1.net' \
  --username 'rootuser' \
  --email '[email protected]' \
  --apache no \
  --phpfpm yes \
  --multiphp no \
  --vsftpd no \
  --proftpd no \
  --named no \
  --mysql yes \
  --mysql8 no \
  --postgresql no \
  --exim yes \
  --dovecot yes \
  --sieve no \
  --clamav yes \
  --spamassassin yes \
  --iptables yes \
  --fail2ban yes \
  --quota no \
  --webterminal no \
  --api no \
  --interactive no

Maybe solution would be to delete web domain acp,domain1,net, but the only reason it is there is that mail letsencrypt for domain1,net was returning 404 until i created ssl for domain acp,domain1,net and now mail uses ssl cert from the same web domain, so deleting it might cause more problems than it solves..

What am I missing here?

I would simply like to open phpmyadmin from within hestia cp interface, without typing phpmyadmin user/password every time..

For those facing same issue: solution was to change hestiacp web subdomain IP from reserved (floating) IP to actual server IP.
I’m really impressed with hestiacp simplicity and how it works (provided you know what you are doing) :slight_smile: