-
Notifications
You must be signed in to change notification settings - Fork 415
Using Gulp watch will result in JWT failure #62
Comments
i cant reproduce the error, i tried googling, and it always points me to google oauth, can you check if your google client id, google client and google redirect are correct. also serve laravel using |
if issue still exists you could eliminate 3000 and go directly to 8000 its just browserSync doing proxy on localhost:8000, the only disadvantage you'll have is not having your browser refresh on every file change anyway. also i'm thinking to remove browserSync it seems a little buggy on windows platform |
Hi @silverbux , Thanks for your help. I do use 8000 on windows these days and it works fine. Thomas |
yeah i use mac too, i use |
Oh thanks! Everything works great on mac now after adding |
if we use php artisan serve the site will be hosted in localhost:8080 by default.
if we then use gulp watch the site will be browser-sync'ed to another port, e.g. localhost:3000, the change of host seems will result in JWT error for every put request
{"message":"Wrong number of segments","status_code":401}
Actions such as updating user profile, will fail, if we carry out the action in localhost:3000 but it is completely normal in localhost:8000. Login is okay in both 3000 and 8000.
Anyone having this issue? Please correct me if I am wrong. Thanks.
The text was updated successfully, but these errors were encountered: