I have opened a micro instance on AWS with a Windows_Server-2008-R2_SP1-English-64Bit-Base-2013.11.13 (ami-1e53c82e) virtual machine. RDS is open and I have connected with remote desktop connection. Additionally, at initialization I set HTTP (port 80), and HTTPS (port 443) although I do not know how to verify that now. From within the VM I navigated to XAMPP and installed a default installation (minus MySQL). I then navigated to XAMPP control panel V3.2.1 and started Apache. I set a password on XAMPP directory. I set a "Hello World" test txt file in htdoc and that loads in the VM browser. However, when I try to access the pubic IP, my local browser times out.
I think I covered the first three checks on
"xampp configuration in windows server 2008 r2 ec2 instance" post
but not sure how to change the elastic or private IP response if that is relevant.
If you're using VPC, you have to allow both inbound/outbound in the network ACL and inbound for the security group. You probably also have to open the ports in the windows firewall.
Edit: You definitely don't want to disable the firewall altogether. Also, it doesn't matter whether you use public ips from within AWS. And public host names resolve locally anyway.
Related
I installed on VM--->server 2019, and on the server i have configured a Wamp server 3.1.9 version php 7.1, I have access to my project on my server, also i changed my localhost project to domain name and again i access to my project(url with authentication with no problem) its a ticketing system my project
The real problem now is that i can't connect from another pc on my local network from another vm machine
both the server and the client are on the same VMnet(0)
this is my conf file
Problem solved!!
Adding httpd.exe(WAMP Apache) application to firewall, rule application open connections for port 80, And one more rule for MySQL database tcp rule open connections for port 3306!!
I have created a Chat application in Ratchet PHP. It runs fine on local machine using WAMP. I want it to setup on live server.
On my server I have:
PHP Support
SSH access
Port 9000, which is opened for OutBound connections.
Sub-domains
What I don't have:
No port for InBound connections.
No root access in SSH. Say I cannot see/edit iptables
I ran php server.php which gives success message about the server is started and listening at port 9000. But when a HTML page tries to connect it using ws://domain:9000 it runs into error-
Firefox can’t establish a connection to the server at
ws://domain.com:9000/
I googled a lot and it appears that what I need is a port for inbound connections.
But according to this answer the thing I need is PHP support for Ratchet to work on shared hostings. Can anyone explains what I really need and Is there any workaround If it's not availble in the list of things I have on my server.
Basically, No
It is not likely for a shared hosting environment (i.e. Apache with VirtualHost config, PHP, MySQL, and a CPanel interface) to support your websocket application.
For websocket to work, you need to either:
have a port dedicated to websocket in-bound connections; or
have a HTTP/HTTPS server that knows when to upgrade a connection and proxy pass to your websocket application.
The first route requires the server to allow in-bound connection to a certain port number. This is a potential security issue for the hosting provider and, thus, is unlikely for your vendor to grant you that.
The second route requires Apache server have with both mod_proxy and mod_proxy_wstunnel installed and enabled. It also require you to use ProxyPass config, which cannot be overridden by .htaccess configs at all.
So unless your hosting grants you the permission to touch the Apache main configuration (or would apply such change for you), you're pretty hopeless.
Suggestion
To run your own websocket service, you should think about using Virtual Private Server services such as Amazon EC2, DigitalOcean VPS.
I have installed xampp on my local machine as well as Windows Server 2008 and Apache and MySql is running on both.
I created a test application which I am running on my local machine.
http://localhost/example/
I want to test this example application on the server. How can I do this?
adding 192.168.1.11/example/(ip address of the server) gives me 404 - File or directory not found.
You would have to move those files over to the server instance. and make a change in your XAMPP configuration to allow the IP of your local machine to connect to the instance.
Do you have physical access to the server instance? (I.E. VM/SSH, In basement)
This question might be helpful if you are looking to allow an external IP.
httpd-xampp.conf: How to allow access to an external IP besides localhost?
My boss wants me to merge my dev server on to the same server as our live production application.
The problem with this is that the current application is .NET and development is WAMP.
On my local machine this worked fine because I could just tag a port to the URL like :8080 or :81.
But, I have tried to point our testing subdomain to an alternate port, but, I found out this isn't possible with DNS.
How can I successfully leave IIS as the main host (www.domain.com) and serve requests for the subdomain (dev.domain.com) from WAMP?
Since both services are webserver operating on port 80, you simply can't without moving one or another to a different port.
The only "workaround" that comes to mind is to set up a subdomain on IIS with redirect to your WAMP dev server.
What is the best (and easiest) way to set these up on Windows 7? I have tried Xampp and WAMP but all I get after installing them is a blank local host. So I create a php info file using the following code:
<?php
phpinfo();
?>
Put it in the httpdocs folder, call it using http://localhost/info.php and I get a 404 file not found error. Even though I followed the typical install settings.
Are you by any chance running Skype in the background? Skype claims port 80 and port 443 as a firewall workaround. You can disable this in the advanced options -> connection.
This happens to me almost all the time I set up a new PC...
The problem was not with either xampp or wamp. The problem was with the proxy that is installed where I was using the internet. It has blocked access to the localhost. Bypassing the proxy for localhost in Internet options -> Connections -> LAN Settings -> Proxy Server does not fix this for wireless so to access the webserver I have to disconnect from the network to what I need to do and then reconnect.
The web server worked fine when I was on other non proxy networks.