I want a project hosted on 192.168.10.18/WAMP to be access from all pcs in LAN using a domain name
it is hosted on port 82
I can access using www.project1.ae:82
but if I put just www.adcspos.ae it is showing me the IIS bcz port 80 is used by IIS.
I can not move it to port it, I want to access it without mentioning port on client side while on server it should be hosted other than port 80.
1- 192.168.10.18/v-hosts
<VirtualHost *:82>
ServerName www.project1.ae
ServerAlias localhost
DocumentRoot "${INSTALL_DIR}/www/project1"
<Directory "${INSTALL_DIR}/www/project1">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
# Require local
Require all granted
</Directory>
</VirtualHost>
2- 192.168.10.18/httpd.conf
Listen 0.0.0.0:82
Listen [::0]:82
3- firewall port 82 allowed
4- Client-PC host file
192.168.10.18 www.project1.ae
Can I mention port here in client host or it should be handled at server.
Related
I have a Docker container running Apache that is currently listening to the port 80.
I am trying to run another website on the same server, using Apache natively this time, also listening to the port 80.
The problem is that I cannot have both applications listening to the same port (Docker and Apache).
Can I set up the server’s native Apache installation to redirect internally certain requests based on the domain name to my Docker container? For instance, Apache would listen to the port 80 and requests to mycontainer.com would be internally transferred to the port 9999 to which Docker would listen.
Yes, you can do that. The first time I wanted to test, this is the way I did and worked with no issue.
We have an Apache container running to port 80, and let us call another domain like mycontainer.com that we want to be accessible on port 80 too but we cannot.
No matter how do you run these containers, I mean by docker run or docker-compose, but the point is they should be in the same network.
Create a network called my_network:
docker network create my_network
I call the first Apache as main and the latter as the_name one.
So now let us run both in the same network:
docker run --name main --network my_network httpd
docker run --name the_name --network my_network another_image
Now you can exec into the the_name container and create a domain.conf file in Apache conf path with below contents:
<VirtualHost *:80>
ServerName mycontainer.com
ProxyPreserveHost On
ProxyPass "/" "http://the_name:9999/"
ProxyPassReverse "/" "http://the_name:9999/"
ProxyRequests Off
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
I Guess it is possible with Apache named virtual host and Proxy Pass.
You can try something like below. Just make sure you enabled apache mod_proxy.
NameVirtualHost *:80
<VirtualHost *:80>
ServerName app-running-in-docker-container.com
ErrorLog "var/log/container_error_log"
CustomLog "var/log/container_access_log" common
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass / http://127.0.0.1:999
ProxyPassReverse / http://127.0.0.1:999
</VirtualHost>
<VirtualHost *:80>
ServerName app-running-natively.com
DocumentRoot /path/to/project/doc/root
ErrorLog "var/log/nativelyapp_error_log"
CustomLog "var/log/nativelyapp_access_log" common
</VirtualHost>
I've WAMP server 2.1 installed on windows 8, and I'm trying to connect through LAN cable.
I've put it online, and changed apache2.conf settings to
<Directory "c:/wamp/www/">
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
But still cannot connect to my server (tried through IP and machine name)
just remove any ip only listen port
now start wamp server and click on its icon and click put online
also make sure firewall is allowing your port 80
on a dedicated server Debian 7, my default domain is www.example.org
I installed a mail server as smtp.example.org on localhost, running fine
I would like to deploy a rails app as a subdomain as : myapp.example.org
I deployed correctly the app, w Capistrano , and added a vhost :
<VirtualHost *:80>
ServerAdmin webmaster#example.org
ServerName myapp.example.org
ServerAlias myapp.example.org
DocumentRoot /var/www/rails/staging/myapp/current/public
<Directory /var/www/rails/staging/myapp/current/public>
AllowOverride All
Options -MultiViews
</Directory>
</VirtualHost>
the I enabled the site and restarted apache and tried to get http://myapp.example.org
but I always get the default site : http://www.example.org
my /etc/host is the following :
127.0.0.1 localhost smtp.example.org
localhost.localdomain localhost smtp
when I perform in the console : apache2ctl -S, I get
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
...
*:80 is a NameVirtualHost
...
port 80 namevhost myapp.example.org (/etc/apache2/sites-enabled/myapp.example.org:1)
what did I missed ?
Found the answer at :
http://shapeshed.com/developing-subdomain-rails-sites-locally/
in the vhost file , I changed :
ServerAlias *.example.com
...
Options +FollowSymlinks +SymLinksIfOwnerMatch
RackEnv staging # or development or production
I have a server running a rails 3.2 application. It has thin server running on port 3000, apache(proxy) server running on 443.
Is it possible that if I try to host another rails application on the same server by creating a folder under /www and make it run on port 3002 or any other and then another apache for proxy on some other port ?
The new rails app that I have created is in Rails 4 with Ruby 2.0
Please guide.
Add another VirtualHost for port 3002
<VirtualHost *:3002>
ServerName your-server-name
DocumentRoot /www/your-second-app-public-folder-path
<Directory /www/your-second-app-public-folder-path>
AllowOverride all
Options -MultiViews
</Directory>
</VirtualHost>
use host virtual host configuration specifying different ports for the same ip
You have multiple domains going to the same IP and also want to serve multiple ports. By defining the ports in the "NameVirtualHost" tag, you can allow this to work. If you try using <VirtualHost name:port> without the NameVirtualHost name:port or you try to use the Listen directive, your configuration will not work.
Refer Running different sites on different ports.
Server configuration
Listen 80
Listen 8080
NameVirtualHost 172.20.30.40:80
NameVirtualHost 172.20.30.40:8080
<VirtualHost 172.20.30.40:80>
ServerName www.example.com
DocumentRoot /www/domain-80
</VirtualHost>
<VirtualHost 172.20.30.40:8080>
ServerName www.example.com
DocumentRoot /www/domain-8080
</VirtualHost>
I'm trying to configure SSL on EC2onrails with no luck. At present I am unable to even telnet into my server at port 443, it simply says trying MY.IP.ADDRESS... and stays there indefinitely. Telnet into 80 works fine.
This was my starting point. I followed the instructions exactly, and because I have a go daddy cert I created this custom default-ssl file so I could add the SSLCertificateChainFile directive:
NameVirtualHost *:443
<VirtualHost *:443>
Include /etc/apache2/sites-available/app.custom
Include /etc/apache2/sites-available/app.common
ErrorLog /mnt/log/apache2/error.log
LogLevel warn
CustomLog /mnt/log/apache2/access.log combined
# see http://httpd.apache.org/docs/2.2/ssl/ssl_intro.html and http://httpd.apache.org/docs/2.2/mod/mod_ssl.html
SSLEngine On
SSLCertificateFile /etc/ec2onrails/ssl/cert/ec2onrails-default.crt
SSLCertificateKeyFile /etc/ec2onrails/ssl/private/ec2onrails-default.key
SSLCertificateChainFile /etc/ec2onrails/ssl/cert/ec2onrails-chain.crt
RequestHeader set X_FORWARDED_PROTO 'https'
ServerName MY_SERVER_NAME
</VirtualHost>
Note that I had to add
ServerName MY_SERVER_NAME
Or else I saw the following warning at apache startup in the error.log file:
[Wed May 27 19:46:20 2009] [warn] RSA server certificate CommonName (CN) ` MY_SERVER_NAME' does NOT match server name!?
I have run cap ec2onrails:server:enable_ssl, apache boots up cleanly, regular access over port 80 works, and apache access logs indicate no request activity to port 443. I know apache is loading my default-ssl config files because if I type gobbledygook in them it complains at startup.
Has anyone else successfully gotten SSL working with EC2onRails? What else can I do to debug this issue? Right now I am using ec2onRails version 0.9.9.1 which is based on a version of Ubuntu.
OK I figured it out. Amazon's EC2 has it's own firewall as part of its "security group" concept. This firewall was blocking port 443.