In this article, we shall discuss how to resolve Apache errors associated with WAMP installation for TeamPass. Apache WAMP (Windows, Apache, MySQL, PHP) is a software stack that allows users to create a local development environment for building and testing web applications on Windows. Please see how to Setup VirtualHost with SSL on WAMP Server, how to Configure SQL Server Instance to listen on a specific TCP Port, and How to create Virtual Hosts in a WAMPserver.
Note: Most of these errors were encountered during the configuration of TeamPass. Also, see Install and configure TeamPass Password Manager, and How to fix TeamPass stuck on working on it.
Note: Using a WAMP stack on Windows (like WampServer or XAMPP) is a great choice for developers. This is because, it is easy to set up and ideal for testing before deploying on a live server.
With WAMP, you can simulate a server environment locally, letting you code, debug, and experiment with websites and web apps in a controlled space without affecting live servers
Also, see Why is BitLocker unable to encrypt Removable Drives via MBAM? Here is ow to resolve BitLocker Protection off: Update UEFI/BIOS to fix issues, and “How to Install and Configure WordPress on Your Windows Computer Using WAMP SERVER“.
Unable to start WAMP Apache Service
When you are unable to start the WAMP service as shown below. This could be due to various reasons.
In order to determine the reason, let us take a look at the Windows Event for more information. This will enable us pinpoint the reason for the error.
Reason for the error is that the module cannot load modules “mod_foo.so”. The specified module cannot be found.
If you have an issue in the httpd.conf or any files included by it there are a couple of ways to find out what the problem is. You can also validate this error via the command prompt. In HTTP, the -t option is used to specify the directory that contains the files to be served when running a simple HTTP server. Often with tools like http-server or python -m http.server.
Open a command window, then CD into \wamp\bin\apache\apache2.x.y\bin, replace x,y with your actual version. Now you can run this command to get Apache(httpd) to validate the httpd.conf file.
httpd.exe -t
The Fix was to comment out the line ’83” “LoadModule foo_modules/mod_foo.so. Commenting out this line LoadModule foo_modules/mod_foo.so in the Apache configuration file prevents it from being loaded by Apache during startup.
Error 2: SSLSessionCache ‘shmcb’ session cache not supported
The Apache service named reported the following error: >>> SSLSessionCache: ‘shmcb’ session cache not supported (known names: ). Maybe you need to load the appropriate socache module (mod_socache_shmcb?).
The error message indicates that the Apache server is unable to start. This is because it cannot find a suitable shared memory cache (shmcb) for SSL session caching. This happens when the required module (mod_socache_shmcb) is not loaded in your Apache configuration as shown in the log message below.
To fix this issues, we will have to configure the Apache Configuration file (httpd-ssl.conf) by opening the httpd-ssl.conf file. Find the line that looks like the below and uncomment the# symbol at the beginning of the line.
We must also not forget the error reported on line 92 indicating syntax error. With the below fix, we should also be able to start the WAMP service.
If everything is fine and you run the command gain. It will display no syntax error as shown below.
Alternatively, there may be a syntax error in Apache conf files. You can check by the tool integrated in Wampserver.
Right-click -> Tools -> Check httpd.conf syntax.
Error 3: AH02577: Init: SSLPassPhraseDialog builtin is not
When you take a look at the apache.error.log. You will see the below error.
“AH02577: Init: SSLPassPhraseDialog builtin is not supported on Win32 (key file C:/wamp64/bin/apache/apache2.4.54.2/conf/key/private.key)”
-AH02311: Fatal error initialising mod_ssl, exiting. See C:/wamp64/bin/apache/apache2.4.54.2/logs/error.log for more information
– AH00016: Configuration Failed
On the error.log file, you will see the following “The Apache service named reported the following error”:
>>> SSLCertificateFile: file 'C:/wamp64/bin/apache/apache2.4.54.2/conf/key/xxxx.pem' does not exist or is empty
SSL Library Error: error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tagNote: Some articles will instruct you to discard the “BEGIN” and “END” and base64-decode the public keys contents. Because the X509EncodedKeySpec expects DER-encoded data, not PEM-encoded. This is correct, but did not resolve my issue as the log prompted another error as shown below.
SSL Library Error: error:0909006C:PEM routines:get_name:no start line (Expecting: TRUSTED CERTIFICATE) -- Bad file contents or format - or even just a forgotten SSLCertificateKeyFile?
Solution
As explained by ssl.com. A .cer file can be either in der or pem encoding. This is why, understanding the SSL encoding format and extensions is paramount. This certificate happens to be in the .pem format and needs to be in the Der format. There is a need to do conversion.
Error 4: The certificate name entered in the httpd-vhosts.conf file is incorrect
Note: When you get the following error below
- AH00526: Syntax error on line 33 of C:/wamp64/bin/apache/apache2.4.54.2/conf/extra/httpd-vhosts.conf:
- SSLCertificateFile: file ‘C:/wamp64/bin/apache/apache2.4.54.2/conf/key/xxxx.pem’ does not exist or is empty
This shows the certificate name entered in the httpd-vhosts.conf file is incorrect. Please check to ensure the right name, format and extensions is specified.
Error 5: SSL Library Error: error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error (Type=PKCS8_PRIV_KEY_INFO)
This error message indicates that there is an issue with the encoding of a PKCS8 private key. The error is caused by an unexpected value or structure in the ASN.1 data that is used to encode the key.
This error can occur in various situations, such as when trying to load a private key from a file or when trying to use a private key to establish an SSL connection. To resolve this error, you can try the following:
- Check the format of the private key. Ensure that the private key is in the correct format and that it matches the intended use case. For example, if you are using the key for SSL encryption, it should be in the PEM format.
- Check the encoding: Make sure that the private key is encoded correctly. Use a tool like OpenSSL to convert the key to the correct format if necessary.
- Check the key for errors: Use a tool like OpenSSL to check the key for errors. For example, you can use the “openssl rsa -in <key_file> -check” command to check the RSA key for errors
Now, check the permissions: Ensure that the user running the command with the necessary permissions to access the private key. As you can see above, I was not running the command prompt as an administrator.
Check the version of OpenSSL and make sure that you are using the latest version of OpenSSL. Older versions may have issues with certain key formats or encodings
Error 6: Aestan tray menu error – wamp server pop up
The Aestan Tray Menu is a graphical user interface tool that enhances the functionality of the WAMP (Windows, Apache, MySQL, PHP) server environment. It provides a user-friendly way to manage the WAMP server and its components directly from the system tray (the area near the clock on the Windows taskbar.
The image shows the Aestan Tray Menu. You can learn more about the pro and cons of this application.
Fix for me, some entries I placed in the php.ini file were removed and this error was no longer present. I therefore went ahead, refreshed and restarted the services again.
Error 7: Port use for Apache virtualhost is not the defiened variable
Apache Virtual Hosts allow enables you to run multiple websites on a single server by directing requests to different directories based on the requested domain name or IP address. This is useful for web hosting environments where multiple sites are hosted on the same server.
The image below describes the error message “Port:443 used for Apache virtualhost is not the defined variable”.
Solution
To fix this, we will have to create a virtualhost. We will have to modify the VirtualHost Form.
Note: Creating a virtual host via the WAMP web interface is a convenient way to set up and manage virtual hosts without manually editing configuration files. The WAMP server provides an intuitive graphical interface that simplifies the process, which can help avoid common configuration error.
Select the radio button and click on Modify host
Click start the creation/modification of the virtualhost
Enter the server name and the absolute path and select the to listen on port 443. Then click on start the creation.
Finish by restarting the DNS.
Error 8: Apache error Not a Listen port
The error message “Port :443 used for the VirtualHost is not an Apache define variable” usually occurs when there is a syntax error in the Apache configuration file for a virtual host. This error indicates that the specified virtual host configuration does not correspond to a valid listening port in your Apache configuration.
One common cause of this error is specifying a port number that is not defined in the Apache configuration. In this case, the error message is referring to the port number 443, which is commonly used for HTTPS traffic.
To resolve this error. This involves defining the port number in the “Listen” directive at the top of the configuration file, as well as in the VirtualHost block for the website. For example, if you want to use port 443 for HTTPS traffic. You would add the following lines to the Apache configuration file.
php
Copy code
Listen 443
<VirtualHost *:443>
...
</VirtualHost>
This would define port 443 as a valid port for Apache to listen on, and specify that the VirtualHost block applies to requests on that port.
Also, ensure that the Apache Configuration File also includes the required directives.
Add the IP address followed by the port as shown below by modifying line 36 above.
Bonus: From another guide. Also ensure the httpd.conf in the Apache main configuration file is set correctly.
Error 9: You don’t have permission to access this resource: Apache2: ‘AH01630: client denied by server configuration
The error, you don’t have permission to access this resource: Apache2: ‘AH01630: client denied by server configuration ‘Apache/2.4.54 (Win64) OpenSSL/1.1.1s PHP/8.0.26 mod_fcgid/2.3.10-dev Server at xxxxx Port 443
The above error ‘AH01630: client denied by server configuration indicates that Apache is denying access to a resource due to configuration settings. This is due to directory permissions or access control settings defined in your Apache configuration file. Please take a look at the log for more information.
[Thu May 11 15:02:45.874459 2023] [authz_core:error] [pid 14008:tid 1440] [client xx.xxx.xxx.xx:0000] AH01630: client denied by server configuration: C:/wamp64/www/TeamPass-master/
[Thu May 11 15:02:46.006448 2023] [authz_core:error] [pid 14008:tid 1440] [client xx.xxx.xxx.xx:0000] AH01630: client denied by server configuration: C:/wamp64/www/TeamPass-master/favicon.ico, referer: https://xxxxxx.com/
Reason for the error
The problem is in VirtualHost has require set to local.
<VirtualHost *:443>
ServerName tester.techdirectarchive.com
DocumentRoot "${INSTALL_DIR}/www/teampass-master"
<Directory "${INSTALL_DIR}/www/teampass-master/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require local
</Directory>
Set this to “Require all granted’ as shown below.
<VirtualHost *:443>
ServerName tester.techdirectarchive.com
DocumentRoot "${INSTALL_DIR}/www/teampass-master"
<Directory "${INSTALL_DIR}/www/teampass-master/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>When this is done, you should be able to access the URL from outside the server.
Error 10: Bad Request: Apache error associated with WAMP installation for TeamPass
Ideally, the “Bad Request” error in Apache corresponds to HTTP status code 400 and signify that the server cannot or will not process the request due to a client error. This error can arise from various issues, including malformed request syntax, invalid request message framing, or deceptive request routing. Please see the error message below.
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Apache/2.4.54 (Win64) OpenSSL/1.1.1s PHP/8.0.26 mod_fcgid/2.3.10-dev Server at localhost Port 80Reason for the issue
The issue was that the WAMP local host was trying to resolve to https. You will need to allow the users to get connected to Teampass according to the documentation. Please see the image below for more information.
The solution is to disable the Maintenance Mode on TeamPass as shown below.
Henceforth, you should be able to use your application (teamPass) without issues.
I hope you found this article very useful on how to resolve Apache errors associated with WAMP installation for TeamPass. Please feel free to leave a comment below.
The post Apache errors associated with WAMP installation for TeamPass appeared first on TechDirectArchive.