Any ideas what error "Server responded with 0 code." means when uploading module.

[gray]

Any ideas what error  "Server responded with 0 code." means when uploading module.

 

All modules in the past upload and install OK.

 

But just one particular one, tries to install. But it comes back with error code.

 

It has copied all the files into the correct module directory. But it has not run the sql commands in the program.

 

But then after that all of BO works, until you go into modules, and you get a blank screen. The only way to get out of it is to manually delete the module directory.

 

Anybody have similar problems and any work around.

 

Thanks.

[gray]

any ideas

[Phinky503]

I am experiencing the same issue after purchasing a paid module for prestashop migration from 1.6 to 1.7.  Did you ever have your problem resolved?

[selectshop.at]

Response of server with code 0 means that request is not OK. You should read server error logs. There you will find the reason. I presume some server restrictions or rights set.

If server quits with 1 than request was executed = OK.

[rodwestwood]

I did this with tech support from my hosting provider with me.  There was nothing in the server error log and there were no permissions problems.  Every single other module installs correctly with zero issues.  The one-click upgrade module fails with response of server with 0 code every single time, so there is clearly a problem with the module archive.

[Gipielle]

Got same problem by update a module. in PS 1.7.6.3

Clean cache by remove /var/cache/dev and /var/cache/prod folders solve the issue.

Edited March 20, 2020 by Gipielle (see edit history)

[Ali Samie]

On 3/20/2020 at 6:00 PM, Gipielle said:

Got same problem by update a module. in PS 1.7.6.3

Clean cache by remove /var/cache/dev and /var/cache/prod folders solve the issue.

thanks a lot this was helpful

[rDuque]

Hi every one! I have the same problem on installing a new module in PS 1.7.2. But it is not solved removing cache files. Any ideas?

 

[zoomwi]

Hi! I was getting same error and in my case it was because of the modSecurity module. I solved it by adding a rule in the .htaccess file adding the ID which was reporting the error in the apache.error.log file:

<IfModule mod_security2.c>
   SecRuleRemoveById 101
</IfModule>

 

Hope this helps someone to solve this issue and reduce the number of investigation hours!

Regards!

[Joel Andreu]

I had the same error and found that i had left some die(); and unused variables somewhere in my module code. Deleting that solved the problem.

Hope this helps someone too.

Regards!