Looks like localhost is not working. For this example I will use 192.192.92.92 as my ip address!
Starting by the C:\Windows\System32\drivers\etc\host:
#
127.0.0.1 localhost
::1 localhost
IIS binding:
Type: http
IP address: All Unasigned (there is no 127.0.0.1 or localhost in the list)
Port: 80
hostName: -blank-
When I start the server and click browse in ISS it opens the browser with the following error:
The strange thing with this is that it works perfectly fine with a custom host name!
C:\Windows\System32\drivers\etc\host:
#
127.0.0.1 localhost
::1 localhost
192.192.92.92 myCustomHostName.com
IIS binding:
Type: http
IP address: 192.192.92.92
Port: 80
hostName: myCustomHostName.com
My main objective is to figure out how to find a way to run the IIS app on the localhost again. It used to work before, but I think uninstalling APACHEE - XAMPP confused everything in IIS and now there is no 127.0.0.1!
Stuff I have tried and didn't work for me:
Youtube:
Error || PhpMyAdmin || Login AllowNoPassword Error - Solved-
How to Restrict access to the phpMyAdmin by IP Address
https://www.youtube.com/watch?v=BX57ooAulsY
How To Change User Password In phpMyAdmin If You're Locked Out Of Your Site | WP Learning Lab
Error || PhpMyAdmin || Login AllowNoPassword Error - Solved-
access denied for user 'root'#'localhost' (using password yes or no)
SO:
Setting up 'localhost' equivalent bindings with IIS7
Getting error mysqli::real_connect(): (HY000/2002): No such file or directory when i try to access my project on live server
How to change the ip address of phpmyadmin MySQL?
Related
I am using Windows Server 2019 and in IIS 10 I have created a website and I have bound it to both: "localhost" and "mydomain.com" on port 80.
mydomain.com works correctly from any client but on the server only when I call "localhost" it works otherwise I get the following error (when called by domain):
Configure your DNS in your local server to resolve the domain name as localhost
On clients, your request domain.com is resolved by its configured DNS.
It can be on public DNS (internet) or private ones (company, intranet).
From the server domain.com, do you have access to the same DNS than your clients use ?
If not, either configure additional DNS servers :
https://serverspace.io/support/help/configuring-a-dns-server-on-windows-server-2012-or-later/
or you could edit you Host file of mydomain.com (local DNS):
C:\Windows\System32\drivers\etc\hosts
It may look like that :
127.0.0.1 localhost
127.0.1.1 mydomain.com
# and existing settings
I am trying setup a loacl domain on my pc for that I have apache server install I want to open my rails s inside this abcd.com instead of 127.0.0.1:3000. In my host I have changed host file like this:
127.0.0.1 localhost
127.0.0.1 abcd.com
But when I am trying to open abcd.com with this command I am getting this message:
Address already in use - bind(2) for "127.0.0.1" port 80 (Errno::EADDRINUSE)
When I stop apache it works on localhost any help
You need to write all hostnames behind the ip like this :
127.0.0.1 localhost abcd.com
All,
I have MAMP Pro 3.4. I have a virtual host 'mysite.local' running on the standard MAMP port 8888. I'm running Apache/MySQL server as my user (not WWW). Everything works.
But when I change the host name in MAMP to anything else (like 'localmysite', restart the servers and reload the site in Chrome, I get:
"Access Denied (policy_denied) Your system policy has denied access to the requested URL."
When I view the Hosts file from MAMP, it looks like MAMP correctly updated the host file:
127.0.0.1 localmysite # MAMP PRO - Do NOT remove this entry!
::1 localmysite # MAMP PRO - Do NOT remove this entry!
But it simply doesn't work. When I change the host name back to 'mysite.local' and restart the servers, it works again. What is wrong and how do I fix it so I can change the host name?
Thanks.
OK, after a lot of trial and error I figured out what was going on. It was a proxy server problem. My machine is connected to a corporate proxy server, and that server was attempting to interpret "localmysite" and failing to allow it.
In Chrome, I simply had to go to:
Settings->Advanced->Change proxy settings->Bypass proxy settings for these Hosts & Domains.
Then add "localmysite" to the list of sites that will bypass the proxy server.
My Problem:
I can only access my sites through port 8000, but not 80, which makes me think it is not redirecting 80 to 8000 as it says it should be. I want to simply type local.kujif.com into my browser and it loads the site, which I read was port 80 by default. I am using curl to check it and it returns:
curl 'http://local.kujif.com'
curl: (7) Failed connect to local.kujif.com:80; No error
However if I add :8000 to the url then it works; it returns my index.php which simply prints 'test':
curl 'http://local.kujif.com:8000'
test
My Details:
I am using Laravel Homestead and Vagrant with Oracle VM VirtualBox.
In the Homestead.rb it has the port forwarding. I haven't edited it at all:
config.vm.network "forwarded_port", guest: 80, host: 8000
config.vm.network "forwarded_port", guest: 3306, host: 33060
config.vm.network "forwarded_port", guest: 5432, host: 54320
I also have Microsoft IIS installed for my work stuff. I obviously stop that service whenever I need vagrant to use the localhost.
"vagrant up" shows:
My Homestead.yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
authorize: /Users/Tyler/.ssh/id_rsa.pub
keys:
- /Users/Tyler/.ssh/id_rsa
folders:
- map: C:\DEV\Linux
to: /var/www/
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
- map: local.kujif.com
to: /var/www/kujif
variables:
- key: APP_ENV
value: local
You should continue to use ports above 1024 since they are non-privileged ports, BUT if you do want you can run as port 80 on the Homestead VM, as long as you don't have anything holding on to that port on the host machine. Just tried it and it worked, with a few gotchas. First, you change that line in the .rb file from:
config.vm.network "forwarded_port", guest: 80, host: 8000
to
config.vm.network "forwarded_port", guest: 80, host: 80
When you fire your VM up after saving you will get a warning from vagrant:
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
default: 80 => 80 (adapter 1)
But it worked for me. Now, to actually get to the VM I had to use it's private IP instead of the localhost name:
http://192.168.10.10/
But sure enough my site was there and everything was working. If you decide to keep it that was you can add that IP address to your hosts file to give it a nice short name.
Hope this helps.
I see there is an accepted answer, but this alternative may also help someone.
If I understand correctly you really dislike the port "8000"!
Have you tried setting a private network?
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
/*other config stuff here */
config.vm.network :private_network, ip: "192.168.33.22"
This way you can simply use that IP address, or edit you hosts file to map the local domain to that IP.
Take a look at the Vagrant docs:Vagrant Private Networks
BTW, You shouldn't need to shutdown your IIS local server as that is running on a totally different IP range. I have Apache running locally while also accessing the VM server. This allows you to use tools like composer (to pull in laravel) on your local if needed.
I'm not sure what the confusion is - this is the way it's supposed to work.
The web server on the VM listens on port 80. Vagrant/VirtualBox forwards that port from 80 (on the VM) to 8000 (on localhost) so that you can access the site at http://localhost:8000.
Port 80 on the VM's domain name is not going to be available - that domain name probably resolves to localhost.
Try the following: dig local.kujif.com (or nslookup or even ping - I don't know what tools are available on Windows) to find out what IP address that name is resolving to. You will probably find that it's 127.0.0.1 (localhost).
You could try using the IP address set in the homestead file instead: http://192.168.10.10/ - this might work, but it will depend on how networking is configured in the VM.
Ideally, you need to set networking to "bridged" in the VM - this will make the VM look (to your network) like any other device on the network. Other networking options in the VM (sorry, I'm not familiar with the options in VirtualBox) will set the VM up with its own network that is not accessible outside the VM - this is why port forwarding is used to expose network services on the VM.
You can disable the default port forwarding completely by adding the following to the Homestead.yaml:
default_ports: false
Or configure however you like by adding something like:
ports:
- send: 80
to: 80
I currently have two websites hosted on my IIS 7 server. Each website has its own host name but shares the same port (80).
Everything works great locally to access the two sites:
Site #1: http://localhost/ -> http://arcadiastudio.ch
Site #2: http://webService.ch/
But from the outside I cannot reach my second website hosted on the same port. I do not know what to put in the URL:
Site #2: http://arcadiastudio.ch/??
Here is what I have in my host file:
127.0.0.1 localhost
127.0.0.1 webService.ch
::1 localhost
This should be very simple. All you need to do is to have each hostname specified in your hosts file. In your case, your host file on your local PC should look like:
127.0.0.1 localhost
127.0.0.1 webService.ch
::1 localhost
127.0.0.1 arcadiastudio.ch
And the hosts file on your remote PC should look like:
127.0.0.1 localhost
<remote_ip> webService.ch
::1 localhost
<remote_ip> arcadiastudio.ch
Obviously, you need to change <remote_ip> to the IP address of your web-server.
Also, if you want to allow any remote PC to connect, you will need to register your domain names for DNS - you can't edit every host file in the world!!