title: Laravel Socialite - google login failed "Missing required parameter: client_id" although specified
body: <p>I have this strange issue with using Laravel Socialite to log users in via Google API.</p>
  
  <p>Everything configurations seem normal and ordinary, but I keep getting error <code>Missing required parameter: client_id</code>. Not only that, sometimes I tried again and the error became <code>Missing required parameter: redirect_uri</code> despite all these parameters have been supplied.</p>
  
  <p>This is how it is set up:</p>
  
  <p><strong>service.php</strong></p>
  
  <pre><code>'google' =&gt; [
          'client_id' =&gt; 'xxxxxxxxxx-x98asxxxx913ofk5tqvgq7lqfpgdi5u2.apps.googleusercontent.com',
          'client_secret' =&gt; 'mklOWJFhpbCzTKxxxx-xxxx',
          'redirect' =&gt; 'http://myapp.com/auth/google/callback'
      ],
  </code></pre>
  
  <p><strong>routes.php</strong></p>
  
  <pre><code>Route::get('/auth/{social_channel}', 'Auth\AuthController@redirect_to_provider');
  
  Route::get('/auth/{social_channel}/callback', 'Auth\AuthController@handle_provider_callback');
  </code></pre>
  
  <p><strong>AuthController.php</strong></p>
  
  <pre><code>/**
       * Redirect the user to the Google authentication page.
       *
       * @return Response
       */
      public function redirect_to_provider($social_channel)
      {
          return Socialite::driver($social_channel)-&gt;redirect();
      }
  
      /**
       * Obtain the user information from GitHub.
       *
       * @return Response
       */
      public function handle_provider_callback($social_channel, SocialAccountService $service)
      {
          $user = $service-&gt;create_or_get_user($social_channel, Socialite::driver($social_channel)-&gt;user());
  
          Auth::login($user);
  
          return redirect()-&gt;to('/go');
  
      }
  </code></pre>
  
  <p>Facebook Login works for me, just this Google Login issue is a stubborn and bizarre problem.</p>
  
  <p>The app is deployed on Forge (Ubuntu, Nginx).</p>
  
  <p>Can anybody spot anything wrong with this at all?</p>