Xampp - How to find my ip address with version 8.1.6 - sql

I was watching this YouTube demo of connecting xampp to mysqlworkbench. The only issue I'm having is that this video was uploaded last year 2021, which I'm assuming was a different version of xampp where the ip address was visibly there.
However, my version of xampp does not have that and the closest I got was going on the apache web server openconfig file and going above Listen to find some ip address, however, that is failing when I test the connection on mysqlworkbench. Either the ip address given to me is incorrect or something is wrong with mysqlworkbench.
I would like to know however where I can find my ip address with this current version of xampp.

Are you using the local host address which is: 127.0.0.1
You can also type: localhost in the URL bar of your browser.
You should see the XAMMP welcome screen. That information is coming from a folder that you can access from the main "Open Application Folder". Go to "htdocs" and that is where you will put all your webpage files.

Related

How resolve ERR_CONNECTION_REFUSED

Hi guys i'm stuck with my web api. i hosted my api locally on my computer. if i request using localhost e.g http://localhost:85/api/user/getallusers it works fine.
see this image
but if i use the my local ip e.g. http://192.168.43.86:85/api/user/getallusers it returns "ERR_CONNECTION_REFUSED".
see this image using locally assigned ip
see my ipconfig result
any idea? thank you...
From this link,you can see rsplak says When you access localhost, your /etc/hosts file will tell your computer not to look any further and redirects you to your own computer. When you access the local IP adress, your computer will ask the router to fetch the data, and your router will then point back to your computer.
So it means the mapping of localhost maybe wrong in localhost(it maybe 127.0.0.1 by default).
You can change it in C:\WINDOWS\system32\drivers\etc\hosts.Change the IP to your 192.168.43.86.

Use Windows 2016 server with Xampp to host more than 1 website

I have tried all kinds of things, read all answers, and configured the bananas out of it, but I cannot seem to get the following working:
A windows 2016 server with XAMPP, to host more websites than 1.
What have I done:
I have altered the httpd-vhosts.conf as described all over the web with allowing NameVirtualHost, and setting up virtual host with documentroot, servername etc.
I have pointed a domain with the a-record to this server
installed the latest XAMPP release to date
changed the windows hosts file, as described everywhere (127.0.0.1 domainname.com)
What works:
I can get the domain working on my server's browser. When I enter the specific domainname.com it shows the hello world page I made in the specified folder. The domain resolves and shows the page that is in de directory accordingly
Besides that, the localhost of apache is also working, I have 2 sites working, but only on the browser of the server, on the machine itself.
What does not work:
Only 1 thing. when I want to access the domain from any other machine than the server (from outside so to say), it will not work, but when I ping the domain on my home-pc it resolves to the server.
I am at a loss. Been at this for hours, and beginning to question if it is even possible.
Can anyone tell me what I am doing wrong here, or if it is even possible to have more than 1 website to work on XAMPP and resolve form the outside?
Thank you in advance.
It was windows firewall that stopped all inbound connections. I finally figured it out!

err_name_not_resolved Win7 Error

I am facing a strange issue on a single PC, all other PC's I have tried are fine so the problem definitely seems localised to this setup.
Windows 7
Google Chrome Version 48.0.2564.82 m
I have developed a simple website on an Apace web server (Windows Server 2012), and assigned it an internal IP address (1.2.3.4), and internal dns name (MyWebsite.MyDomain).
This website is only available within our company. When I type the URL MyWebsite.MyDomain into any browser I am presented with the correct web page, great. When I type the IP address 1.2.3.4 into any browser I am also presented with the correct web page, great again.
This is the case for every PC I have tried so far, apart from one. Instead I am presented with the following error message;
This web page is not available
ERR_NAME_NOT_RESOLVED
Why would this be?
Things I have tried so far on the local PC;
delete history/cache on local PC
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns
changed to Google public dns (8.8.8.8 / 8.8.4.4)
restart (multiple times)
tried IE and FFOX (same error)
checked hosts file (all looks ok)
The only change I ever made to this individual PC was I installed XAMPP and changed the hosts file (for testing purposes). I have since uninstalled XAMPP and reverted to the original hosts file - could this be the issue? I can't think of any other changes.
I had thought the issue was with my web server setup, but as the web site is accessible from all other PC's it would appear not?
Looks like a re-build may be necessary for this PC, unless somebody can perhaps point me to another suggestion? Any help appreciated.
That machine doesn't happen to have any static ip addressing configured, does it? I'm thinking that perhaps a manual entry for DNS server is conflicting or overriding what DHCP is supposed to be assigning.

Public IP Web Page "Connection Timed Out" When Connected To

Recently, I made a website server on my server PC running Windows 7. I used WampServer, and I configured it as follows:
Download and install WampServer.
Check http://localhost (worked).
Program out the HTML files necessary.
Put it inside of the 'www' directory (the default directory of WampServer for HTML files)
Go to http://localhost to see if it worked (yes, it did). Then right click WAMP notification and "Put online".
Go to my main PC and go to http://[local-ip-of-server-computer] to see if it worked. It did.
Now, I configured the httpd.conf to "Request all granted"
Next, I went on ahead to port forward. My router is Frontier Netgear router.
I went to 192.168.254.254 (Frontier's router addresss) > Firewall Settings > Port Forwarding > Add
I selected "World Wide Web (HTTP)" and "OK".
Then I went to the menu and to "DMZ Host". I enabled my server computer for that.
With my main PC, I went on ahead to my public WAN IP mentioned on the router page. It didn't work.
Whenever I try to load my http://[router-public-wan-ip], Google Chrome gets a "Webpage not avaliable. ERR_CONNECTION_TIMED_OUT"
I have port forwarded on my server PC's Windows Firewall.
My httpd.conf is set to be on port 80. Also, I have changed my ServerName to [local-server-computer-ip]:80.
Can anyone provide any advice? Thanks.
This was my mistake. The solution to this problem is that, well, there was no problem at all. I simply hadn't realized that external IP addresses cannot be accessed by their own servers - one inside of the server LAN has to use the server computer's local private IP address.
I sincerely apologize. Thank you to all who contributed.

User getting default Apache page instead of website - Safari/FF?

I have someone complaining that www.archstl.org (a site I manage) loads fine from his Windows PC, but not on his Mac; and apparently he can't get it anywhere he takes his Mac, either...
I've heard of this happening to one other person, but I can't find an explanation. When they try loading it on their Mac using either Safari or FireFox, they get the default Apache page: "If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page."
I have had him ping www.archstl.org, and it always returns the proper IP address of our server (174.37.22.142), so I don't know what could be going wrong. It seems that our server is sending him the wrong page, plain and simple...?
As it turns out, the dns entry for archstl.org included a self-referring ipv6 address (::), which caused Macs running Apache to go to localhost (ignoring the ipv4 address). Our data center removed the v6 address, and now all is well.