Home Issue

Issue

A collection of articles addressing common errors, warnings, and issues in software and systems, along with clear, step-by-step solutions for users of all experience
Chung
By Chung
6 articles

‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead

If you recently encountered a warning like this: "[Warning] Plugin mysql_native_password reported: 'mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead." Don’t worry—this is just a message letting you know that a feature in MySQL (called mysql_native_password) will no longer be supported in the future. To ensure your MySQL server keeps running smoothly, you need to update its configuration to use a newer, more secure option: caching_sha2_password. How to Fix This Warning in FlashPanel 1. Go to the Server Page: - Open FlashPanel and navigate to the server details page where your MySQL is running. 2. Access MySQL Configuration: - Click on the "Application" tab. - Find the MySQL application in the list. 3. Open the Configuration File: - You will see a "Config" button next to MySQL. Click on it. - This will open the File Manager where MySQL configuration files are located. 4. Edit the Configuration: - You will see two files: my.cnf and mysql.cnf. - Open these files one by one. - Look for the line: default_authentication_plugin=mysql_native_password - Change it to: default_authentication_plugin=caching_sha2_password 5. Save Changes and Restart MySQL: - Save the changes in the configuration files. - Restart the MySQL server to apply the new settings. Why Is This Important? Updating to caching_sha2_password ensures better security for your MySQL server. It’s the new standard for MySQL authentication and provides stronger encryption, keeping your data safe. By following these steps, you’ll fix the warning and make sure your server stays up-to-date and secure. If you encounter any issues, feel free to reach out for further support!

Last updated on Dec 07, 2024

Validating this certificate is not possible using http-01. Possible validation methods are: dns-01

This message indicates that the standard HTTP-based validation can’t be performed. The likely reason is that your domain configuration is set to use a wildcard subdomain. Wildcard certificates (e.g., *.example.com) often require DNS-01 validation, which is more complex and can’t be done automatically in some scenarios. Why Disabling the Wildcard Subdomain Helps: By turning off the wildcard subdomain option, you switch back to a setup where the certificate can be validated using the simpler HTTP-01 method. This method is straightforward and allows the SSL provider to confirm domain ownership without needing DNS changes. How to Fix the Issue: 1. Go to Your Domain Settings: Navigate to the “update domain name” settings block. 1. Disable the Wildcard Subdomain: Locate the option that says “Enable wildcard subdomain” and remove the checkmark (untick the box). 1. Save Your Changes: Click the “Update” or “Save” button to apply your new domain settings. 1. Reinstall the SSL Certificate: Once the wildcard is disabled, retry installing the SSL certificate using the HTTP-01 validation method. The process should complete successfully this time. In Summary: You can install free SSL certificates like Let’s Encrypt or ZeroSSL easily when using standard domain validations. If you run into the “HTTP-01 not possible” error, it’s often because a wildcard subdomain is enabled. Simply disable the wildcard, update your domain settings, and try again. This quick fix allows the automatic validation to work smoothly, securing your site with a trusted, free SSL certificateb

Last updated on Dec 09, 2024

Resolving Redirect Issues After Cloning a WordPress Website

When using FlashPanel's Clone Website feature, users often ask: "Why does the cloned site redirect to the original website?" For example: - example.com (clone version) - test.example.com (original version) This guide explains the reason for the redirection and how to resolve it. Why Does This Happen? When FlashPanel clones a website, it performs a full copy of: - The source code (website files) - The database FlashPanel does not make any changes to the website's content, database, or configuration during cloning. For WordPress websites, redirection occurs because WordPress stores the site URL and home URL in its database. If these values still reference the original domain (e.g., test.example.com), any requests to the new domain (e.g., example.com) will be redirected back to the original domain. How FlashPanel Handles This FlashPanel uses WP-CLI to automatically update the WordPress siteurl and home options in the database to match the new domain during the cloning process. However, if your wp-config.php file contains hardcoded values for WP_HOME or WP_SITEURL, the redirection issue will persist. How to Fix the Issue Step 1: Check for Hardcoded Values in wp-config.php 1. Access your WordPress website's files using a file manager or SSH. 2. Open the wp-config.php file in the root directory of your WordPress installation. 3. Look for the following lines: define('WP_HOME', 'http://test.example.com'); define('WP_SITEURL', 'http://test.example.com'); Step 2: Update or Remove the Hardcoded Values - Option 1: Remove the lines If you remove these lines, WordPress will use the values stored in the database. // Remove these lines from wp-config.php // define('WP_HOME', 'http://test.example.com'); // define('WP_SITEURL', 'http://test.example.com'); - Option 2: Update the values Replace the old domain with the new domain (e.g., http://example.com). define('WP_HOME', 'http://example.com'); define('WP_SITEURL', 'http://example.com'); Step 3: Restart PHP Opcache (If Enabled) If your server has Opcache enabled, changes in wp-config.php might not take effect immediately. 1. Go to the Server Management page in FlashPanel. 2. Select the Apps tab. 3. Locate the version of PHP your website is using (e.g., PHP 8.3). 4. On the right-hand side, click the Restart button. This will clear the Opcache and apply the changes made in wp-config.php. Step 4: Test the New Website 1. Save the changes to wp-config.php. 2. Visit the new cloned domain (e.g., example.com) to ensure it no longer redirects to the original domain. Tips for Avoiding Issues - Always ensure the WordPress database is updated with the correct siteurl and home values. - Use the FlashPanel WP-CLI integration for automatic updates during cloning. - Avoid hardcoding WP_HOME and WP_SITEURL in wp-config.php unless absolutely necessary. - Remember to restart the PHP Opcache after making changes to configuration files. By following these steps, you can ensure that your cloned website functions correctly without redirecting to the original domain.

Last updated on Jan 24, 2025

Understanding and Resolving “Can Not Connect to Server!”

When using FlashPanel for remote server management, the platform establishes an SSH connection to the server to execute user requests. If this connection fails, the system will return the error message: "Can not connect to server!" Below are the possible reasons for this issue and how to resolve them. Common Causes and Solutions 1. SSH/SFTP Access Disabled for System User FlashPanel requires the system user to have SSH/SFTP access enabled to establish a connection. Solution: 1. Open FlashPanel and go to the Server Management page. 2. Select the System Users tab. 3. Check the "Can access SSH/SFTP" switch for the relevant system user. - If the switch is disabled, enable it by toggling it to the ON position. 2. Network Configuration Issues Disruptions or misconfigurations in your network settings may prevent FlashPanel from reaching the server. Solution: - Verify that your server and the FlashPanel platform are connected to a stable and properly configured network. - Test connectivity by pinging the server from your local machine. If the ping fails, investigate your network setup. 3. SSH Authentication Key Issues If the SSH key used for authentication has been changed or is no longer valid, the connection attempt will be denied. Solution: 1. Ensure that the SSH key used by FlashPanel is valid and properly configured on the server. 2. Re-add or update the SSH key in FlashPanel if necessary: - Go to the Server Management page in FlashPanel. - Update the SSH key for the server. 4. Firewall Blocking the Connection Your server’s firewall might block the SSH connection due to specific rules or closed ports. Solution: 1. Check the firewall rules on your server. Ensure that port 22 (default SSH port) is open. 2. If your server is hosted on a cloud platform like AWS, check the associated security group settings to allow SSH connections. 3. Use the FlashPanel logs or a terminal to confirm that the server is reachable via SSH. Next Steps After addressing the above issues, retry the action in FlashPanel. If the error persists, contact FlashPanel support with detailed information about the issue, including the server logs and the steps already taken to resolve it. By following this guide, you can resolve the "Can not connect to server!" issue and ensure smooth operation of your remote server management tasks.

Last updated on Jan 27, 2025

Redis Fails to Start – Troubleshooting Guide

This guide provides steps to diagnose and fix common issues when the Redis service fails to start on a Linux system using systemd. 🔍 Step 1: Check Redis Service Status Start by checking the status of the Redis service: sudo systemctl status redis-server If the service failed to start, you will see output indicating an error. Example: redis-server.service: Failed with result 'exit-code'. 📄 Step 2: View Detailed Logs with journalctl To understand why Redis failed, use journalctl to inspect logs: sudo journalctl -u redis-server This command shows the logs specific to the Redis service. 🛠 Case 1: Missing Log File/Directory Example error message from journalctl: *** FATAL CONFIG FILE ERROR *** Can't open the log file: No such file or directory This gives you precise information about what caused the failure (e.g. missing log file, port in use, config syntax error, etc.). If the error is related to missing log file or directory (as shown above), follow these steps: sudo mkdir -p /var/log/redis sudo chown redis:redis /var/log/redis sudo chmod 755 /var/log/redis sudo systemctl restart redis-server 🛠 Case 2: Port Already in Use Example error from journalctl: Failed to bind to 127.0.0.1:6379: Address already in use Cause: Another process is already using the Redis default port (6379). Solution: Check which process is using the port: sudo lsof -i :6379 If another process is occupying the port, either stop that process or change Redis’s port in the config file (/etc/redis/redis.conf): Open the config file and find the line with port 6379: sudo nano /etc/redis/redis.conf Change the port number, e.g., port 6380. ✅ Confirm Redis is Running After resolving the issue, recheck the status: sudo systemctl status redis-server You should see: Active: active (running) 🧪 Optional: View Redis Logs After Redis starts successfully, you can review logs here (if enabled in your config): cat /var/log/redis/redis-server.log

Last updated on Apr 29, 2025