Start a new site on port 80 - ruby

I created a sample demo site in ruby on rails and deployed it on the server. Currently I am using phusion passenger as the app server. I can see it by giving address as abc.net:3000. But instead of port 3000, I have to use port 80. I used the following command to start the app server and the site can be accessed as abc.net.
rvmsudo rails server -p 80
I have to configure phusion passenger with nginx. I did it this way. But when I tired to access the site, but I got the nginx index page. The nginx was started on port 80.
How can I use nginx and phusion passenger and start the app on port 80? I tried to start nginx on port 8080 and passenger on port 80, but my nginx is not starting on port 8080.

Related

xampp apache not starting after changing port

enter image description hereApache in XAMPP not working I've searched and I found that I have to change port from 80 to 8080 and from 443 to 4433 and I did this and the same result I've tried another port but no change the same error
note : I'm not have skype
I tried to change port and uninstall XAMPP and reinstall and apache still not working

Port 80 not available on macbook localhost

I am trying to setup my macbook to serve Apache over (localhost) port 80. Here's what I did:
add line pass in proto tcp from any to any port 80 to /etc/pf.conf
reboot
switch off the firewall
make sure that httpd.conf listens to port 80 Listen 80
It is still giving me "connection refused" in the browser, and port 80 is not showing up on the portscan utility.
The configuration seemed to be messed up because I was trying to run httpd through brew. It ended up giving index pages from different directories. I ended up removing httpd from brew and reverting to the built-in apache.
Apache now listens to port 80

Wakanda Server 10 on Amazon EC2, cannot listen for connections on port 8080 or secure port 4433 on all IP addresses

I have installed wakanda server on an Amazon EC2 server running ubuntu by following this utube video: https://www.youtube.com/watch?v=uSQODnB7wRU .
Now the video is for an older version but I have followed along successfully until I actually launch wakanda on the server. This is what I get in the console:
Welcome to Wakanda Server 10 build 10.187175
Publishing "DefaultSolution" solution
The solution's log file will be stored in the "/home/ubuntu/.Wakanda Server/UserCache/Wakanda Server/DefaultSolution-1882/Logs/" folder
The Administration Web Server cannot listen for connections on port 8080 or secure port 4433 on all IP addresses
You can customize the Administration Web Server's ports with the "--admin-port" and "--admin-ssl-port" options
, then when I try to log into it via the browser it says the connection dropped! Any help would be much appreciated, it seams I need to restrict the IP addresses which can access, but how?
Your wakanda server tried and failed to listen on 8080 and/or 4433
Check the following things:
Are the ports 8080 and/or 4433 used by other processes? (sudo netstat -tapen | grep :8080, if a result is found, then yes another process uses 8080. Check 4433 also)
You may found that wakanda server is already running as a service:
yes you should use this service (create and edit /etc/default/wakanda, add WAKANDA_SOLUTION_AT_STARTUP=your_path and restart with sudo /etc/init.d/wakanda restart)
or to continue starting it manually, stop the service first (sudo /etc/init.d/wakanda stop)
Has the current user the right to listen on those ports? (try running the server with sudo just to check, then use authbind or equivalent)
Can you use alternative ports? (use --admin-port and --admin-ssl-port wakanda server options)
wakanda-server --help will give you the list of options available, especially --solution=VALUE to provide the path to your solution.

Can't access Ruby server on VM from host machine

I have a VM set up running Ubuntu server 14.04. In my VM I have created the following Ruby/Sinatra app:
require 'sinatra'
set :environment, :production
set :bind, '0.0.0.0'
get '/' do
"Hello World!"
end
When I execute this using ruby hello.rb I get the following output:
[2015-03-09 16:58:34] INFO WEBrick 1.3.1
[2015-03-09 16:58:34] INFO ruby 2.1.5 (2014-11-13) [x86_64-linux]
== Sinatra/1.4.5 has taken the stage on 4567 for production with backup from WEBrick
[2015-03-09 16:58:34] INFO WEBrick::HTTPServer#start: pid=2258 port=4567
Everything seems to work fine, but when I try to access localhost:4567 from my host machine (Windows 8.1) I get a GET http://localhost:4567/ net::ERR_CONNECTION_REFUSED error (in Chrome).
If I try to access the server from within my VM (ex, by using wget http://localhost:4567) it works fine.
I also have Apache2.4 running in my VM, which works fine, but I disabled it when trying to access my Ruby server by running sudo service apache2 stop.
What could the problem be? I have no problem running regular Ruby files, and I can access my Ruby/Sinatra app if I use Apache2 with Phusion Passenger. But when I simply run ruby hello.rb I can't access it from my host machine.
localhost refers to your local host, which in the case of Windows is not the same as your Ubuntu instance.
You'll need to connect to your Ubuntu instance IP directly, whatever that is. Usually you can find out with ip addr or ifconfig.
If you need a friendly DNS name you can put in your browser, xip.io provides one.
If you're using Vagrant then you can configure port forwarding so you can still use localhost if you want. Without port forwarding you will not be able to connect indirectly.
I have the network adapter for my VM attached to NAT. I was forwarding ports 443, 22 and 80 to my VM, and accessing my server on those ports works fine. Since I was running the Ruby WEBrick server on the default port 4567, I just had to forward port 4567 from my host machine to my VM as well.
After that change, typing http://localhost:4567 into my web browser served up the content from my Ruby file.

Can't use the port other than port 80 and 8080 on EC2

I have an instance Ubuntu 13 on EC2 of AWS
In that instance, in installed 2 applications on nginx with port 80 and 8080. I have also Tomcat running on port 8888.
I have penned theses port with AWS console -> Securit Group -> Inbound -> Custom TCP rule.
It worked well until last night for all port 80, 8080, 8888.
But this morning, i can't connect to the port 8888. I don't change any thing neither on my instace nor on console of AWS. I verify that wget localhost:8888 work well
Have you an idea to resolve this problem ?
Thank you in advanced.
Tien,

Resources