Laravel Pusher广播问题：修改APP_URL后无法正常工作

Hey there, let's work through this Pusher broadcasting issue you're facing after updating your Laravel app's APP_URL to http://helpme.test. I've dealt with similar quirks before, so here are the most likely fixes to try step by step:

1. Verify Configuration References to APP_URL #

First, make sure no part of your setup is still clinging to localhost instead of using the updated URL:

• Check your config/broadcasting.php file: Ensure the Pusher configuration doesn't have a hardcoded host or auth_endpoint pointing to localhost. It should rely on environment variables or the APP_URL config value.
• For your frontend, confirm you're using the MIX_APP_URL environment variable in your Pusher/Echo initialization. Add MIX_APP_URL=http://helpme.test to your .env file—Laravel Mix requires the MIX_ prefix to expose variables to the frontend.

2. Clear Caches & Rebuild Frontend Assets #

Laravel caches configuration values, and frontend assets are compiled with environment variables at build time. Run these commands to refresh everything:

# Clear Laravel config and cache
php artisan config:clear
php artisan cache:clear
php artisan view:clear

# Rebuild frontend assets to inject updated MIX_APP_URL
npm run dev
# Or use npm run prod for production builds

3. Update CORS Settings #

Custom domains often trigger CORS blocks. Check your config/cors.php file:

• Ensure the paths array includes /broadcasting/auth (the route used for Pusher authentication).
• Add http://helpme.test to the allowed_origins array, or set it to ['*'] temporarily to test if CORS is the culprit. Example:

  'allowed_origins' => ['http://helpme.test'],
  

4. Check Pusher Dashboard Origin Permissions #

Log into your Pusher dashboard, navigate to your app's Settings > Origins, and make sure http://helpme.test is listed as an allowed origin. Pusher blocks connections from unapproved domains by default, so this is a common gotcha.

5. Debug Frontend Initialization #

Open your browser's developer console to check for JavaScript errors related to Pusher/Echo:

• Confirm your Echo initialization in resources/js/bootstrap.js uses the correct authEndpoint tied to your new URL. It should look like this:

  import Echo from 'laravel-echo';
  
  window.Pusher = require('pusher-js');
  
  window.Echo = new Echo({
      broadcaster: 'pusher',
      key: process.env.MIX_PUSHER_APP_KEY,
      cluster: process.env.MIX_PUSHER_APP_CLUSTER,
      encrypted: true,
      authEndpoint: `${process.env.MIX_APP_URL}/broadcasting/auth`,
  });
  

• If you see errors about missing environment variables, double-check that MIX_APP_URL is set in .env and you've rebuilt your frontend assets.

6. Test the Broadcast Authentication Route #

Manually visit http://helpme.test/broadcasting/auth in your browser. You should get a 401 Unauthorized response (normal, since it requires authentication) instead of a 404 or CORS error. If you get a 404, ensure Broadcast::routes() is included in your routes/web.php or routes/api.php file.

Start with the cache clearing and frontend rebuild—those are the quickest wins. If those don't work, move through the other steps one by one.

内容的提问来源于stack exchange，提问作者Nadir