带有wordpress安装的ubuntu虚拟机意外重定向（端口转发80到8080？）

我有一个运行在Windows10主机上的Ubuntu14VM

我已经安装了nginx并使用

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

在我的文件中，我可以在访问时看到默认的nginx页面

127.0.0.1:8080在主机上的我的浏览器中

通过这项工作，我将wordpress安装在一个文件夹中，这样它就会显示为

这也起到了作用，wordpress站点可以在Windows10中的地址看到

但是在我的虚拟机中发生了一件奇怪的事情。我可以在没有问题的情况下设置服务器的根目录

 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]

如果我打开安装wordpress的“aqua”子文件夹

 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.

我被重定向到端口8080。 这两个wget都在guest-ubuntu机器上

这可能是我流浪的症状吗

    # -*- 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

#-*-模式：ruby-*-
#vi:set ft=ruby:
#所有的流浪配置都在下面完成。Vagrant.configure中的“2”
#配置配置版本（我们支持较旧的
#向后兼容性）。除非你知道什么，否则请不要改变它
#你在干什么。
Vagrant.configure（2）do | config|
#下面对最常见的配置选项进行了说明和评论。
#有关完整的参考资料，请参阅
# https://docs.vagrantup.com.
#每个流浪的开发环境都需要一个盒子。你可以搜索
#盒子在https://atlas.hashicorp.com/search.
config.vm.box=“ubuntu/trusty64”
#禁用自动框更新检查。如果禁用此功能，则
#只有在用户运行时，才会选中复选框进行更新
#“流浪汉盒子过时了”。不建议这样做。
#config.vm.box\u check\u update=false
#创建允许访问特定端口的转发端口映射
#从主机上的端口在计算机内。在下面的例子中，
#访问“localhost:8080”将访问来宾计算机上的端口80。
config.vm.network“forwarded_port”，来宾：80，主机：8080
#创建专用网络，仅允许主机访问计算机
#使用特定的IP。
#config.vm.network“专用_网络”，ip:“192.168.33.10”
#创建一个公共网络，它通常与桥接网络相匹配。
#桥接网络使机器显示为计算机上的另一个物理设备
#你的网络。
#config.vm.network“公共_网络”
#将其他文件夹共享到来宾VM。第一个论点是
#主机上实际文件夹的路径。第二个论点是
#来宾服务器上装载文件夹的路径。还有第三个选项
#参数是一组非必需的选项。
#config.vm.synced_文件夹“./data”，“/vagrant_data”
#提供程序特定的配置，以便您可以微调各种
#为流浪者提供支持。这些公开特定于提供程序的选项。
#VirtualBox的示例：
#
#config.vm.provider“virtualbox”do | vb|
##启动机器时显示VirtualBox GUI
#vb.gui=true
#
##自定义虚拟机上的内存量：
#vb.memory=“1024”
#结束
#
#有关详细信息，请查看您正在使用的提供程序的文档
#关于可用选项的信息。
#为推送到Atlas定义一个流浪推送策略。其他推送策略
#例如FTP和Heroku也可以使用。请参阅位于的文档
# https://docs.vagrantup.com/v2/push/atlas.html 了解更多信息。
#config.push.define“atlas”do | push|
#push.app=“您的\u ATLAS\u用户名/您的\u应用程序\u名称”
#结束
#使用shell脚本启用资源调配。其他供应人，如
#木偶，厨师，Ansible，盐和码头工人也可以。请看
#有关其特定语法和用法的详细信息，请参阅文档。
#config.vm.provision“shell”，内联：根据我的经验，这是由于wordpress及其重写规则和wp_config DB表造成的。
site\u url
和
home
行中可能指定了端口，这导致了此意外行为。
谢谢。事实证明，从windows浏览器安装wordpress意味着wordpress设置将端口作为地址的一部分。谢谢你让我走上了正确的道路。@Declan没问题，很高兴我能帮上忙。如果你的问题已经解决，请记得投票并选择一个被接受的答案。