Closed titantwentyone closed 2 years ago
Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.
Thanks!
@driesvints Managed to track down my issue which was the firewall not accepting connections on 9003. Generally, the firewall on Linux distros are quite restrictive by default and I've seen the same issue reported here in lots of places - many with no solution and I'm wondering if a small note would be worth adding to the docs? I think people will be so fixated on a config issue with docker/sail that they may miss this. Could save a lot of heartache. Literally just one sentence - "Make sure your docker host accepts connections through the port used by xdebug, typically 9003.".
@titantwentyone feel free to attempt a PR to the docs 👍
Also...
Description:
XDebug not hitting breakpoints
Steps To Reproduce:
Below are the minimum steps I needed to recreate the issue.
laravel new xdebug-issue
cd xdebug-issue/
php artisan sail:install
(Only selected option 2 - MariaDB)SAIL_XDEBUG_MODE=develop,debug
to .env (note that according to the docs, I do not need to addSAIL_XDEBUG_CONFIG
as my installed versions ofdocker
anddocker-compose
exceed those required to manually specifiy thehost.docker.internal
var)sail up
routes/web.php
:http://localhost/
- breakpoint is not hitConfig for VSCode is:
I note that the logs from Sail state
I'm really unsure whether this is an issue with Sail (specifically on Linux machines) or something is missing from the docs (again - something as Linux users we need to do).