I am having the same/similar problem. When I go to upload pics it almost instantly puts caution signs on the pics file names and then locks the upload.

It's bad enough that if I try to go to maintenance or anything else, it will lock up my entires site with "This site can't be reached  /**Direct link piwigo please **/  took too long to respond.  ERR_CONNECTION_TIMED_OUT

First time I thought it was me or my service provider, but it's happened every time I've attempted to upload pics the last few Sundays. (My normal upload day) The fact it locks the whole site is extremely worrisome. 

Have loved the program so far, and hope to keep using it. Since reinstalling did not work for the gentleman who created the thread, I will wait to hear if the next solution works or not. I'm just savvy enough to get most things done, but not enough to try stuff randomly. :P

Thanks!

P.S. My piwigo is in a separate folder from the normal website

Last edited by ddtddt (2016-05-30 06:19:19)

Hello again,

Update 2 to previous:

I contacted my hosting support, since I thought that maybe this could be a more general problem and they solved it.
This is what they said:

"One of ModSecurity rules have been triggered by Piwigo.
ModSecurity is an web-based firewall application that is configured to protect web applications from various attacks.
Sometimes, due to poor website coding, mod_security may incorrectly determine that a certain request is malicious, while it is legitimate actually.
So, in case of such false-positive results it is recommended just to whitelist the mod_security rule in question which we did."

Now everything is working fine. I can upload again and don't get any error messages or stuck pages.

So I guess it is a Piwigo related problem that can be solved by the hosting company until it happens again, or until the software stops triggering ModSecurity.

Antigone

Hello,

I'm not a software developer, nor a tech. I just said what THEY told me. Of course in an environment that is based on so many things, it is hard to figure out where the fault is. Fact is that they solved it in less than 5 minutes while I was for 3 days trying to figure out with forums what was wrong. So on the one hand you could say that they were familiar with issues like that and thats why they knew how to solve it so fast. This can be due to their coding of course, too.
But I would not expect them to explain technical issues over a costumer help line.
In the end the only thing I am interested in is, that my site works again with a gallery that I'm really much fond of and that helps me in my everyday practice.
When issues arise they need to be solved and anyone who posts questions tries to find answers for himself and for all the people that need them, too, and this is nothing to be ironic about.

Antigone

I'm beginning to believe that the 2.8 upgrade wasn't functional when released and Piwigo has no real solutions.  Cutting to the chase, I have followed all of your "Instructions" . I got past the upload problem and then all of my pics had the triangle error.  Auto back up failed.  Then site locked up on the upgrade.php file.  I'm in the process of deleting everything from my domain and reinstalling a clean copy of 2.8.1.  Now other forums say that doesn't work. 

How do I reinstall my 5055 pictures in the proper directory structure after my reinstall?

No bullshit "I've already answered that" answers.  Please.

But I Love it when you moan and whine.  Anyway.  My tricky self had a another gallery running 2.7.4 so most of my pictures are there.  When I upload a new picture I get the triangle exclamation point. My browser has been firefox for years.

Now I get this

http://luckypuppy.bravehost.com/GALLERY … ecent_pics


What is the symbol trying to tell me. 

When I clicked to see the picture lo and behold I got this! Yay.

http://luckypuppy.bravehost.com/GALLERY … ategory/12

I've disabled all of my plug ins.

hello cally6008
as you can easily see by searching CVE-2014-4614, the message refers to https://cve.mitre.org/cgi-bin/cvename.c … -2014-4614 which is http://piwigo.org/bugs/view.php?id=0003055 and so was fixed in 2014

So it sounds like the ModSecurity makes a false positive

and to answer directly to

If anyone from Piwigo happens to read this, I do think you need to look into errors that members are posting and work out why

the details you gave was exactly what I -we- was waiting for and that's the kind of answer I expect from a professional webhosting. Unfortunately the one of Antigone was not one of them.

To conclude on that, we will try to change our code to bypass that block, and probably report here https://github.com/SpiderLabs/owasp-modsecurity-crs if i'm not mistaken

I logged back into my cpanel and turned it back on and all is well. Able to upload.