I'm trying to understand how hosting providers implementing the support for SSL.
As I know (i found many resources on web to confirm this), it's impossible to assign a SSL for more than one domain on IIS, if these domains sharing the same EP (IP:PORT).
If so, how then GoDaddy (on other hosting provider) allows me to set SSL for my site?
Does they provide IP for each hosting account? Does they provide virtual server with IP and IIS?
The question is totally theoretical and just for understanding the technology...
Thanks
If you have an SSL on Go Daddy shared hosting you are assigned a dedicated IP.
Related
I have a quick question on opting the SSL Certificate for the Web Application. In the Web Application, am using Kestrel as WebServer and application is not configured in IIS.
For Customers, I install the Application as a Service in Server Machine and its used by the employees only in intranet. Now the address of my application is http://machineName:port but I would like to have https://machineName:port.
Question 1) Is this possible for the Intranet sites?
Question 2) Will SSL be really needed in this case?
Qeustion 3) SSL works, only if I configure Web Application with IIS?
Yes it is possible. As long as the certificate is trusted by the clients. You can create a self signed certificate and have client machines add it to trusted root certificate authorities in windows. Or if the intranet is using a windows domain, you can have a Certificate Authority trusted by domain computers issue the certificate.
SSL is always better even in intranet and localhost scenarios. It ensures site identity, encrypts traffic, etc. Whether it is needed depends on the site. Some browser functionality such as using the camera/mic won't work unless the website is using SSL.
Kestrel allows using SSL. Checkout docs here.
So,
I currently have a net core web api running in a windows VPS (amongst other things). When I make requests to this api, I would like to do so using https. It seems I need to have an SSL Cert on this VPS (which does not have a domain, just an IP).
The https API is on xxx.xxx.xxx.xxx:443
The net core application is published into a self-contained package and run as an .exe (i think using IIS express)
Ideally I would like to use a free SSL cert from something like zerossl.com or any viable alternative you may suggest
How can I go about making it so that if I access xxx.xxx.xxx.xxx:443/api/values, I get a secured icon in my browser?
Thanks
It seems I need to have an SSL Cert on this VPS (which does not have a domain, just an IP)
It is impossible to bind SSL Certificate to IP address.It must bind to domain.
My hosting company has implemented SSL on my account. It is a multi-site Drupal setup and the sites that are accessed directly via my domain registrar (Hover) are working correctly but one site doesn't ... the problem for that site appears to be that I forward that domain to FastMail to manage some email and from there I forward the domain to the web host. I get the domain name is not secure and this message: NET::ERR_CERT_COMMON_NAME_INVALID
Does anyone know how to change the configuration?
Thanks for the feedback however my host service was unable to set the site to use ssl because it went via a 3rd party mail server.
I have a wcf service which work locally and within the network when used with the server name, this service needs to work on the internet to others outside the network to consume. I am currently hosting it on IIS. what will I need to make it available on the internet ? Do I need a DNS and SSL ? I am not sure what is required. Could somebody please let me know.
If your web service is going to be open to the public, i.e. on the internet, then you will need a domain or at least have your IP mapped to a name in DNS accessible to the public, this would require that you are self hosting the sight on you own server and have a static IP address accessible outsite your network.
Typically you would run a DNS to map your web service's IP to a domain name. However if you are going through a hosting provider they will most likely do that part for you.
Anything public facing, I would recommend using SSL over HTTPS. If the service will only be accessible to certain people, then you could use several of the different types of authentication, certificates, username/password, or tokens. There are lots of things to consider like firewalls etc.
Here some maybe helpful links to get you started:
SSL in IIS
How do I host a wcf service on the internet?
Question in the simplest way possible: I have a website which I want to make capable to use https - how to do it?
I heard about Google and its super powers, but the amount of results treating about ssl and https and so on, is too d* high. I'm really afraid to end up with incompatible certificates or empty bank account because of choosing wrong article or something out there.
I politely ask you to help me find the right articles about this topic. "Where do I start, where do I begin" as Chemical Brothers have sung.
I have an account on shared hosting
the very goal is to let users use my website through the https connections
I have one domain
all of images, javascript, css files are on the same domain
I'm aware of fact that maybe the best articles are right before my eyes (even now as I'm writing this question), but please - be understanding. I don't even know what should I know in the first place.
Thank you in advance for any guides.
First of all you need to create an SSL certificate. There are lots of sites out there that do it http://www.selfsignedcertificate.com/ or http://www.godaddy.com.
Once you have a certificate you need to install it on your web server. Depending on Windows or other OS you will do this differently.
Lastly you will configure you website to use https (port 443) rather than http (port 80). This is configured with IIS or Apache directly.
Hopefully this link for windows and this for Apache helps a bit too.
If you are using another hosting application, just Google: install ssl certificate [myhostingApplication]
Update:
For shared hosting this will more than likely depend on your hosting provider. If you don't have access to IIS or similar, you more than likely will have to contact your provider directly. I use shared hosting with GoDaddy and they say:
NOTE: If you want to install an SSL certificate on our shared hosting, Website Builder or Quick Shopping Cart®, you must purchase one of our SSL certificates. We do not install SSL certificates from other providers on our shared hosting accounts.
Your provider may be the same. So do be careful.
When I click on myAccount->SSL Certificates it redirects me to a page where I need to purchase one from GoDaddy. Upon purchasing one, I can then manage it from SSL Certificates on myAccount page.
Your provider may be different, since you haven't mentioned who they are, you may just have to scour their knowledge base.