
What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello guys! My xdebug suddenly stopped working! I've already tried rebooting, reinstalling the proje

Hello guys! My xdebug suddenly stopped working! I've already tried rebooting, reinstalling the project, purging the docker machines, using different browsers and IDEs.
Does anyone have any idea on what I can try to resolve this?
These are my debug configs:
Comments
-
can you verify that these ports are indeed exposed and open?
0 -
Yeah, PhpStorm is listening for them
0 -
Might be related to discussion we had yesterday internally.
There was a major Xdebug update (2.9 -> 3) in the latestΒ spryker/php:7.3, but the included config doesn't match yet. Switch toΒ spryker/php:7.2Β in your docker-comppose as a temporary fix (e.g.Β deploy.dev.yml).
But I would try actually to use spryker/php:7.3-alpine3.12 or spryker/php:7.3-alpine3.11 if changing to 7.2 isn't an option.
0 -
Hmm I'll try to do that, thanks @valerii.trots
0 -
Or maybe that won't help as both has been pushed yesterday as well.
0 -
So maybe the only option is really to downgrade to 7.2 images.
0 -
We already use spryker/php:7.3-alpine3.12, I'll try chanigng to spryker/php:7.3-alpine3.11 and 7.2 if it does not work
0 -
Same here, can't debug anymore.
0 -
The strange thing is that it was until yesterday it was working fine, we did not update the docker images
0 -
Don't waste your time with 7.3:
We updated all the images on docker hub except 7.2 based.
0 -
I did a clean setup this morning. Most likely I git the docker images updated.
0 -
Also these settings may work:
xdebug.default_enable=0 xdebug.auto_trace=0 xdebug.coverage_enable=0 xdebug.mode=debug xdebug.start_with_request=1 xdebug.client_host=${SPRYKER_XDEBUG_HOST_IP} xdebug.client_port=9003
0 -
Any timeframe on when the 7.3+ Images will be fixed?
0 -
Port 9003 needs to be exposed
0 -
Any timeframe on when the 7.3+ Images will be fixed?
Yesterday it was said that today they will be fixed but it's not an official statement and I wouldn't like to bring wrong expectations here.
0 -
π
0 -
I can confirm that docker/sdk 1.30.0 and changing the debug port to 9003 worked for me. Thanks!
0 -
Got it to work by using por 9003 thanks @valerii.trots
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 79 Spryker News
- 949 Developer Corner
- 807 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 69 Spryker Safari Questions
- 50 Random