I have two sites in my IIS 8 server. Site MyProjectA and MyProjectB, for each project I have a domain name, lets say myprojecta.com and myprojectb.com. I have set in my DNS provider that both domains points to the server IP. I have configured so MyProjectA runs on 443 and MyprojectB runs on 8181, both SSL.
So if I browse to:
https://myprojecta.com I see MyProjectA and its working fine
If I browse to:
https://myprojectb.com:8181 I see MyProjectB and that is working
fine.
But now I wonder, how can I configure so I can omit the :8181 part, and in turn reach MyProjectB site by browsing to https://myprojectb.com only (and with correct certificate). As far as I understood this should be possible with a reverse proxy configuration in IIS but I cannot get it to work. Anyone can help how to achieve that?
Since you are using IIS 8, the simplest approach is to set up multiple HTTPS sites at port 443 using SNI support. Then there is no need of reverse proxy.
Reference
Related
I have 3 sites(virtual directories) registered under the Default Web Site in IIS, those can access like below:
http://localhost/Site1
http://localhost/Site2
http://localhost/Site3
Currently I have one port number which is port 80.
I need to setup those sites with https having different port numbers, like below:
https://demo.mydomain.com:5001/Site1
https://demo.mydomain.com:5002/Site2
https://demo.mydomain.com:5003/Site3
I am new to the IIS. Can someone please help me out with the approach to solve the above scenario?
is the domain already pointing to your webserver or are you trying to achieve this on you development machine?
If the domain is already pointing to the server, you can do this IIS by adding bindings to your websites (in your case its the defaultwebsite).
You can achieve this by right-clicking the website. Here you can see "Edit Bindings". You will have to add a binding foreach port. Just click on "add" and type in the right hostname (demo.mydomain.com) and the port. You can also choose a certificate here for the https connection.
If you are trying to achieve this on your dev machine, you will also have to add your hostname to the windows hosts-file. Under "C:\Windows\System32\drivers\etc\hosts" add the line "127.0.0.1 demo.mydomain.com".
Jonathan
Hi everyone need your support with the following problem. Please do apologies if I confuse you in anyways with my explanation.
I have a add-on domain (example.com) pointed to a Godaddy Linux server, domain is also in the Godaddy same account.
The web application for "example.com" is a Laravel 5.6 based one, and the web app has 'Get' type search form which needs to be forwarded to another Windows IIS server's port with all the query strings where another web app is hosted. the action of the from will be similar to below.
Request => http://sub1.example.com/route/method?var=val1&var2=val2&var3=val3
From this point on-wards the application has to continue work from the IIS server with the subdomain, which mean I am not expecting any replies from this IIS server to the Linux server.
Its been advised to use the subdomain to mask the forwarding to the IIS server, so I did like above with sub1 sub-domain. This subdomain has to be forwarded to a server's port as I mentioned above, something similar to below.
http://sub1.example.com => http://xxx.xxx.xxx.xx:9596
I did tried with the Godaddy's default subdomain forwarding with masking, but the query strings are not being forwarded and shows "Destination Unknown" error.
In a online forum its been advised not to go with Godaddy's forwarding instead go with .htaccess to have more control.
Therefore any possible solutions or your support with the redirection with .htaccess from web application to the external web server's specific port along with the query strings would be a life saver.
Thank you in advance.
As per the GoDaddy support, the domain forwarding to a IP's port is not possible with the Shared hosting.
The support suggested to go-ahead with the VPS and configure.
Please do comment, if this is wrong statement!
I am hosting my public facing site at a shared host (Hostgator) with the domain pointing to the same. I also have my application hosted on a dedicated server with a different host. Both servers have their own SSL certificates installed.
Is there any way to edit the .htaccess file to do the following:
https://www.domain.com/CUSTOMER redirects to https://x.x.x.x/CUSTOMER while the browser still shows www.domain.com/CUSTOMER?
I'm vary of using frames due to the SSL ramifications. My domain registrar is Hostway and they do not offer URL masking/forwarding.
This can be done by making your server act as a proxy. Even if you have no access to the servers configuration you might be lucky that apaches proxy module is loaded: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html
If so you can 'map' the remote site (IP) as if being served by your normal server.
Also apaches rewriting module can make use of that module by using the [P] flag in a RewriteRule.
Be sure you have a copy of that site on the different server, preverally with the same database, so you don't get in trouble with i.e. order numbers or user logins between http and https. The certificate server must be the web server for your SSL provided web content.
Take a look here foor further informations. "Google Search Result"
I've been trying unsuccessfully to use a UCC multiple site certificate to provide SSL to my subdomains (for example, I have the certificate set for www.example.com and I would like to bind it to sub1.example.com and sub2.example.com). These sites are all on the same ip.
The problem I'm having is that when I try to bind the certificate to the subdomains, strange behavior begins to happen. When attempting to use https with the subdomains, they redirect to the root site in some strange way (the URL reads https://sub1.example.com but displays the page https://www.example.com).
I've tried multiple solutions both through the IIS manager and the command line (appcmd in inetsrv), but nothing seems to be working. Any insight into the problem?
The IIS GUI manager is not able to configure these types of certificates properly, but command line should:
appcmd set site /site.name:{SITE NAME AS PER IIS GUI} /+bindings.[protocol='https',bindingInformation='{IP ADDRESS TO BIND TO}:443:{HOSTHEADER OF WEBSITE}']
http://sslnews.blogspot.com/2010/11/requiring-multi-domains-to-wildcard-ssl.html
So I have this project I took over from another guy - whom I can't consult with unfortunately. And I have no experience in SSL.
Basically there's this sharepoint web-app which has been setup to use SSL - and everything's working great. I see in the central admin page, that there are two zones to the web-app (standard and internet). In IIS there are 2 web sites containing to this sharepoint site.
One has the port value TCP 0 and SSL port 443, the other a TCP 80 with a redirect to the SSL website. So far so good.
Now I need to extend this website with a forms-authenticated extranet. How do I go about this?
I did, what I would do with a normal sharepoint website, and first extended the web-app from central admin, remembered to set the zone to extranet, and checked "use SSL". (port 1580)
I went into the web-config file in the virtual directory, and set up the forms-stuff (connection string, providers, etc.).
But then I was stumped as to how to actually access this extranet. I couldn't access it by doing:
http://site.com:1580
or
https://site.com:1580
And I tried just changing the existing redirect to the virtual directory of the extranet - no dice. I know this is simple, so there must be someone who can explain it to me, as if I was a child :D
My guess is that IIS does not know about your 1580 port.
Go into IIS manager, into the new extended web site, and check that the 1580 port has been mapped to it. Check that the SSL port has been mapped too. And don't forget to add the certificate.