- Joined
- Dec 27, 2023
- Messages
- 2
- Points
- 1
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?
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?