Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Greetings!
This is interesting. I could see a clear reason for HeidiSQL, and maybe that leads to the reason for the others. I assume phpMyAdmin and Adminer are set up on the server while HeidiSQL is run remotely. If they’re all three remote, then my idea makes sense across all of them.
When you create a user in MySQL, you define a host. If you do not define a host, it defaults to localhost. This means that all users are “user@ip” and by default “user@localhost.” So when you try to log in externally, you’re not just logging in as “user” but as “user@yourexternalip” instead.
Creating a remote user works like this from the shell:
GRANT ALL PRIVILEGES ON database.* TO 'username'@'ipaddress' IDENTIFIED BY 'password';
To connect remotely, ipaddress should be your external IP as found here: https://ifconfig.me/
Jarland