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
Related
I have a problem, I installed OJS using Xampp, the installation went smoothly, but when accessing localhost/ojs I am receiving the error 500, in the index of my Xampp there is the following sentence:
Something is wrong with the XAMPP installation :-(
I don't know where to start, I've tried renaming index.php to index.txt with no results.
Thank you for your attention.
Tried to rename index.php
Tried reinstall ojs on another xampp database
localhost/phpmyadmin works fine.
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.
Working on a computer with several old Laravel projects. It looks like they are all parked with Valet.
Valet is not working on new projects, I think because Valet is over extended.
Is there a way to 'mass' un-park and unlink all valet connections or do I have to uninstall and reinstall Valet?
Going through every folder individual and manually un-parking is unrealistic.
Laravel Valet has forget command that removes parked directories to valet park list.
cd parked_directory
valet forget
While Laravel Valet doesn't have a command to forget all the registered working directories, you can manually do it by editing the ~/.valet/config.json file and remove the registered directories from the paths array like the following:
{
"domain": "dev",
"paths": [
"/Users/whoami/.valet/Sites",
"/Users/whoami/Sites/Test"
]
}
Alternatively, you can manually go to each of the registered Valet directories and forget them by running valet forget. However, this would be time-consuming especially when you have bulk registered directories with Valet.
valet links
will display all the links of the parked sites
valet unlink SITENAME
To unlink the current working directory:
valet unlink
To unlink a specific project (directory):
valet unlink my-project
Try cd into the directory that you want to "un-park" and run
valet forget
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
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