Before installing Laravel and Valet on my dev environment (Ubuntu), I had installed PHP 7, MySQL and phpMyAdmin and everything was working fine.
In order to install Valet I had to disable apache2 as Valet was complaining during the instalation and add nginx and follow these steps https://github.com/cpriego/valet-linux/wiki/Requirements:%20Ubuntu
However after the instalation when I try to access the phpMyAdmin through the browser I'm getting the default white page 404 - not found. How can I fix this?
You have parked your workspace directory using
valet park
Clone the phpmyadmin repository using
git clone https://github.com/phpmyadmin/phpmyadmin --depth=1
cd phpmyadmin
composer install
In the same directory just download phpmyadmin package & extract it. You will be able to access it from
http://phpmyadmin.test
If you have phpmyadmin already installed from your last setup, you don't have to download it & install it again.
I was facing the same thing migrating to valet from lamp, this is what I did:
1- Navigate to original phpmyadmin folder
cd /usr/share/phpmyadmin
2- Then add a link to valet
valet link
Hooray! you can now access it at: phpmyadmin.test
If you changed a port 8080. You can try this
localhost:8080/phpmyadmin/
I tried this and it failed to work for me, I found a workaround, check the link for my solution: https://stackoverflow.com/a/47211246/8768078
Related
I followed tutorial to setup valet in wsl2. I created a projects folder, cloned by laravel project to the folder, and ran valet park in the projects folder. I also added the .test domain to the hosts file in windows.
On opening projectname.test i am getting Valet - Not found. I am not sure if i am missing some steps here. Any help would be appreciated.
So I'm developing responsive websites and obviously need to test these via phones and tablets and it used to work fine, up until yesterday, after I tried installing js frameworks like npm.
For some reason, when I browse to my local testing using the ip it get:
404 - Not Found
I've been used to using:
http://192.168.0.2/filename.php
I've tried:
http://192.168.0.2:8080/filename.php
...still get 404 - Not Found
I've restarted Apache and checked the the port is correct, and it is.
Listen 80
This happened before when I installed Laravel and Valet, but not long after that I had to wipe my Mac due to work and it started working again with a fresh install.
Am I missing something in Apache? does npm and Laravel mess with the Apache settings?
Locally, everything works fine. I can browse to localhost/filename.php directly using Mac with PHP and MySQL talking to each other, albeit after using Homebrew to install MySQL, PHP connections now only accepts 127.0.0.1 rather than localhost.
I've set all the permissions to "everyone" there should be no access issues.
I've noticed another oddity with Firefox Dev Ed too. When I've been using Valet or Gulp, it stops connecting and give a Cannt connect to server error, but Safari and Chrome seem to work ok.
If anyone can shed some light on this, I'd be happy to give it a go!
All fixed! It was Larvel's Valet installation that was causing the issue, as suspected.
So, looked at the brew Cellar directory in /usr/local/Cellar, but it wasn't actually in there. Then opened up Terminal and typed:
valet install
Then ran valet by typing:
valet
Then uninstalled valet by typing:
uninstalled valet
Then restarted Apache2 by typing:
sudo apachectl restart
adding password
Booted up the browser and browsed to localhost/info.php which holds the line <?php phpinfo() ?> and HAPPY DAYS :)
I just cloned a repo from GitHub for a Laravel site and running it locally on valet.
I'm getting a 404 - Not Found error when I try to visit tmye local dev site, however I have the root folder in one of my valet paths directories, and have also tried running valet link in the root directory.
My other sites running in the same directory are loading just fine.
I've also tried uninstalling and reinstalling valet.
Any other ideas? I've tried everything I could find when searching the error.
I figured out the solution:
Laravel likes a "public_html" directory while valet likes "public", so I created a symbolic link folder named public and all is fine and dandy.
EDIT
This no longer seems to be an issue with valet, it recognizes both public and public_html directories
I have successfully followed the Setup a Mac Dev Machine until this tutorial: https://laracasts.com/series/setup-a-mac-dev-machine-from-scratch/episodes/10?autoplay=true
The problem is that when I go to SITENAME.dev, nothing shows up. Instead, I get the following message:
This site can’t be reached
test2.dev refused to connect. Did you mean http://test2.de/? Search Google for test2 dev ERR_CONNECTION_REFUSED
I've tried this both for a laravel install (using the laravel installer) and a wordpress install. Neither one works.
Any idea why it is not working. I have followed the course step-by-step as well as the comments. For instance, I modified the .zshrc file as follows based on the course and comments:
export PATH=$HOME/bin:/usr/local/bin:$HOME/.composer/vendor/bin:$PATH
And, in case it is relevant, I am on Mac Sierra (freshly updated).
In short, where Jeffrey is able to get a home page of laravel, I get an error.
Any idea how to fix this?
Thanks.
Go to your site folder and execute the following commands:
cd your_project
composer global update
valet uninstall
rm -rf ~/.valet
rm -rf ~/.config/valet
valet install
valet link
valet open
It fixed this issue for me, and particularly after PHP upgrades.
Mac os mojave - version 10.14,
cd in your-project-folder-name and run
valet secure your-project-folder-name
Solution:
composer global update
brew upgrade nginx
cd your_project
valet start
For more details read this blog
https://medium.com/#panjeh/valet-this-site-cant-be-reached-err-connection-refused-ad424ea1e343
Have you actually started the valet service? Head over to the directory that you ran
$valet park
in, I'm assuming it's where you've also placed your project and type:
$valet start
into the terminal. That works for me.
Be sure you're over http://app.test and not https://app.test
Laravel Valet uses Not secure http as default.
By the way if you want to secure your app then use
valet secure YOURAPPNAME
Deleting the file (sudo rm /etc/resolver/dev) will clear this issue up.
IF valet is trying to open a HTTPS (SSL connection) type command line in your terminal
valet secure
I'm trying to install Laravel valet but I keep getting (when I visit domain.dev):
It works!
I already tried a lot. For example:
remove valet
stop apache (apachectl stop)
composer global require laravel/valet
valet install
valet restart
But that does not work for me. I've also installed Laravel Homestead in a vagrant box. Perhaps that has something to do with it? I can visit my Homestead sites.
How can I fix this problem?
"It works!" will always be a message from Apache.
Apache has to be turned off for Laravel Valet to work.
I see you have tried these before:
$ stop apache (apachectl stop)
$ sudo apachectl -k stop
I had the same problem. Try with the command below and then after be sure to restart valet again! This fixed it for me:
$ sudo apachectl stop
$ valet restart
So many different combinations of what to do here
Here is what worked for me.
Turn off other local Apache altogether
sudo apachectl -k stop
sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist
Remove the Valet directory altogether
rm -r ~/.valet
Removed Valet via composer globally
composer global remove laravel/valet
Re-install via composer
composer global require laravel/valet
Install Valet
valet install
Go to Folder to Add directories
cd ~/Sites/
Then add projects to park
valet park
Change Valet domains to something else to stop urls forcing to https://
valet domain app
Change directory into the project folder
cd ./laravel-project/
Then open current project
valet open
The browser should open to http://laravel-project.app
No need to stop Apache, and it doesn't have anything to do with Homestead.
The answers provided solve your problem but they are not good.
You can simply run
valet port 8888
(or whatever port you want) and get your site on domain.dev:8888
The point is not that Apache and Nginx don't like each other, they are agnostic of each other, just keep them listening on different ports.