sajya
405 Method not allowed on production
Hi,
Currently I'm running "laravel/framework": "^8.10" with "sajya/server": "^2.0". When I'm on my local machine(windows) the rpc endpoint works fine when posting. When I do the same post to the production environment via Postman I get the error The server returned a "405 Method Not Allowed". I have cleared the routes and cached them again. The production systen is running Ubuntu
Hey Joey. I doubt I can reproduce my error. But I can help realize it. Error 405 is not Sajya answer. That is, the package does not start its work either. Do you have cached routes?
Execute the artisan command
php artisan route:clear
It would also be great if you specified the command and headers, for example, using curl.
Hey Joey. I doubt I can reproduce my error. But I can help realize it. Error 405 is not Sajya answer. That is, the package does not start its work either. Do you have cached routes?
Execute the artisan command
php artisan route:clearIt would also be great if you specified the command and headers, for example, using
curl.
I did already gave that a shot before posting the issue, but I will try again tonight and see if it changes anything.
Hey Joey. I doubt I can reproduce my error. But I can help realize it. Error 405 is not Sajya answer. That is, the package does not start its work either. Do you have cached routes? Execute the artisan command
php artisan route:clearIt would also be great if you specified the command and headers, for example, using
curl.I did already gave that a shot before posting the issue, but I will try again tonight and see if it changes anything.
Still the same issues
same error returns.
'Laravel Framework 8.62.0' 'sajya/server 4.0.2'
Just quick start followed.
Maybe it's a little late, but can help others later facing to same issue. In my case my fault caused the same problem, and that was trivial. Our production server run on https, but i sent the calls through standard http, when I tried to test the jsonrpc backend. The apache server forwarded the calls to https, but with GET method. That's why I got 405 errors from the laravel backend.
