I have a little website in my IIS and i tried to configure HTTPS.
I created an autosigned cert but i still have the NET::ERR_CERT_AUTHORITY_INVALID if i try to open in google chrome from the internet ( using the public ip adresse).
I don't have any domain name and don't want any domain name.
I wonder where is the probleme with my certificate, is it because i have to set the IP in the certificate ? Is there any simple way to do it ? My website is juste an access from a rest webservice, i just want to use with my IP and using https.
Is it possible ?
Thanks
Related
I am hosting a web app on a Digital Ocean VPN. I set up an A record via GoDaddy to point my domain to the VPN server. I'm wondering if there is a way to still access public files from within the web app that I have on GoDaddy shared hosting at that same address.
I basically want to access a file at http://example.com/uploads/somedoc.pdf
Which would be at the following path on the GoDaddy server:
home/site/public_html/uploads/...
But example.com now points to the VPN. I tried using the GoDaddy website IP address instead in the URL but that doesn't work either. I get a 404 file not found error even though the files are actually in the uploads folder. I figure it's looking for them on the VPN instead.
In case anyone else runs into this problem I solved my issue by simply adding an A Record for a subdomain in my DNS zone file and I was able to point my VPN server IP to that subdomain. So with my web app being served at app.example.com I was successfully able to access the files on the GoDaddy shared server from my web app (ie example.com/uploads/somefile.docx).
To ensure that the client would still visit the web app at the new subdomain I setup a permanent redirect to send all traffic from example.com to app.example.com instead of them having to remember to type the subdomain each time they want to access the web app.
I would like to have my webserver on AzureVM. I will use multiple sites via host header.
Bindings: All unassigned and host header = www.site.com
My VM is configured and sites running locally (I can show website on erver in IIS.. Browse...) with no problem. Endpoints are configured too. Default web page of IIS is accessible on address .cloudapp.net
Problem:
I cant access my second website from internet:
service.cloudapp.net/www.site.com (this is maybe wrong)
service.cloudapp.net.www.site.com
service.cloudapp.net.www.site.com.
Nothing working :-(
Haw can i access it?
Thank you in
You can have multiple websites hosted on the same IIS Server.
To access the websites individually over the Internet, you need to suffix the DNS Name with the Public Port.
For Example :
DNS Name : myvm.cloudapp.net
Website 1 : myvm.cloudapp.net:52477
Website 2 : myvm.cloudapp.net: 51998
However if you are using Host Headers in IIS, you might want to refer to the below link which gives more insight
https://msdn.microsoft.com/en-us/library/azure/gg433110.aspx
Hope this helps !
Regards,
Sowmya
I am able to access my website via the domain name outside of the network.
On the internal network I am able to access the site via "localhost/websiteName/", "internalIP/websiteName", and "computerName/websiteName", but I am unable to hit either "http://example.com" or "http://www.example.com".
I was able to get it to work on a computer by adding the ip and website to the hosts file, but I am still unable to access the website using the domain via mobile devices on the internal WiFi.
I completely disabled the firewall, so I know that that is not the problem.
I have bindings set up for www and without www with all IP Adresses unassigned.
I did try adding a binding for both www and not, using the internal and external IP addresses, both IPv4 and IPv6.
I am running this on http without any certificates.
I have a cname record for www
My # record is pointing to my external, static IP
The website is set up separately from the default website and it is not a virtual directory.
I am using Comcast Business with their Cisco DPC3939B router.
This is initial setup of the website, and it is not an issue that just started after having worked previously.
I figured it out. All I did was add an # record to the DNS to resolve the website to the internal IP. Here is a really great reference for accessing websites on a Local Network: devside.net
I am having some trouble with hosing.
Currently on our server have have 6 or so IIS sites hosted. They are all http currently: and work on port 80 with the host names set.
Now I want to go an change them to use SSL. But this then removes the ability to use the Host headers.
I have tried using self generated ssl cert from within IIS Manager before I go out and buy real ones. But the issue I am having is that it seems that the SSL cert is linked to an IP address. I can add the ssl cert to one site. But after that When I try assign site 2. it says that there are no Ip addresses.
So My question which Im hoping someone can explain how it works when multiple sites are hosted with iis on the same machine.
Do I have to get a wildcard SSL Certificate?
Do I need to have a unique IP address for each site being hosted?
If not, could somebosy please help and try explain to me what I need to do in order to achieve this.
Can anybody explain why I see another web site at my http secure address. I don't have a certificate. I can manage files from folder httpsdocs but cannot access them from web. Also httpsdocs is empty. https://innovacube.com/
And base of my problem is Google indexes my https domain but I cannot denny Google Bot.
You're sharing IP addresses with another site - you'll see that both www.innovacube.com and www.cokyader.com resolve to 92.199.202.62. HTTP/1.1 allows this because you also send a host header
GET / HTTP/1.1
Host: www.innovacube.com
so the web server knows which site to serve for a given connection.
It isn't, however, possible to do this for HTTPS. The problem is that the certificate negotiation happens before the server gets to HTTP so you can't switch depending on the site that the browser really means. Therefore you can only host one HTTPS site per IP and this IP is hosting cokyader.com. (There are proposed extensions to help fix this but I've never seen any progress on this.)
If you want your own separate HTTPS site then your host will have to allocate you your own separate IP address.
Because you are using shared hosting, and it has been configured with a default SSL site that isn't yours (but presumably belongs to someone who has paid for SSL support and has their site hosted on the same server).