Hi everyone,
I have a vagrantbox (lucid64) with a legacy Zend web application, I want to 
being able to debug it remotely from host(windows7) using X-Debug.
this is the *Vagrantfile*:

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

    # Vagrantfile API/syntax version. Don't touch unless you know what 
you're doing!
    VAGRANTFILE_API_VERSION = "2"

    Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
      # All Vagrant configuration is done here. The most common 
configuration
      # options are documented and commented below. For a complete 
reference,
      # please see the online documentation at vagrantup.com.

      # Every Vagrant virtual environment requires a box to build off of.
      config.vm.box = "lucid64"

      # The url from where the 'config.vm.box' box will be fetched if it
      # doesn't already exist on the user's system.
      config.vm.box_url = "http://files.vagrantup.com/lucid64.box";

      # 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: 8060
      config.vm.network "forwarded_port", guest: 9000, host: 11000
      config.vm.network "forwarded_port", guest: 3306, host: 11306


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

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

      # If true, then any SSH connections made will enable agent forwarding.
      # Default value: false
      # config.ssh.forward_agent = true

      # 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 "", "/home/cari", id: "vagrant-root",
        owner: "vagrant",
        group: "www-data",
        mount_options: ["dmode=775,fmode=664"]


      # proxy settings
      config.apt_proxy.http = "http://kite.contextis.co.uk:3128";
      config.apt_proxy.https = "https://kite.contextis.co.uk:3128";
      config.proxy.http     = "http://kite.contextis.co.uk:3128";
      config.proxy.https    = "https://kite.contextis.co.uk:3128";


      # execute ansible script
      config.vm.provision :shell do |sh|
        sh.path = "bootstrap.sh"
      end

      # 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|
      #   # Don't boot with headless mode
      #   vb.gui = true
      #
      #   # Use VBoxManage to customize the VM. For example to change 
memory:
      #   vb.customize ["modifyvm", :id, "--memory", "1024"]
      # end
      #
      # View the documentation for the provider you're using for more
      # information on available options.

      # Enable provisioning with CFEngine. CFEngine Community packages are
      # automatically installed. For example, configure the host as a
      # policy server and optionally a policy file to run:
      #
      # config.vm.provision "cfengine" do |cf|
      #   cf.am_policy_hub = true
      #   # cf.run_file = "motd.cf"
      # end
      #
      # You can also configure and bootstrap a client to an existing
      # policy server:
      #
      # config.vm.provision "cfengine" do |cf|
      #   cf.policy_server_address = "10.0.2.15"
      # end

      # Enable provisioning with Puppet stand alone.  Puppet manifests
      # are contained in a directory path relative to this Vagrantfile.
      # You will need to create the manifests directory and a manifest in
      # the file default.pp in the manifests_path directory.
      #
      # config.vm.provision "puppet" do |puppet|
      #   puppet.manifests_path = "manifests"
      #   puppet.manifest_file  = "site.pp"
      # end

      # Enable provisioning with chef solo, specifying a cookbooks path, 
roles
      # path, and data_bags path (all relative to this Vagrantfile), and 
adding
      # some recipes and/or roles.
      #
      # config.vm.provision "chef_solo" do |chef|
      #   chef.cookbooks_path = "../my-recipes/cookbooks"
      #   chef.roles_path = "../my-recipes/roles"
      #   chef.data_bags_path = "../my-recipes/data_bags"
      #   chef.add_recipe "mysql"
      #   chef.add_role "web"
      #
      #   # You may also specify custom JSON attributes:
      #   chef.json = { :mysql_password => "foo" }
      # end

      # Enable provisioning with chef server, specifying the chef server 
URL,
      # and the path to the validation key (relative to this Vagrantfile).
      #
      # The Opscode Platform uses HTTPS. Substitute your organization for
      # ORGNAME in the URL and validation key.
      #
      # If you have your own Chef Server, use the appropriate URL, which 
may be
      # HTTP instead of HTTPS depending on your configuration. Also change 
the
      # validation key to validation.pem.
      #
      # config.vm.provision "chef_client" do |chef|
      #   chef.chef_server_url = 
"https://api.opscode.com/organizations/ORGNAME";
      #   chef.validation_key_path = "ORGNAME-validator.pem"
      # end
      #
      # If you're using the Opscode platform, your validator client is
      # ORGNAME-validator, replacing ORGNAME with your organization name.
      #
      # If you have your own Chef Server, the default validation client 
name is
      # chef-validator, unless you changed the configuration.
      #
      #   chef.validation_client_name = "ORGNAME-validator"
    end


and this is *xdebug.ini* on the guest machine:

    zend_extension=/usr/lib/php5/20090626/xdebug.so                         
                                                                            
                                                                            
         
    xdebug.default_enable=1                                                 
                                                                            
                                                                            
         
    xdebug.remote_enable=1                                                 
                                                                            
                                                                            
          
    xdebug.remote_log=/tmp/php5-xdebug.log                                 
                                                                            
                                                                            
          
    xdebug.remote_handler=dbgp                                             
                                                                            
                                                                            
          
    xdebug.remote_autostart=1                                               
                                                                            
                                                                            
         
    xdebug.remote_connect_back=1                                           
                                                                            
                                                                            
          
    #xdebug.remote_host=192.168.56.110                                     
                                                                            
                                                                            
          
    xdebug.remote_port=11000                                               
                                                                            
                                                                            
          
    xdebug.remote_autostart=1


seems that the only ports correctly forwarded on host are 80 and 22 
(respectively on 8060 and 2222). 

I can access to the application with `http://localhost:8060/myapp`, but not 
`http://localhost:11000/myapp`. I similarly added a port forwarding to 
default MySQL port (3306 -> 11306), in order to connect from host to remote 
db (guest) using the IDE (NetBeans), but I got the same results.

Anybody that experienced the same problems and have some suggestion on how 
to solve them?

Thanks 

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to