I have three different webroles in my azure solution.
They are all deployed to xyz.cloudapp.net:
webrole 1 at port 81
webrole 2 at port 82
webrole 3 at port 83
For accessing webrole 2, I need url xyz.cloudapp.net:82. I have noticed that the ports in the url get blocked by some firewalls so I want to get rid of the port.
What is the best method to exclude the need for ports in the url?
Take a look at:
http://www.wadewegner.com/2011/02/running-multiple-websites-in-a-windows-azure-web-role/
http://channel9.msdn.com/Shows/Cloud+Cover/Cloud-Cover-Episode-37-Multiple-Websites-in-a-Web-Role
You should be able to do it with host headers and CNAME mappings. But not sure if you can with the cloudapp.net URL.
A couple of options. The easiest way is to change your web roles so they're each have their own service/deployment. This would mean that you could run them all on port 80 and they'd have their own url e.g. xyz.cloudapp.net, xyztwo.cloudapp.net, xyzthree.cloudapp.net. It has the side effect that it is easier to deploy each of them separately.
If you have a domain that you're using for your app e.g. xzy.com then you could setup all three of the web roles to be sites under one web role using host headers to distinguish between them. Then you could add CNAMEs for www.xyz.com, two.xyz.com, three.xyz.com all to point to xyz.cloudapp.net.
Actually you can also use a single web role with multiple instances. Then the work load will be evenly distributed to those instances. If you have a single code base, the best choice is to use a single web role with multiple instances. They can use a single port 80 on the load balancer. If you have different requirements for different applications, then please multiple roles. In this case you can either host them in different hosted services (so they use different domain names but can use the same port), or host them in the same hosted service as knighpfhor pointed out.
Best Regards,
Ming Xu.
Related
i have a server that has a common dns and hosts multiple containers of different applications but the problem here for each domain name for an application, any app on the server can be accessed with the right port number. i have an internship management system and hospital management system on a single server with the respective domains; ims.ius.ca.com and hms.ius.ca.com where the common dns is "ius.ca.com". These two application have different port numbers 2301 and 2401 respectively. However, when a user keys hms.ius.ca.com:2301 the internship management system application is accessed instead of the hospital management. How do I resolve this conflict.
I agree with #Martheen The common solution for this problem is to have a reverse proxy in front of your applications (docker applications). You could use Nginx or HAProxy as reverse proxy.
This is my first VPS, so I am pretty new to administrating my own box. I already have experience with a managed web server, registrars, DNS settings, etc. The basics. Now I'd like to take it a step further and manage my own VPS to run multiple services for different business and private projects.
So far I got an VPS from Contabo, updated the system, set up a new user with sudo rights, secured the root user, configured Ufw, installed Nginx with server blocks for two domains and created SSL certificates for one domain using Certbot.
Before I go on with setting up my VPS, I'd like to verify my approach for hosting multiple services for multiple domains makes sense and is a good way to go.
My goal is to host the following services on my VPS. Some of them will be used by all projects some only by a single one:
static website hosting
dynamic website hosting with a lightweight CMS
send and receive emails
Nextcloud/Owncloud
Ghost blog
My current approach is to run all services except for Nginx and the mail server with Docker. Using Nginx as proxy to the services encapsulated in Docker.
Is this an overkill or a valid way to go forward in order to keep the system nice and clean? Since I am new to all of this, I am unsure if I also could run all of the services without using Docker but still be able to serve the different projects on different domains without messing up the system.
Furthermore, I'd like to make sure, that access to the services and the stored data is properly separated between the different tenants (projects). And of course ideally the admin of the services is kind of manageable.
I have been looking for the answer to this but unable to find it thus far.
I have an Azure Windows VM with 3 Websites on it. I have managed to configure one domain to point at the IP Address of the Server (A Record) but when I try to point domains to the other two sites, I cannot specify the port number.
How would I go about getting additional custom domains to point at different ports on my VM?
Thanks! Tom
You cannot map different domains to ports.
What you can do, is map domains to specific sites on IIS and have them listen to that specific hostname. Godaddy has a guide on how to do that here
Please tell me the difference between "someSite.com/something" and "something.someSite.com". Are they equivalent? As an amteur programmer, I know how to do the former. I think that I may need to learn network administration to be able to do the latter.
It's usually referred to as a subdomain. This is the over simplified version:
You have a DNS server that converts the domain to an IP. That DNS server also handles subdomains. usually www is synonymous with the base domain itself. You can have more subdomains also, like sub.domain.something.someSite.com/something
You can make them resolve to the same or different IPs, depending on their purpose.
Even if they resolve to the same IP, the web server at that IP receives a request that includes the original domain name. So on that same IP, the server can give different responses for each domain. This is usually the case with small hosting packages, as they can have thousands of domains on a single IP and they all serve up different websites from different clients.
someSite.com/something is from technical point of view a file on the server, while something.someSite.com is a subdomain, which could link to a completely different webserver.
In most cases, the two variants does give you the identical content, because both of them are server-side linked to the same page.
I have a scenario where I have many domains (could be hundreds) pointing to my one web application for example
site1.com
site2.com
site3.com
.... etc
All point to my single web app, this app will be in a shared hosting environment.
The only way I can think of configuring these bindings in IIS is to send my shared hosting company an email every time I need a new binding. Is there a better way? for example some how sending all host headers to my site? How do I do that?
You probably need your own IP address to do this. Then you could just not specify a Host name in your binding:
You will need to specify your IP in the binding though.
This means that as long as your DNS points all sites to your IP, then your site should respond.