PHP script execution won't start at break point - vagrant

Question

I'm running PHP 5.5.9 on Ubuntu 4.19, Vagrant, Virtual box on Mac. I'm trying to use debugger on PhpStorm (2016.2.1) , so I followed couple of tutorials how to do that, enabled XDebug 2.2.3. My current status is:
When checked from PhpStorm (Run -> Web Server Debug Validation) everything is ok, no errors.
On Google Chrome I've installed "Jet Brains IDE support" plugin
On PhpStorm when I click on "Start listening for PHP debug connections" it turns green - everything fine here too, I guess.
PhpStorm, when I click "Debug" icon, Chrome starts well, opens page I'm trying to debug and I get balloon tip from Chrome: "JetBrains IDE Support" is debugging this browser and small bug icon turns green ("debug" mode).
So apparently everything is ok, but script execution just won't stop at my break point. Any idea what I'm missing here. Here is my php.ini settings regarding xdebug:
Directive Local Value Master Value
xdebug.auto_trace Off Off
xdebug.cli_color 0 0
xdebug.collect_assignments Off Off
xdebug.collect_includes On On
xdebug.collect_params 0 0
xdebug.collect_return Off Off
xdebug.collect_vars Off Off
xdebug.coverage_enable On On
xdebug.default_enable On On
xdebug.dump.COOKIE no value no value
xdebug.dump.ENV no value no value
xdebug.dump.FILES no value no value
xdebug.dump.GET no value no value
xdebug.dump.POST no value no value
xdebug.dump.REQUEST no value no value
xdebug.dump.SERVER no value no value
xdebug.dump.SESSION no value no value
xdebug.dump_globals On On
xdebug.dump_once On On
xdebug.dump_undefined Off Off
xdebug.extended_info On On
xdebug.file_link_format no value no value
xdebug.idekey PHPSTORM PHPSTORM
xdebug.max_nesting_level 100 100
xdebug.overload_var_dump On On
xdebug.profiler_aggregate Off Off
xdebug.profiler_append Off Off
xdebug.profiler_enable Off Off
xdebug.profiler_enable_trigger Off Off
xdebug.profiler_output_dir /tmp /tmp
xdebug.profiler_output_name cachegrind.out.%p cachegrind.out.%p
xdebug.remote_autostart Off Off
xdebug.remote_connect_back Off Off
xdebug.remote_cookie_expire_time 3600 3600
xdebug.remote_enable On On
xdebug.remote_handler dbgp dbgp
xdebug.remote_host 192.168.33.22 192.168.33.22
xdebug.remote_log no value no value
xdebug.remote_mode req req
xdebug.remote_port 9000 9000
xdebug.scream Off Off
xdebug.show_exception_trace Off Off
xdebug.show_local_vars Off Off
xdebug.show_mem_delta Off Off
xdebug.trace_enable_trigger Off Off
xdebug.trace_format 0 0
xdebug.trace_options 0 0
xdebug.trace_output_dir /tmp /tmp
xdebug.trace_output_name trace.%c trace.%c
xdebug.var_display_max_children 128 128
xdebug.var_display_max_data 512 512
xdebug.var_display_max_depth 3 3
Update 1
On #LazyOne suggestion I checked on php error log and there was an error:
PHP: syntax error, unexpected '=' in /etc/php5/apache2/php.ini on line 1935
Failed loading /usr/lib/php5/20100525/xdebug.so: /usr/lib/php5/20100525/xdebug.so: cannot open shared object file: No such file or directory
I checked for missing xdebug.so file and it's parent dir was wrong. On my machine it was "20121212", so I changed that, restarted apache and after I'm getting following content in error log:
[Fri Aug 26 12:15:55.407344 2016] [mpm_prefork:notice] [pid 22840] AH00169: caught SIGTERM, shutting down
PHP Warning: Module 'xdebug' already loaded in Unknown on line 0
[Fri Aug 26 12:15:56.415611 2016] [mpm_prefork:notice] [pid 22903] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.19 configured -- resuming normal operations
[Fri Aug 26 12:15:56.415660 2016] [core:notice] [pid 22903] AH00094: Command line: '/usr/sbin/apache2'
That's all there is in php error file. #LazyOne, is that the error log file you were talking about or there is some other?
Update 2
I added following configuration to my php.ini file:
[xdebug]
zend_extension = /usr/lib/php5/20121212/xdebug.so
xdebug.remote_enable = 1
xdebug.remote_host = 192.168.33.22
xdebug.remote_port = 9000
xdebug.idekey = PHPSTORM
Update 3
xdebug log follows:
Log opened at 2016-08-26 13:55:30
I: Connecting to configured address/port: 192.168.33.22:9000.
E: Could not connect to client. :-(
Log closed at 2016-08-26 13:55:30