[xdebug-general] Using XDebug in the latest version of PHPStorm, can't connect with the server.

After setting up XDebug for use in PHPStorm, I found that I could not
connect with it. I had my internet hosting company reset the
web-service, but still I was not able to connect, so I ran the Tailored
Installation Instructions at https://xdebug.org/wizard.php and was told:

    Summary

# *Xdebug installed:*2.4.1

    You're already running the latest Xdebug version

# *Server API:*Apache 2.0 Handler
# *Windows:*no
# *Zend Server:*no
# *PHP Version:*5.6.27
# *Zend API nr:*220131226
# *PHP API nr:*20131226
# *Debug Build:*no
# *Thread Safe Build:*no
# *Configuration File Path:*/etc
# *Configuration File:*/etc/php.ini
# *Extensions directory:*/usr/lib64/php/modules

In PHPStorm, the Files/Settings > Languages & Framworks >PHP, clicking
on the info (i) button shows the following, which I've abbreviated.

    *PHP version: *5.6.27

*PHP CLI: */usr/bin/php
*PHP CGI: */usr/bin/php-cgi

*Loaded Configuration File: */etc/php.ini

*Additional .ini files parsed: *
/etc/php.d/15-xdebug.ini
     :
*Debugger extension: *xdebug 2.4.1

*Loaded extensions: *
... xdebug ...

*Configuration options:
*

*PHP Info:*

:
extension_dir /usr/lib64/php/modules
:
xdebug.auto_trace 0
xdebug.cli_color 0
xdebug.collect_assignments 0
xdebug.collect_includes 1
xdebug.collect_params 0
xdebug.collect_return 0
xdebug.collect_vars 0
xdebug.coverage_enable 1
xdebug.default_enable 1
xdebug.dump.COOKIE
xdebug.dump.ENV
xdebug.dump.FILES
xdebug.dump.GET
xdebug.dump.POST
xdebug.dump.REQUEST
xdebug.dump.SERVER
xdebug.dump.SESSION
xdebug.dump_globals 1
xdebug.dump_once 1
xdebug.dump_undefined 0
xdebug.extended_info 1
xdebug.file_link_format
xdebug.force_display_errors 0
xdebug.force_error_reporting 0
xdebug.halt_level 0
xdebug.idekey ronbrown
xdebug.max_nesting_level 256
xdebug.max_stack_frames -1
xdebug.overload_var_dump 2
xdebug.profiler_aggregate 0
xdebug.profiler_append 0
xdebug.profiler_enable 1
xdebug.profiler_enable_trigger 0
xdebug.profiler_enable_trigger_value
xdebug.profiler_output_dir /home/ronbrown/tmp
xdebug.profiler_output_name cachegrind.out.%p
xdebug.remote_addr_header
xdebug.remote_autostart 0
xdebug.remote_connect_back 1
xdebug.remote_cookie_expire_time 3600
xdebug.remote_enable 0
xdebug.remote_handler dbgp
xdebug.remote_host localhost
xdebug.remote_log
xdebug.remote_mode req
xdebug.remote_port 9000
xdebug.scream 0
xdebug.show_error_trace 0
xdebug.show_exception_trace 0
xdebug.show_local_vars 0
xdebug.show_mem_delta 0
xdebug.trace_enable_trigger 0
xdebug.trace_enable_trigger_value
xdebug.trace_format 0
xdebug.trace_options 0
xdebug.trace_output_dir /tmp
xdebug.trace_output_name trace.%c
xdebug.var_display_max_children 128
xdebug.var_display_max_data 512
xdebug.var_display_max_depth 3
:
zend.detect_unicode 1
zend.enable_gc 1
zend.multibyte 0
zend.script_encoding
:

This indicates that PHPStorm can communicate with the server, at least
to the extent that it can retrieve this information. Also, the list
shows that the settings, right or wrong, that I put into the
/etc/php.d/15-xdebug.ini file are being loaded into the PHP settings
list, including the xdebug.idekey that PHPStorm needs to communicate
with the XDebug service.

The following show that the Server is configured for the XDebug service:

As does the following:

However, the following shows that the connection is not made:

This may entirely be on the PHPStorm side, but I'm reaching out to you
and JetBrains for help.

Thank you,
Ron Brown

Senior Software Engineer HungryGenius®
5173 Waring Road, #35
San Diego, CA 92120

Direct: (858) 304-8100

ron[@]hungrygenius.com
www.hungrygenius.com

https://twitter.com/hungrygenius
https://www.facebook.com/HungryGenius
http://pinterest.com/hungrygenius/

PRIVACY NOTIFICATION: Email & attachments are intended to addressee.
Information is confidential, and exempt from disclosure under law. If
you received this message in error, you are hereby notified that
disclosure, forwarding, posting, printing, distribution or copying is
prohibited. Please notify us by reply email that you've received our
message in error and delete from your system. Thank you.
Received on Wed Oct 26 2016 - 13:31:58 BST