Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a .Net programmer, lately developing a website in Jsp, using Jetty. I use Eclipse and the Maven-Jetty plugin.

I have a virtual private server, which has IIS installed and is serving .NET websites. My domain name (for the Jsp website) redirects to this server.

My question is: How do I connect the domain name to the website in Jetty? Jetty listens to port 8080, and IIS to port 80.

I tried configuring a virtual host in a Jetty configuration file (jetty-web.xml) (followed this manual), the result is: when I open a browser inside my server and navigate to I get to the website. But if I do it externally, I get nothing.

  1. What do I need to configure in order to get to my website?
  2. How do I overcome the 8080 port number? or do I need to redirect my domain name to this port?

Thank You

share|improve this question
  1. It sounds like there is a firewall rule either on your server or upstream that is blocking port 8080. Call your host.

  2. You can't easily. Only one service can bind to any single port. You could get another IP and add it to the server, then tell Jetty to listen on port 80 on that interface and then make an A record for that in your DNS zone, or you could possibly proxy it through IIS depending on what version of IIS. Getting an additional IP is probably the easiest way.

share|improve this answer
1. I added an inbound rule in the firewall to allow HTTP traffic on port 8080, but it doesn't solve the problem. I still get nothing when I navigate to mydomainname:8080 2. I don't care if Jetty will continue to listen on port 8080, but I want my users to navigate to my domain name and get there, do I need a new IP for this? Thank you – Yaron Oct 29 '11 at 17:55
@Yaron thn something else is blocking that port. Call your host like I suggested. Also, your second question would require using IIS as proxy for Jetty. If you're unfamiliar with this type of setup, you will need to get another IP like I suggested. My answers to your follow ups were already in my original answer. – MDMarra Oct 29 '11 at 18:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.