Photo Gallery Forums

Hi Karl,
I am getting an error in panel after I  uploaded X3 to web server ,  after I change any setting or add any context, and save, I always got an error like attached after about 30 seconds wait.   but I don't have it on my local computer. 

I am going to send you the link via private message.

thanks

Leon

This is your server Firewall blocking POST requests in the panel when saving settings. It's explained here:
https://forum.photo.gallery/viewtopic.php?t=9281

Furthermore, it is likely your host at first will claim there's nothing wrong on their side. Here is a typical dialog I would have with a host to solve the issue (scroll down a bit after clicking to view this post):
https://forum.photo.gallery/viewtopic.p ... 662#p41680

Hi Karl,

thanks,  but if I tried 1-3 times , it can save successful,   is this still the server firewall issue?  

laxina wrote:thanks,  but if I tried 1-3 times , it can save successful,   is this still the server firewall issue?  

You mean sometimes you can save, other times not? Then you are having some real problems with your server. When you click SAVE, X3 simply POSTS data to panel/x3_settings.php ... If this randomly fails, then you have problems with your server and/or internet connection. Please provide login to your panel so I can try.

Hi Karl, yes, sometimes I can save, other times not.  

link
admin
admin

Tried dozens of times just clicking "save" repeatedly, never fails:


X3 will not just randomly fail with this ... If it returns parse error, it means the returns script does not load, which in 100% of cases I have dealt with, is because of server Firewall. The firewall could be triggering based on something specific you are adding to panel, but then I need to be able to reproduce it. This is not an issue native to X3 ... how could we make it fail randomly?

If you can't find out exactly WHEN it happens, so I can try to reproduce it, then the best I can do is ask a few others to visit your panel and try to save, in an attempt to reproduce a FAIL.

Hi, Karl, thanks a lot, let me try more and see if I can find when it happen. 

I met the some problems just now.

I tried the following steps:
1. Copy the conents I just edited
2.Duplicate the chome tab
3.Paste
4.Save 

Saved!

BeastTL wrote: I met the some problems just now.

I tried the following steps:
1. Copy the conents I just edited
2.Duplicate the chome tab
3.Paste
4.Save 

Saved!

When content is too much, this error will more frequently appear.

BeastTL wrote: I met the some problems just now.
...
Saved!

What exactly is the problem? Explain the error, and send link and login to panel (PM) if you want me to diagnose.

BeastTL wrote:When content is too much, this error will more frequently appear.

It's not X3. This is your server. Either firewall rule triggering on something in the content, or triggering on too much content, or content is beyond your servers POST_MAX_SIZE (unlikely).

X3 can't bypass your server rules. If it's a firewall rule getting triggered, this needs to get resolved on your server. If you want it diagnosed, send link and login by private message.

BeastTL wrote: I met the some problems just now.

I tried the following steps:
1. Copy the conents I just edited
2.Duplicate the chome tab
3.Paste
4.Save 

Saved!

Well, I mean sometimes I can save, other times not...
So, I did the steps above, it works sometime.

It's not important whether it is X3's wrong or not, I just share these information for you.

Ok. If I am to diagnose, I need to test. Most likely it's a firewall on your server triggering on certain text in the content. It's not X3 blocking this.

mjau-mjau wrote: Ok. If I am to diagnose, I need to test. Most likely it's a firewall on your server triggering on certain text in the content. It's not X3 blocking this.

I see.
I  just post same content, but my current working chrome tab shows error, the duplicated new tab shows saved.
after more content was input, the way I said doesn't woek.

I  belive the most important reason is from server's configuration.

so, I just want to share what a saw, I don't think it's necessary to resolve this issue. 

Just let it be.