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?
I am deploying a new mesh app with an Asp.Net API core container image. I am able to successfully deploy and access the API using http://[]:80. I used the Following configuration in gateway yaml file:
http:
- name: BenApiHTTP
port: 80
hosts:
- name: "*"
routes:
- name: benapi
match:
path:
value: "/benapiservice/"
rewrite: "/"
type: Prefix
destination:
applicationName: BenApplication
serviceName: BenApi
endpointName: BenApiListener
Now I want to use my own ssl certificate and wants to enable the same api using https i.e. on port 443. So my questions are:
How to upload the ssl certificate in mesh?
What Yaml updates I have to make in gateway.yaml ?
How to set the FQDN for the url ?
I have VPS running Debian 9 with Keter serving single web application.
I've generated certificates using Create certificate button in Origin Certificates section of Crypto tab.
Then I've edited my keter.yaml:
stanzas:
- type: webapp
exec: ../dist/bin/dummy-name
args: []
hosts:
- dummy-domain.info
ssl:
key: /opt/keter/etc/cert/dummy-domain.info.key
certificate: /opt/keter/etc/cert/dummy-domain.info.pem
There are also a remark:
# Enable to force Keter to redirect to https
# Can be added to any stanza
# requires-secure: true
When I've uploaded new bundle it looks like that things does not work correct. My website can be visited via HTTP (works as expected), and HTTPS, but it cannot load generated CSS and JS files from static (links injected in document have http scheme).
What else should I do to make everything work using secure HTTPS connection?
There are unclear options for keter:
# for all stanzas
requires-secure: true
# stanza based
host: ....
secure: true
Also I have no idea which options should I use on CloudFlare too
SSL type now set to Flexible
Always Use HTTPS is OFF
OK, finally I've done following:
Application's keter.yml
stanzas:
- type: webapp
exec: ../dist/bin/dummy-name
args: []
hosts:
- dummy-domain.info
requires-secure: true
ssl:
key: /opt/keter/etc/cert/dummy-domain.info.key
certificate: /opt/keter/etc/cert/dummy-domain.info.pem
Keter configuration on server keter-config.yaml
root: ..
#
# # Keter can listen on multiple ports for incoming connections. These ports can
# # have HTTPS either enabled or disabled.
listeners:
# HTTP
- host: "*4" # Listen on all IPv4 hosts
port: 80 # Could be used to modify port
# HTTPS
- host: "*4"
port: 443
key: cert/dummy-domain.info.key
certificate: cert/dummy-domain.info.pem
CloudFlare config:
SSL type now set to Full
Always Use HTTPS is ON
Also I've restarted keter service
sudo service keter restart
Now everything work as expected.
All external URLs work on my machine but not on other devices on the same network. In over a year it never really has but now it would be really handy for my workflow.
I have used dev-ip and set the correct IP. I use mamp pro and tried various ports and its defaults (80, 8888). The Ips are correct too.
Using those ports instead of the below yields no results. I think i should of been able to at least access the UI External from another device on the same network but cannot.
Any help appreciated or if any more info would help please let me know!
I have 30+ sites in mamp pro so always use the proxy setting incase i'm working on more than one at a time. Being able to use http://10.50.2.64:3000 on same network machines would be amazing!
[BS] Proxying: http://ggdev.jynk.net.local
[BS] Access URLs:
-----------------------------------
Local: http://localhost:3000
External: http://10.50.2.64:3000
-----------------------------------
UI: http://localhost:3001
UI External: http://10.50.2.64:3001
browserSync (latest version) & gulp settings -
browserSync.init({
files: ['{lib,templates,templates-misc}/**/*.php', '*.php'],
notify: false,
watchTask: true,
open:false,
proxy: config.devUrl,
host: "10.50.2.64",
snippetOptions: {
whitelist: ['/wp-admin/admin-ajax.php'],
blacklist: ['/wp-admin/**']
}
});
Any help appreciated. D.
Type this in your command line to open port 3000/tcp in your machine (Ubuntu):
sudo ufw allow 3000/tcp
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