Forwarding domain through DDNS for SSL

Hi, I'm a newvie looking for help or clue about where is the right place for looking for that help or a reference.
I have a WEB application developed with ASP. It's mounted on a IIS 7 on Windows Right now I have access using http and want to use https.
I adquired the SSL certificate for domainname.com in dodaddy (the domain is there too) and have access to my server using no-ip something like jump.ddns.com, obviusly, my server is located at my office.
I use cname for jumping from primary.com to jump.ddns.com and everything goes well until I try to access via 443 port. My server is working well but the client is looking for the SSL at the domainname.com domain and the SSL is installed at the server(CRT was obiously generated in my Windows server), the ports are opened, etc. The real problem is that the certificate is not located at my primary server.
Is there a way to route everything to my windows server? so the SSL access is transparent to the client?

The SSL certificate must be installed in server where your domain is hosted and not where your domain is registered. Also i see no issue with using free letsencrypt ssl certificate instead of buying it.
If you can't install SSL in your server, just put your domain in cloudflare and proxy it, and force http/s and you will be fine.

It seems like you're encountering issues with SSL certificate setup on your Windows server for your ASP web application. To enable HTTPS access using the SSL certificate you acquired from GoDaddy, you need to ensure the certificate is properly installed and bound to the correct domain on your IIS server.

The discrepancy might be arising because the SSL certificate is issued for "domainname.com," but your client is accessing your server via "primary.com." To resolve this, you'll want to make sure that the SSL certificate matches the domain your clients are using to access your web application.

Consider using the SSL certificate for the domain your clients are visiting (primary.com) or set up a redirect from "primary.com" to "domainname.com" to align with your SSL certificate. Additionally, verify that your router/firewall is correctly forwarding traffic on port 443 to your server's internal IP address.

Testing the setup from different devices and networks can help identify any issues. If you're facing difficulties, GoDaddy's support or online forums specific to IIS and SSL configurations might provide tailored guidance for your setup. Remember, ensuring the SSL certificate is correctly installed and matches the domain being accessed is crucial for secure HTTPS connections.