SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

-

This issue typically occurs when the symbolic link is not created. You can create the link using the following command:

# ln -s /etc/apache2/sites-available/default-ssl /etc/apache2/sites-enabled/000-default-ssl

Comments

Post a Comment

Popular posts from this blog

Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)

-
The error usually arises from one of the following issues: Missing Certificate File: The certificate file may not be located at the specified path. Ensure that the file exists and the path is correctly referenced in your SSL configuration. Incorrect SSL Configuration: There may be issues within your SSL settings. Double-check your configuration files for any errors or misconfigurations that could affect SSL functionality. If neither of these issues seems to be the problem, try the following: Update the Apache Ports Configuration: Open the /etc/apache2/ports.conf file and locate the line that reads "Listen 443". Change it to "Listen 443 http". This adjustment can help ensure that Apache correctly listens for secure connections on port 443. By addressing these points, you should be able to resolve the error effectively.
Read more

Using a Self signed Certificate to Run Apache2 under SSL

-
Generating a Self-Signed Certificate for Apache2 SSL Generating a Self-Signed Certificate for Apache2 SSL This guide will help you create a self-signed certificate to enable SSL for Apache2. While using a commercial certificate is preferable for production environments, a self-signed certificate is suitable for development or testing purposes. Step 1: Enable SSL for Apache First, enable the SSL module in Apache: sudo a2enmod ssl Step 2: Create a Directory for Certificates Next, create a directory to store your self-signed certificate and its associated keys: sudo mkdir /etc/apache2/certificate Step 3: Generate the Self-Signed Certificate Now, generate the keys for your self-signed certificate. You will be prompted to provide some information during this process: sudo openssl req -new -x509 -days 1095 -nodes -out /etc/apache2/certificate/apache.pem -keyout /etc/apache2/certificate/apache.key During this step, you will see output similar to this:...
Read more

How to Efficiently Handle Sparse Files with tar

-
How to Efficiently Handle Sparse Files with tar Sparse files are files that contain empty blocks, which can take up less disk space. To efficiently create and manage backups of sparse files, you can use the tar command with the --sparse option. Here's a quick guide on how to do this. Creating a Backup of Sparse Files Open your terminal. Run the following command: tar cvSf file.tar.bz2 sparsefile c : Create a new archive. v : Verbose output (optional, shows progress). S : Handle sparse files. f : Specify the output file. file.tar.bz2 : The name of your archive. sparsefile : The sparse file you want to back up. Decompressing the Backup To restore the sparse files from your backup, follow these steps: In your terminal, run: tar xSf file.tar.bz2 x : Extract files from the archive. S : Handle sparse files during extraction. f : Specify the archive file. Conclusion Using tar with the --sparse option is an effective way to back up and restore sparse files while minimizing disk space u...
Read more