laragon

ERROR 1524 (HY000): Plugin 'unix_socket' is not loaded - Laragon

吃可爱长大的小学妹 提交于 2020-06-29 05:16:38
问题 I'm migrating my production wordpress website to my local environment on Laragon. I did the following: Opened Laragon's Terminal: Menu > Laragon > Terminal Ran this command: scp user@your-remote-host:/dump.sql C:/laragon/tmp/dump.sql Imported sql-dump to my local database: mysql -u root -p your-database < C:\laragon\tmp\dump.sql Then I cloned my git repo to the root at C:\Laragon\www\ Started it up and at first it displayed a replica of the live server's homepage, but gave an error when

URL generator putting “localhost” before domain in Laravel

眉间皱痕 提交于 2020-06-01 05:14:55
问题 I've been trying to email users a verification link using signed URLs in Laravel. It seems to work okay, but the link comes out incorrect when it is built using the URL facade. public function toMail($notifiable) { $url = URL::signedRoute('confirm', ['user' => $this->user->id]); return (new MailMessage) ->subject('Activate your email address') ->line('In order to use the application, please verify your email address.') ->action('Activate your account', $url) ->line('Thank you for using our

Self-signed SSL certificate in Laragon

帅比萌擦擦* 提交于 2020-03-05 02:48:47
问题 I developed a web app in Laravel on the Laragon Apache. But this app is only available within the oraganization, and need to be exposed to the rest. Our Miscrosft team (as the system is running on a Microsoft VM) send me a 3 .crt files (Intermediate, Root and ServerCertificate). I am not using the IIS on the Microsoft VM. How do I install the certificates that the web app can be exposed (https) to the world. SSL is enabled on Laragon. 回答1: Make my Laragon Localhost web SSL Secure SOLVED by

Laravel project installed with laragon is forcing https in google chrome

半城伤御伤魂 提交于 2019-12-23 19:27:16
问题 I have a laravel project which is installed with laragon and I was working for few days nicely. Now after a sudden stop of my pc (because of electricity unavailability) I can no longer access the local site in chrome and it is forcing me to an https location. I then opened the site in mozila and it's working there perfectly. Here what chrome shows as error This site can’t provide a secure connection school.dev sent an invalid response. Try running Windows Network Diagnostics. ERR_SSL_PROTOCOL

Chrome redirects .dev to https

拈花ヽ惹草 提交于 2019-12-17 06:16:05
问题 Suddenly Google Chrome redirects my virtual-host domain myapplication.dev to https://myapplication.dev. I already tried to go to chrome://net-internals/#hsts And enter myapplication.dev into the textbox at the very bottom "Delete domain security policies" but this had no effect. I also tried to delete the browser data. What I also did is to change the v-host to .app instead of .dev but Chrome still redirected me to https:// ... It's a Laravel application running on Laragon. On other PCs in

Composer Install “Failed to open stream”

谁说胖子不能爱 提交于 2019-12-13 03:01:54
问题 Whenever I run the installer, or even manually installing Composer, I get an error that disallowed me to complete the installation and it is irritating. In Laragon, a program used to create many different projects using composer and its packages. It will not allow me to use Laravel because the Composer will not properly install and function. The Error is: The "https://getcomposer.org/versions" file could not be downloaded: failed to open stream: A connection attempt failed because the

Chrome redirects .dev to https

狂风中的少年 提交于 2019-11-26 22:44:03
Suddenly Google Chrome redirects my virtual-host domain myapplication.dev to https://myapplication.dev . I already tried to go to chrome://net-internals/#hsts And enter myapplication.dev into the textbox at the very bottom "Delete domain security policies" but this had no effect. I also tried to delete the browser data. What I also did is to change the v-host to .app instead of .dev but Chrome still redirected me to https:// ... It's a Laravel application running on Laragon. On other PCs in the same network, it works perfectly. There is no way to prevent Chrome (>= 63) form using https on .dev