Xampp port not working - xampp

I've got xampp installed on ubuntu. The port which I'm using is 3000. Let's say that my IP address is 123.123.123.123
When from another device I'm checking port 3000 for page 123.123.123.123 it's saying it is open.
When I'm opening page 123.123.123.123:3000 on my computer it's working. However when I'm opening 123.123.123.123:3000 on another device it's not working.
How is it possible? (The port is open)
*it looks like client is being redirected to localhost.

Let's say you are running Xampp server (apache) on port 8000. In this case, your local server access address would be localhost:8000/ or 127.0.0.1:8000/
Let us consider your ip address to be 123.123.123.12. So in your LAN network, the server access address would be 123.123.123.12:8000/. So the address you have used will work in case of devices connected in a LAN network.

Related

Accessing localhost Xampp from Internet

So, localhost is working
static ip is assigned and port forwarded to 80
localhost and port forwarding
But I still cannot access from other computer Firewall is disabled and ive tried myipaddress,myipaddress:80 and myipaddress:8080 as well and when I type my ip router modem static ip (192.168.10.100) I do get redirected to localhost.
can someone help me understand what im doing wrong
firewall and remote desktop out of local network

remote connect to xampp website(v3.2.2)

I try to connect to my computer xampp website from other computer.
I got my IV4 IP, it works from local but not work from other computer.
my xampp version is v3.2.2
seems like there's no version available right now.
how can I set for it?
thanks for looking.
on the LAN line, most routers allow any connections between peers, but I think you're trying to connect from outside that WiFi/router, yes?
If so, you need to get the public IP of the host computer running xampp (Google 'what is my ip'), then you'll need to port forward your local ip (192.168.1. something) and the port of xampp by going into your router settings. Port forwarding basically tells your router that outside connections should be allowed if they're using that IP and port. You'll then use the public IP and port in your browser from any device to see the website.

Why does HTTPS break my hosts file redirection?

There is a machine (let's call it Machine) with a hostname in my local network. If I go to abc.def.com, my DNS service resolves Machine's external IP and connects me successfully with https://. I've added a hosts file entry so that local.abc.def.com resolves to Machine's local, internal IP.
However, using https://local.abc.def.com breaks everything. I get ERR_CONNECTION_REFUSED in Chrome and This page can't be displayed in Internet Explorer. If I replace https:// with http://, it works again. What's going on?
I assume, for your abc.def.com machine you have https redirect configured with 443 port as well.
Based on description above your application/web server you are using
is not listening port 443 or there is a firewall rejecting your connection.

local host connection in same network

I am trying to connect to my localhost from another computer. I have changed the host files to add the following at the end of the file: 127.0.0.1 privacy.local
And in my httpd-vhosts, I've added the following: DocumentRoot "/xampp/htdocs/app/" ServerName privacy.local
On my computer, I able able to access my website using privacy.local and my IP address. However, when I try to access this from my other computer, it does not work. I have also edited the host file for the other computer with my IP address and the servername.
Does anyone know why and how to fix this problem?
I am using xampp - apache.
There is nothing like a localhost in a network. You connect a host at a network adapter. The localhost is a virtual adapter to allow connections at one host without specifying the IP address of a network card. Each host has it's own localhost.
You must use the IP address of the adapter that is used to connect to the network, usually the one and only network card.
If you have DNS support you should use the host name instead of the IP address, because the IP address can change if it's assigned by DHCP.

Do we have to buy a domain to serve Bugzilla?

I tried putting my IP from whatismyip.com in the urlbase of Bugzilla but it did not work. I wasn't able to create a new account for my team mate, and he wasnt able to access the server by typing the my ip address in his browse. And surely, when I connect again, my IP address will change. Do we have to buy a www address to host Bugzilla?
You can setup a dynamic dns service, for example via http://www.dyndns.com or http://www.no-ip.com or http://freedns.afraid.org to solve the changing ip problem without buying a domain (or buying a domain as well, but it's not a requirement).
But the real problem is that your team mate cannot access the server via the current IP address which points to either a misconfiguration of the webserver (listening only on localhost?), to a firewall in between, or most likely, that port forwarding isn't set up in your router for requests coming to your external IP address to be forwarded to the machine where you have Bugzilla set up. Additionally, you must set the urlbase to your local IP address, not to the external IP address, as blak3r says.
Check http://www.portforward.com for instructions on how to do port forwarding. But don't forget that everything mentioned has to be working:
Web server listening to outside requests: This can be tested from the same internal network via the local network IP address (what you see typing in a command line console ipconfig in Windows and ifconfig in Linux). If you can connect from a different machine on the same network via the local IP address, this is solved.
Firewalls (in router and the webserver machine) accepting connections to the web server port: For firewalls in the web server, the same test as above covers it.
Port forwarding so the router forwards the requests received on the web server port to the web server machine: This gets tested in the same way as firewalls in the router, that is, you must have your friend (or yourself from the house of your friend) try to connect to the dyn dns name set up or to the external IP as reported by whatsmyip.org.
This is all assuming your test mate is not on your same network, if he is, just using the local IP address (shown via ipconfig or ifconfig) instead of the external IP address and making sure the first step is covered (web server listening to outside requests) should be enough and nothing else is needed!
You most likely do not have your port 80 forwarded to your machine which is the reason he cannot connect when using the IP that was returned from whatismyip.com.
Assuming you're on a windows box... do
Start->Run->cmd then type
ipconfig
If your address starts with 192...* or 10...* this is your Local Area Network (LAN) IP. If this is the case, then your isp provided you with a router. Look for a setting called port forwarding or "application setting" which allows you to forward all incoming traffic on your router to a particular IP address. Go into your router's configuration settings and make sure port 80 (and maybe 443 if you're using ssl are forwarded to your local ip).
The other problem you mentioned is you do not have a static IP. This is a common problem and no you do not need to buy an address. There are several sites which can provide you a free dynamic dns host. Try no-ip.org.

Resources