Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallYou can self-host MySQL on a VPS with Coolify without hand-building a Docker stack: connect the VPS to your Coolify installation over SSH, create a MySQL resource in the correct project and environment, select the server and Docker destination, review the generated credentials and connection URLs, and start the resource. Keep applications on Coolify’s private network, retain the persistent volume mounted at /var/lib/mysql, and configure scheduled mysqldump backups to S3-compatible storage.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
This setup gives you control over the server and database deployment, but it does not provide automatic durability or a universal security and performance guarantee. A persistent Docker volume protects data from ordinary container recreation; only tested, off-server backups protect you from server loss, corruption, operator error, or an unusable upgrade.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Coolify is doing in this setup
Coolify is the control layer; the MySQL server itself runs as a Docker container on a connected VPS that you select. Coolify separates platform control from workload runtime, so the dashboard can manage a workload while the database files remain on the server’s storage.
The normal topology is:
- Your Coolify instance manages projects and environments.
- Your VPS is connected to Coolify over SSH and registered as a workload server.
- A MySQL resource is created on that server and its Docker destination.
- Coolify starts the MySQL container and attaches a named persistent volume at
/var/lib/mysql. - An application on the same destination reaches MySQL through Coolify’s private network and the database container name.
MySQL does not need a public IP for this arrangement. Public exposure is an exception for a genuine external-client requirement, not a prerequisite for an application deployed in Coolify.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Prerequisites and decisions before deployment
Server and access
- A running Coolify installation with permission to add servers and create resources.
- A VPS you control, with SSH access that Coolify can use to connect and run Docker workloads.
- A server role and Docker destination chosen for the database. The database and application should normally share the destination network when private connectivity is desired.
- Enough CPU, memory, disk, and I/O for your workload, backups, and growth. Coolify’s documentation does not publish a universal minimum VPS size; requirements depend on query load, connection count, dataset size, and other services on the machine.
Operational choices
- Decide which Coolify project and environment will own the database.
- Decide whether the database is used only by applications in Coolify or also by an external desktop client, reporting job, or another network.
- Choose an S3-compatible destination and retention policy before you need a restore.
- Plan where a second copy of critical backups will live. S3 storage configured in Coolify is an off-server destination, but a single bucket or account can still be deleted or compromised.
Connect the VPS to Coolify over SSH
Coolify expects you to provide the servers where workloads run. In the server-connection flow, add the VPS and supply the SSH details required by your installation. Confirm that Coolify can complete the connection and that the server is available as a deployment target before creating MySQL.
- Open the server-management area in Coolify and start the flow to add a server.
- Enter the VPS SSH address, port, user, and authentication details permitted by your server policy.
- Allow Coolify to perform its connection and Docker checks.
- Wait until the server is shown as connected and selectable for a resource.
- Confirm the Docker destination you intend to use; this is the network boundary that determines which applications can use an internal database URL.
Do not treat a successful SSH connection as proof that the database is ready for production. It only establishes that Coolify can manage containers on that host. Disk capacity, firewall rules, update procedures, monitoring, and restore testing remain your responsibility.
Deploy the MySQL resource
Use the one-click resource flow
- Open the target Coolify project and environment.
- Choose New Resource → MySQL.
- Select the connected VPS and the Docker destination.
- Review the generated image, root password, normal-user credentials, initial database, and connection URLs before starting.
- Select Start and wait for the resource and container health state to become ready.
Coolify’s documented defaults are:
| Setting | Default or behavior | What it means |
|---|---|---|
| Container image | mysql:8 |
The standard one-click resource uses the MySQL 8 image tag. |
| Internal port | 3306 |
Applications on the same destination use this container port. |
| Normal database user | mysql |
Coolify generates the normal-user password when the resource is created. |
| Initial database | default |
The resource begins with this database unless you change the supported setting. |
| Data mount | /var/lib/mysql |
MySQL’s data directory is placed on the persistent Docker volume. |
| Root password | Generated at creation | Record it in a secure password manager; do not put it in source control. |
Read the generated values immediately after creation. A password shown in a dashboard is not a substitute for an operational secret-management process, and changing credentials later can require coordinated application changes.
Connect an application to MySQL privately
For an application deployed on the same Coolify destination network, use the generated internal URL in the application’s environment variables. The documented pattern is:
mysql://<user>:<password>@<database-container>:3306/<database>
- Open the MySQL resource and copy its internal connection URL or the equivalent generated values.
- Open the application’s environment-variable settings in the same project and environment.
- Set the variable expected by your framework or ORM, such as its database URL variable, to the internal URL.
- Redeploy the application so it receives the new value.
- Run the application’s migration or health check and verify that it can create a connection without exposing MySQL publicly.
Use the database container name supplied by Coolify as the host. Do not replace it with the VPS’s server IP for an internal connection. Container-name addressing keeps traffic on the Docker network and avoids making the application depend on public routing or a changing host address.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Connection details that commonly break
- Wrong host: a server IP is being used where the internal database container name is required.
- Wrong network: the application and database were placed on different destinations, so the application cannot resolve or reach the container.
- Wrong database or user: the URL still contains the initial values while the resource uses changed credentials.
- Malformed URL: a generated password contains characters with special meaning in a URL. Preserve Coolify’s generated URL exactly, or URL-encode reserved characters when constructing one from separate fields.
- Startup race: the application starts before MySQL has completed initialization. Let the database become ready, then redeploy or restart the application according to its deployment settings.
Should MySQL be publicly accessible?
Keep the database private unless an external client truly needs direct TCP access. An application hosted in Coolify does not need public MySQL exposure when it can use the internal URL.
Recommended Free Tools
When external access is required
- Enable Coolify’s public TCP proxy for the MySQL resource only when the client cannot use the private network.
- Expose only the required proxy port.
- Restrict that port in the VPS and provider firewalls to the smallest set of source addresses possible.
- Use SSL/TLS where supported by the client and MySQL configuration.
- Prefer a VPN, bastion, or another private access path for administration instead of leaving a database port open to the internet.
- After testing, inspect the provider and host firewall rules to confirm that no broader port range was accidentally opened.
Public routing changes the threat model: password guessing, protocol scanning, TLS configuration, and firewall maintenance become part of database operations. A TCP proxy does not make an unrestricted public database safe by itself.
Persistent storage: what survives and what does not
Coolify attaches a named Docker volume to /var/lib/mysql. Because the volume is separate from the container, redeploying or recreating the container normally leaves the database files intact. This is why a routine container replacement does not automatically mean data loss.
The volume is still local to the deployment server unless you deliberately provide shared storage. If the VPS disk fails, the server is deleted, the filesystem is corrupted, or an operator removes the volume, the container’s persistence does not help. Persistent storage is not a database-aware backup.
Storage checks to perform
- Verify that the MySQL resource shows the expected data mount before loading real data.
- Keep free disk capacity for the live dataset, temporary table growth, binary or redo logs, and backup jobs.
- Do not casually delete or recreate the named volume while troubleshooting a container; that can destroy the only live copy.
- Include the volume’s server and resource identity in your operations notes so a restore or migration targets the correct database.
Configure scheduled MySQL backups
Coolify’s database-backup feature uses mysqldump. Configure it from the database-backup settings for the MySQL resource and send the result to S3-compatible storage rather than keeping the only copy beside the live database.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Open the database-backup configuration for the MySQL resource.
- Select whether to dump particular databases or all databases.
- Set the schedule appropriate for the amount of data and the maximum loss your application can tolerate.
- Set retention so old dumps are removed according to your storage and recovery policy.
- Configure the S3-compatible endpoint, bucket, credentials, and path.
- Save the configuration and run or wait for a backup according to the available Coolify controls.
- Confirm that an object appears in the destination and that its timestamp and size are plausible.
When you choose all-database dumps, Coolify gzip-compresses the dump. Compression reduces storage and transfer volume, but it does not encrypt the contents by itself. Protect the S3 credentials, bucket policy, and encryption settings separately.
What a useful backup policy includes
- A schedule matched to business activity, not merely the default interval.
- Retention long enough to cover delayed discovery of corruption or accidental deletion.
- At least one copy that is not on the MySQL VPS.
- Restricted write and read permissions for the backup bucket.
- A documented restore owner and a regular restore test.
Do not claim a particular recovery point or recovery time from the existence of a schedule. Actual RPO and RTO depend on when the dump completes, whether it is usable, storage availability, restore speed, and the procedure your team follows.
Restore a backup without making the incident worse
Coolify provides an Import Backup form that can restore a MySQL backup while the database resource is running. A restore replaces data in the target, so treat the target selection and application write behavior as safety-critical.
- Identify the exact target resource and database before importing anything.
- Stop application writes. Put the application in maintenance mode, scale it down, or otherwise prevent requests from changing data during the restore.
- Preserve a separate copy of any current data that must not be replaced.
- Open the MySQL resource’s backup-import control and select the intended backup.
- Verify the backup date, database scope, destination, and overwrite warning.
- Start the import and monitor the job until Coolify reports completion or failure.
- Run application migrations only if the restored application version requires them, then perform read and write checks against the restored data.
- Re-enable application traffic only after validating authentication, critical records, background jobs, and scheduled backups.
A successful upload or import message is not the same as a verified recovery. Test that tables, users, character sets, permissions, and application queries behave as expected. If the restore is wrong, stop writes again before attempting another recovery.
Plan MySQL image and version upgrades
The one-click resource defaults to mysql:8, but the correct image tag is a compatibility decision involving your application, drivers, schema, and backup/restore tooling. Do not change a major version on the live resource as an experiment.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Take a fresh backup and confirm that the object exists in off-server storage.
- Test restoring that backup into a separate resource or copy of the data.
- Check application compatibility with the proposed MySQL version, including authentication, SQL modes, collations, and client-library support.
- Test the upgrade procedure against the copy and record the time and any manual steps.
- Schedule a maintenance window, stop writes, and keep a rollback path.
- Perform the production change only after the backup and test results are satisfactory.
- Run application and data-integrity checks, then keep the pre-upgrade backup according to your retention policy.
Changing an image tag is not a backup strategy. A version upgrade can alter behavior even when the container starts successfully, so validate real application queries rather than relying on a green container status.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Coolify’s one-click MySQL versus Docker Compose
Both approaches run MySQL in Docker, but they serve different deployment shapes.
| Decision area | Coolify one-click MySQL | Docker Compose deployment |
|---|---|---|
| Manual configuration | Low: select a project, server, destination, review generated values, and start. | Higher: define the service, environment, network, volume, health behavior, and secrets yourself. |
| Topology flexibility | Best for a standard single MySQL resource managed by Coolify. | Better when you need a custom topology, sidecars, unusual initialization, or an engine unsupported by the one-click catalog. |
| Persistent storage | Coolify supplies the data mount at /var/lib/mysql. |
You must declare and maintain the volume and mount in Compose. |
| Backup workflow | Uses Coolify’s scheduled mysqldump settings, retention, and S3-compatible destination. |
You must design, schedule, store, monitor, and test your own backup jobs unless another platform layer provides them. |
| Upgrade control | Resource settings and image choices are managed through Coolify. | You control image tags and rollout mechanics directly, with corresponding responsibility for testing. |
| Network exposure | Private internal URLs and an optional public TCP proxy are integrated into the resource workflow. | You define published ports, networks, firewall assumptions, and external access yourself. |
Choose the one-click resource when one MySQL instance, Coolify-managed networking, and the built-in backup workflow meet your needs. Choose Compose when you require a topology or initialization pattern that the one-click resource cannot represent and you are prepared to own the additional configuration.
Operational checklist after launch
- Confirm the resource is on the intended server and Docker destination.
- Confirm the internal port is
3306and the data mount is/var/lib/mysql. - Store generated root and normal-user credentials securely.
- Set the application’s internal URL using the database container name, not the VPS IP.
- Verify that the application and database share the intended private network.
- Leave public TCP exposure disabled unless an external client needs it.
- If exposure is required, restrict the port with host and provider firewalls and use SSL where supported.
- Configure scheduled dumps, retention, and an S3-compatible destination.
- Confirm that at least one backup object can be located and downloaded.
- Perform a restore test before calling the deployment recoverable.
- Document the resource, server, volume, backup bucket, and upgrade rollback steps.
Troubleshooting common failures
The application cannot resolve the database host
Check that the application and MySQL are on the same Coolify destination network and that the URL uses the generated database container name. A host IP is the wrong substitute for an internal service name.
MySQL starts but the application receives authentication errors
Compare the application variables with the current generated user, password, database name, and port. Redeploy after correcting variables, and check for URL-reserved characters in a manually assembled connection string.
A redeploy appears to show an empty database
Stop and verify the resource before writing new data. Confirm that the original named volume is still attached and that the deployment is using the same server and resource. Do not delete volumes while investigating.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsA backup job succeeds but cannot be restored
Check that the selected dump covers the required database scope, that the object is complete in S3 storage, and that the import targets the correct MySQL resource. Test restores on a schedule rather than waiting for an incident to discover a damaged or incomplete dump.
An external client cannot connect
Confirm that public TCP proxying was intentionally enabled, the client is using the proxy endpoint and port, and both the VPS and provider firewalls allow only the client’s source address. If the client can use a private network or VPN instead, remove the public exposure.
Security and maintenance boundaries
Coolify simplifies deployment; it does not remove the need to secure the host and database. Patch the VPS and Coolify installation through your normal change process, limit SSH access, protect generated secrets, and review who can access the project and backup storage. Keep MySQL private by default, use least-privilege application accounts, and separate administrative credentials from the credentials used by application code.
There is no evidence for a universal VPS size, throughput, cost, uptime, RPO, RTO, or security posture that applies to every Coolify MySQL deployment. Measure your own workload, monitor disk and resource pressure, and let verified backup and restore exercises—not the presence of a running container—determine whether the service is ready for production.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
