How to set up OpenSSL on Wamp with IIS? - apache

I installed openssl on my Wamp Server following the instructions found at How to install: OpenSSL + WAMP. I have my setup in my http.conf file to currently listen to port 8080 in order to accommodate running Wamp along side IIS.
ServerName localhost:8080
However, I cannot get my wamp server to run after I edit the httpd-ssl.conf file according to the instructions.
So my question is how do I run openSSL on Wamp along side IIS?

Running 2 webserverse on the same server needs to have either different ports or differnet IPs.
You took the road using a different Port which is working but then you need to call your server with
https://localhost:8080/

Related

Run Apache2 server and XAMPP on same machine (Ubuntu)

I have XAMPP installed on my machine. Additionally, I have also installed apache2 as a stand-alone web server. How do I run both on the server independently?
You just have to make sure they listen to different ports.
XAMPP:
Listen 80
APACHE2:
Listen 90

How to enable Apache SSL Reverse Proxy on HTTP application

I've been having problems attempting to implement a reverse SSL proxy on Apache for an HTTP application on Ubuntu 14.04. As a baseline, the application works fine when I access it via port 8000 in the browser normally. For all intents and purposes, let's say the IP of my app is 192.141.56.11 (I do not have a domain name yet). The application runs with HTTP Basic Auth, I don't know if it's relevant. Basically I'm fishing for some glaring error here and would be grateful if you could help me out. Here is a log of my process:
I created my SSL cert and key and put them in the following locations:
/etc/apache/ssl/apache.crt (I performed chmod 644 here)
/etc/apache/ssl/apache.key (I performed chmod 400 here)
I then installed:
apt-get install apache2
a2enmod proxy
a2enmod ssl
a2enmod proxy_http
I then disabled the default config with:
a2dissite 000-default
I created the file "/etc/apache2/sites-available/redirect.conf"
I then created the file "/etc/apache2/sites-available/redirect.conf" and copied the text below:
<VirtualHost *:80>
Redirect "/" "https://192.141.56.11"
</VirtualHost>
After, I created the file "/etc/apache2/sites-available/reverse_proxy.conf" and copied below:
<VirtualHost *:443>
SSLEngine On
SSLCertificateFile /etc/apache/ssl/apache.crt
SSLCertificateKeyFile /etc/apache/ssl/apache.key
ProxyPass / http://127.0.0.1:8000/
ProxyPassReverse / http://127.0.0.1:8000/
and did:
service apache2 restart
I now attempt to access the UI of the application on another machine in the Chrome browser. When trying:
https://192.141.56.11
I get a general SSL connection error.
However, trying
http://192.141.56.11:8000
gives me the application, as if none of my config changed anything. However,
192.141.56.11:80
gives me an "Index Of" page with an html folder that says "Apache/2.4.7 (Ubuntu) Server at 192.141.56.11 Port 80"
192.141.56.11:443
gives me the same result except with "Apache/2.4.7 (Ubuntu) Server at 192.141.56.11 Port 443"
I've tried all manners of configurations but can't get what I want -- any ideas here?
EDIT: I tried https[:]//192.141.56.11 and got a more specific SSL error:
received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)
EDIT2: After running apache, I get this warning;
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
I suppose this is fine as I am using an IP and not a domain name.
EDIT3: It turns out I needed to do:
a2ensite reverse_proxy.conf.
Now https[:]//192.141.56.11 works but defaults to an apache page. working on this.
EDIT4: I had to do
a2dissite default-ssl.conf
Now It actually redirects to the app on https[:]//192.141.56.11!! But I can still access the app via port 8000, which is bad {still working on}
EDIT5: IN the end, I couldn't figure out how to block access to the original app via port 8000 on Apache. Instead, I just implemented iptables on the server so that it can only be accessed via HTTPS. This is probably not the correct method. but all I could think of.

Apache: You don't have permission to access / on this server

Just installed WAMP on a Windows 7 machine.
When I go to localhost / from the localhost, everything works. But when I try to go to the machine from another computer on the local network, I get the following error message:
Forbidden
You don't have permission to access / on this server.
Apache/2.4.9 (Win64) PHP/5.5.12 Server at 192.168.1.13 Port 80
How do I solve this?
See the below question. You have to allow access through port 80 to your Apache server in httpd.conf by making sure you have Listen *:80
How to access site running apache server over lan without internet connection
An additional resource with items to do when you install a fresh copy of WAMP
http://forum.wampserver.com/read.php?2,119754,119754
Click on wamp icon > Apache > Apache modules > rewrite module(enable this module)

Problems with Apache Tomcat and Wamp

this is probably a noob problem but I can't get this to work. The Apache on wamp is currently on Listen 8080 because the regular localhost wouldn't work. However when I turn on Tomcat it is also on 8080 which is conflicting with wamp. I am connecting to Tomcat via Eclipse plugin. With Tomcat on I can't get into phpmyadmin on wamp.
Apache's httpd.conf in wamp is set to:
Listen 8080
ServerName localhost:80
Only with this setting I can get wamp to work.
localhost:8080 will work and 127.0.0.1:8080 works as well. Turning on Tomcat will automatically override wamp's settings. How can I get wamp to just be a regular localhost address and not have it take an 8080 port where Tomcat is sitting on?
try to change the port tomcat is using.
Go to conf folder in tomcat installation directory
e.g. C:\Tomcat 6.0\conf\
Edit following tag in server.xml file
Change the port=8080 value to port=80
Save file.
or another solution is , you can change your wamp port from 8080 to any other one...

How can I get Apache HTTP Server 2.2 and IIS 5.1 to both work on my localhost?

I figured the easiest thing to do was to just change the port number that Apache listens to, but I still can't get it to start back up after installing IIS. My IIS currently serves up pages correctly at http://localhost:80. I have several PHP projects, and here are the basics of how ports are configured in my httpd.conf:
Listen 81
# Begin listening for virtual hosts.
NameVirtualHost *:81
<VirtualHost *:81>
# virtual.myvirtualdomain.com virtual host.
ServerAdmin webmaster#virtual.myvirtualdomain.com
DocumentRoot "c:/Development/HTTPServer_WWW/virtual.myvirtualdomain.com/www"
ServerName virtual.myvirtualdomain.com
ErrorLog "c:/Development/HTTPServer_WWW/virtual.myvirtualdomain.com/logs/log"
<Directory "c:/Development/HTTPServer_WWW/virtual.myvirtualdomain.com/www">
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
Then in my Windows hosts file I have an entry like this:
127.0.0.1 virtual.myvirtualdomain.com
I have several of these virtual domains setup, all running locally for numerous PHP projects I'm working on currently. This was all working correctly on port 80, but then I installed IIS 5.1, and the service no longer starts up. I did some research, and they can't both be running on the same port. I changed it so Apache looks to port 81 now, but it still will not start.
EDIT:
So, I uninstalled IIS, and now I can't get Apache HTTP Server to startup at all still. I changed all of the settings back to port 80, and it is still failing.
Stop the service, then run Apache from the command line. It will show you the errors occuring during start up.
I did what Haarsma suggested, and it turns out that I had removed a virtual directory, and so Apache couldn't find it (thus not starting). Apparently it had nothing to do with the ports at all, and was my dumb mistake. I reinstalled IIS, changed my config for Apache to listen on port 81, and it works!
Stop the iis server and see if apache starts.
In command line, run:
netstat -ano
this will tell you which process ID runs on which port.
Disable windows firewall
It's very strange! I have IIS 6.0 and Apache 2.2 working together correctly on my Windows Server 2003. IIS on port 80, Apache on port 8081, both services set to run automatically.