Category Image Can't Upload

[ronaklimbachiya]

A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.

I'm running on magento 2.2.1.

I have recently installed SM Market theme on my site and created child theme of this SM Market theme. Whenever i have tried to Upload category image its always give me an error like this.

"A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later."

Can anyone have solution on this?

Thank you.

[Damian Culotta]

Hi @ronaklimbachiya,

Can you enable the Magento's logs and check if there is soem reelvant information there. Also the webserver error log could be helpful.

[ronaklimbachiya]

Hello @Damian Culotta

I have check into log files but there is nothing i found related to this issue. I have checked all log files and also check webserver error log but there's nothing overthere.

Image was move to tmp folder but when i'm hit on save then it's gives me an error.

[Damian Culotta]

Hi @ronaklimbachiya,

The status code 406 means (probably) that the response type returned is not included into the Accept HTTP header in your request.

Can you check the response?

[ronaklimbachiya]

Hi @Damian Culotta

I have check the response and it's says {"error":0}

[Damian Culotta]

Hi @ronaklimbachiya,

Can you check your Magento's logs and the webserver error log? (I'm a little bit out of ideas without an error message)

[khadijasadd993]

This kind of issue is quite common when working with Magento 2, especially after updates or configuration changes. One thing I’ve found useful is clearing the generated files and re-deploying static content before testing again — it helps eliminate any cached or mismatched data causing unexpected behavior.

Also, make sure the correct permissions are set on your pub/static and var folders, as incorrect ownership can sometimes trigger similar errors. If the problem persists, enabling developer mode and checking the specific error log entries usually provides a clear direction on what’s failing.

It’s always a good idea to document the steps that led to the issue — that way, it becomes much easier to troubleshoot or discuss with others facing similar challenges.

[iyerananth181b]

Hello,

It could be related to the Rate Limitation Rules on the Server, which can often result in legitimate requests being mistaken for robotic activity.

Please check with your DevOps or server's support team to resolve the issue.

Thank you.