Sending Domain SSL certificate

Can you please explain in detail what you are trying to do?
 
You must ensure that the SSL is installed on the tracking domain. Mumara doesn't care about the main domain, it's the tracking domain that will be used by Mumara for tracking purposes and it should have an SSL installed.
 
have the same problem

1. i create new domain and site on my server for sending domain
for example - mysendingdomain.com

2. i create WILD SSL for these domains

mysendingdomain.com
www.mysendingdomain.com
*.mysendingdomain.com
click.mysendingdomain.com

i try differents combination....

3. i check httpS://click.mysendingdomain.com
and it work fine with SSL

4. i go to my account, add mysendingdomain.com to section "Sending Domains"
i add TXT for
key._domainkey.mysendingdomain.com

and check
and it work fine with SSL

ok, next, i add CNAME
click.mysendingdomain.com

and now httpS://click.mysendingdomain.com NOT work!!
so the problem occurs when the entry is added CNAME


please explain this
 
Hello @timonin2 ,

Adding a CNAME alone is not enough to complete the task. When you add a CNAME, it simply means that your tracking domain points to the Mumara server. However, the Mumara server does not recognize the tracking domain yet. To accomplish this, you must create a virtual host for the tracking domain in your Mumara server and link it to the Mumara folder. This creates a two-way handshake. To verify this, try accessing the tracking domain, which should open the Mumara page.

Now let's talk about SSL. The main domain has no connection to the tracking domain once you have set up the CNAME because it now points to the Mumara server. As a result, the SSL certificate must be installed on the Mumara server.

In my opinion, completing the two tasks below will resolve the issue:

1. Create a virtual host for the tracking domain in your Mumara server
2. Install an SSL certificate for the tracking domain in your Mumara server

Note: If you have a control panel, you can add the tracking domain as an addon domain inside the Mumara hosting account and point it to the Mumara installation directory. You can then look for options to install an SSL certificate. If you are familiar with it, you can also install a wildcard certificate.

Lastly, keep in mind that server-level knowledge is required for this task, so make sure you know what you're doing.
 
understand!
it is a pity that such information is not in the installation manual of your system....
I will try to do this

there is no control panel on my Mumar server right now.
Can I install Vesta? if Mumara is ALREADY installed on the server?
It cannot break the server and all settings?
 
If Mumara team set it up for you or you have built the server using Mumara command line, I can write here the guide for you to add the virtual host entry and install SSL.

Can you answer my question asked?
 
"If Mumara team set it up for you or you have built the server using Mumara command line"

i install Mumara myself using command line
 

Add a Virtual Host for the tracking domain​


Follow the steps below.

1. Login to your server via SSH
2. Create a virtualhost file in /etc/httpd/conf.d folder

Code:
vi /etc/httpd/conf.d/track.mydomain.com

Code:
<VirtualHost *:80>
     ServerAdmin [email protected]
     ServerName track.mydomain.com
     DocumentRoot /var/www/mumaradomain.com/public_html/
     ErrorLog /var/www/mumaradomain.com/logs/error.log
      <Directory /var/www/mumaradomain.com/public_html/>
         AllowOverride All
    </Directory>
</VirtualHost>

Replace track.mydomain.com with your tracking domain and mumaradomain.com with your Mumara domain (it's the folder name in actuality).

Once done, restart apache and php-fpm.

Code:
systemctl restart httpd.service
Code:
systemctl restart php-fpm.service


Install a free SSL by Let's Encrypt​

To install a free SSL, use the command below and follow the steps prompted.

Code:
cd /home && curl -o ssl_install -L https://dl.mumara.com/ssl_install && sh ssl_install
 
@Zeeshanalam, please make sure that our commands work only for the servers that were deployed using our command-line installer. It could be a reason that your server wasn't deployed using our tool.
 
Back
Top