How to import a certificate into WorldClient Rumi, December 21, 2020 WorldClient’s web server currently does not support generating certificate requests. If you have IIS you can use its certificate wizard to create the request and import the response. WorldClient will then be able to use it. You do not need to continue to use IIS at that point, you can disable the service and continue to use WorldClient’s built-in webserver. If you have purchased or otherwise generated a certificate from some source other than MDaemon, you can still use that certificate by using the Microsoft Management Console (MMC) to import it into the certificate store that MDaemon uses. On your Windows toolbar, click Start -> Run., and then type ‘mmc /a’ into the ‘Open:’ text box. Click OK. In the Microsoft Management Console, click Console -> Add/Remove Snap-in. (or press Ctrl+M on your keyboard). On the Standalone tab, click Add. Click Certificates, and then click Add. Choose Computer account, and then click Next. Choose Local computer, and then click Finish. Click Close, and click OK. Under ‘Certificates (Local Computer)’, click the ‘Certificates’ subfolder under the ‘Trusted Root Certification Authorities’ folder if the certificate that you are importing is self-signed. If it is not self-signed then click the ‘Personal’ folder. Click Action -> All Tasks -> Import, and click Next. Enter the file path to the certificate that you wish to import (using the Browse button if necessary), and click Next. Click Next, and click Finish. To verify the certificate will be visible to MDaemon, double click the certificate to view it from within the Certificates MMC. Verify that at the bottom of the General page is the text ‘You have a private key that corresponds to this certificate.’ On the Details page, look for the field ‘Enhanced Key Usage’ and verify it contains ‘Server Authentication.’ If those are missing, MDaemon will not be able to display the certificate. Additional Comments Note: MDaemon will only display certificates that have private keys using the Personal Information Exchange format (PKCS #12). If your imported certificate does not appear in the list then you may need to import a *.PEM file, which contains both a certificate key and private key. Importing this file using the same process outlined above will convert it to the PKCS #12 format. Related Administrations Configurations (Windows) MDaemon
Debian 7 wheezy – Certbot auto started failing with ’ No module named pip.__main__’ February 9, 2020 If you’re using Debian 7 a.k.a wheezy which is end of life at this moment and you were using Let’s Encrypt was your SSL, then you might need some backward compatibility to continue. A possible work around for me as below: wget https://raw.githubusercontent.com/certbot/certbot/75499277be6699fd5a9b884837546391950a3ec9/certbot-auto chmod +x ./certbot-auto ./certbot-auto –no-self-upgrade For renewing… Read More
Create A Network Bridge on CentOS 7 September 1, 2023 Install Module CentOS 7 comes with bridging module loaded on system boot by default. Use the following command to verify whether the module is loaded or not. # modinfo bridge filename: /lib/modules/3.10.0-327.el7.x86_64/kernel/net/bridge/bridge.ko alias: rtnl-link-bridge version: 2.3 license: GPL rhelversion: 7.2 srcversion: 905847C53FF43DEFAA0EB3C depends: stp,llc intree: Y vermagic: 3.10.0-327.el7.x86_64 SMP mod_unload modversions… Read More
Apache htaccess and htpasswd May 23, 2009March 29, 2017 In order to protect a site or a directory using Apache htaccess and htpasswd files follow the steps- 1. Creating .htaccess file and putting the following code- AuthUserFile /your/abosolute/path/to/this/file/.htpasswd AuthGroupFile /dev/null AuthName “Protected files” AuthType Basic <Limit GET> require valid-user </Limit> 2. Create a .htpasswd in the same directory as… Read More