Schedule not working - HTTP 301 about laravel-aws-worker HOT 4 CLOSED

Hmm, 301 is a permanent redirect - and it's not used anywhere in the package or controller

Do you have redirects anywhere in your application, in other routes?

from laravel-aws-worker.

If I set the REGISTER_WORKER_ROUTES variable to true on the production environment, and I send a post request to /worker/schedule on the website it works.

It's just in the worker environment that it doesn't work, it sends a message to http://localhost:80/worker/schedule and it gives an http-err.

I do have redirects on other routes, but I don't know why it would be hitting those on the worker and not in production. I also have redirects in my htaccess, but even removing them I always get the same 301 redirect response from the worker environment in the access log.

Edit: Could it have to do with the worker environment being in a VPC? But then so is the production environment.

from laravel-aws-worker.

Do you have your web application running in worker environment? VPC shouldn't be an issue - Amazon makes those calls from inside, also you wouldn't see anything in the log if AWS couldn't reach you

from laravel-aws-worker.

The problem was with a .ebextensions file that was setting a redirect. Thanks for your help.

from laravel-aws-worker.