[Troubleshooting] Fails to find Valet after debug install #281
Closed
richardhulbert
started this conversation in
Troubleshooting
Replies: 7 comments
-
|
The issue appears to be an extension, as according to the log file xdebug isn't being loaded properly. Here's how PHP Monitor runs the This is probably causing the issue. I'm guessing you're talking about Xdebug that you installed? How did you do so, via PHP Monitor or via |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Nico I believe I installed Xdebug via PHP Monitor. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm guessing this is some sort of permission issue, as PHP can't load the installed extension from the path... or the Let's make sure it's not a silly permission issue related to Homebrew first: what is the output of Also, what's the output of |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok here is the brew doctor output: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
and here is php --ini interesting as Valet is using php 8.1 There is probably a bit of trying up needed in homebrew - I have to go into a meeting now but will have a look after Thanks for looking at this |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
There seems to be some potential issues with Xdebug on PHP 8.1. I don't believe this is caused by PHP Monitor strictly, so I'm going to move this to discussions. Feel free to let me know if you have an update or discover something new. If |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Solution! get a listing of packages Uninstall the old version of Homebrew https://stackoverflow.com/questions/71663540/two-homebrew-on-my-mac-one-in-opt-and-one-in-local-how-do-i-delete-one/71820477#71820477 install a new version of Homebrew for Apple Silicone (Mn) then restart Valet My problem was wholly Homebrew related. As you spotted I was running Homebrew in I had switched machines from intel to Mac silicone M2 and although I thought I had followed the procedure to port to the arm based version of Homebrew I was in fact still running the intel version in a weird place! Many thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there an existing issue for this?
Current Behavior
Initially the app started fine and would be able to select PHP versions etc but I have upgraded Valet and now PHP monitor starts with Your Valet version could not be read
valet --version yields : Laravel Valet 4.6.1
Expected Behavior
App starts up without prompt
Steps To Reproduce
Environment
Do you have a log file (or a screenshot) or any additional information?
last_session.log
Beta Was this translation helpful? Give feedback.
All reactions