405 and possible reasons how to solving

  • Resolved agenciesFirst

    (@agenciesfirst)


    2 years, 3 months ago

    Hi, remember – I had already reported 405 errors a couple of times, and you were never able to replicate them. Now by chance or intuition I found the cause. It was the setting on the NGINX server for gzip compression, and specifically I had set a compression level too high and also directed json files to compress. I now use the default compression without considering json. Now masteriyo works fine. I just wanted to post this here in the forum, as it might be very helpful for others who run their server themselves to do some research in other directions to eliminate such 405 errors. The error output in the browser did not lead to the solution and is rather misleading, although in retrospect it is now logical again. But of course you have to come up with it first. I became skeptical because it ran on other servers of mine, so what was different? … 2000 installations, that’s what I call a Growth ?? Wow. Further success I find your LMS very promising.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Aashil Bijukshe

    (@lihsaa)

    Hello @agenciesfirst

    Thank you so much for pointing out the issue earlier and finding the solutions for this. This type of support surely helps us to grow even bigger in the coming days and helps other users to solve the problem.

    Also, we are currently working to make error handling a much better way. So, that if any error occurs we can easily navigate through it.

    Thank you ??

    Thread Starter agenciesFirst

    (@agenciesfirst)

    Please correct the post – it’s not 405 it caused 505. Sorry for misswriting!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘405 and possible reasons how to solving’ is closed to new replies.