Wordpress ile ubuntu VM, beklenmedik bir şekilde yönlendiriyor (80 - 8080 arası bağlantı noktası iletiliyor mu?)

Question

Windows 10 ana bilgisayarında çalışan bir Ubuntu 14 VM var. Ben ana makinede benim tarayıcıda

127.0.0.1:8080

ziyaret ettiğinizde ben varsayılan nginx sayfasını görebilirsiniz benim Vagrantfile içinde nginx ve

config.vm.network "forwarded_port", guest: 80, host: 8080 

kullanarak yüklemiş olduğunuz

. o kadar iyi çalıştı http://127.0.0.1:8080/aqua/

ve wordpress site olarak görünür, böylece ben bir klasörde wordpress yüklü olduğu çalışma ile

, Windows 10

yılında http://127.0.0.1:8080/aqua/ adrese Ama garip bir şeye görülebilir Sanal makinemde olur. Sunucunun kökünü sorun olmadan uyandırabilirim.

wget localhost/ 
--2016-03-23 21:30:54-- http://localhost/ 
Resolving localhost (localhost)... 127.0.0.1 
Connecting to localhost (localhost)|127.0.0.1|:80... connected. 
HTTP request sent, awaiting response... 200 OK 
Length: 12 [text/html] 
Saving to: ‘index.html.3’ 

100%[======================================>] 12   --.-K/s in 0s 

2016-03-23 21:30:54 (295 KB/s) - ‘index.html.3’ saved [12/12] 

Ben wordpress ben port 8080 konuk ubuntu makinede olan bu wget ait hem yönlendirilmiş olsun

wget localhost/aqua 
--2016-03-23 21:32:28-- http://localhost/aqua 
Resolving localhost (localhost)... 127.0.0.1 
Connecting to localhost (localhost)|127.0.0.1|:80... connected. 
HTTP request sent, awaiting response... 301 Moved Permanently 
Location: http://localhost/aqua/ [following] 
--2016-03-23 21:32:28-- http://localhost/aqua/ 
Reusing existing connection to localhost:80. 
HTTP request sent, awaiting response... 301 Moved Permanently 
Location: http://localhost:8080/aqua/ [following] 
--2016-03-23 21:32:28-- http://localhost:8080/aqua/ 
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused. 
Resolving localhost (localhost)... 127.0.0.1 
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused. 

yüklü 'aqua' alt klasörü wget edin.

Bu, Vagrant dosyamın bir belirtisi olabilir mi?

# -*- mode: ruby -*- 
# vi: set ft=ruby : 

# All Vagrant configuration is done below. The "2" in Vagrant.configure 
# configures the configuration version (we support older styles for 
# backwards compatibility). Please don't change it unless you know what 
# you're doing. 
Vagrant.configure(2) do |config| 
    # The most common configuration options are documented and commented below. 
    # For a complete reference, please see the online documentation at 
    # https://docs.vagrantup.com. 

    # Every Vagrant development environment requires a box. You can search for 
    # boxes at https://atlas.hashicorp.com/search. 
    config.vm.box = "ubuntu/trusty64" 

    # Disable automatic box update checking. If you disable this, then 
    # boxes will only be checked for updates when the user runs 
    # `vagrant box outdated`. This is not recommended. 
    # config.vm.box_check_update = false 

    # Create a forwarded port mapping which allows access to a specific port 
    # within the machine from a port on the host machine. In the example below, 
    # accessing "localhost:8080" will access port 80 on the guest machine. 
    config.vm.network "forwarded_port", guest: 80, host: 8080 

    # Create a private network, which allows host-only access to the machine 
    # using a specific IP. 
    # config.vm.network "private_network", ip: "192.168.33.10" 

    # Create a public network, which generally matched to bridged network. 
    # Bridged networks make the machine appear as another physical device on 
    # your network. 
    # config.vm.network "public_network" 

    # Share an additional folder to the guest VM. The first argument is 
    # the path on the host to the actual folder. The second argument is 
    # the path on the guest to mount the folder. And the optional third 
    # argument is a set of non-required options. 
    # config.vm.synced_folder "../data", "/vagrant_data" 

    # Provider-specific configuration so you can fine-tune various 
    # backing providers for Vagrant. These expose provider-specific options. 
    # Example for VirtualBox: 
    # 
    # config.vm.provider "virtualbox" do |vb| 
    # # Display the VirtualBox GUI when booting the machine 
    # vb.gui = true 
    # 
    # # Customize the amount of memory on the VM: 
    # vb.memory = "1024" 
    # end 
    # 
    # View the documentation for the provider you are using for more 
    # information on available options. 

    # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies 
    # such as FTP and Heroku are also available. See the documentation at 
    # https://docs.vagrantup.com/v2/push/atlas.html for more information. 
    # config.push.define "atlas" do |push| 
    # push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME" 
    # end 

    # Enable provisioning with a shell script. Additional provisioners such as 
    # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the 
    # documentation for more information about their specific syntax and use. 
    # config.vm.provision "shell", inline: <<-SHELL 
    # sudo apt-get update 
    # sudo apt-get install -y apache2 
    # SHELL 
end 

Misafir makinede bir yönlendirmeye neden olacak hiçbir şey göremiyorum. Wordpress, konuk makinede bir yönlendirmeye neden oluyor ancak siteyi ana makinede hala görebiliyorum.

Answer 1

Benim durumumda bu, wordpress ve onun yeniden yazma kuralları ve wp_config DB tablosundan kaynaklanıyor. site_url ve home satırlarında, muhtemelen, bu beklenmedik davranışa neden olan, belirtilen bağlantı noktası vardır.