By Martin Mubiru on Monday, 02 July 2018
Posted in General Issues
Replies 9
Likes 0
Views 569
Votes 0
Hi,

What could be causing this error of gateway timeout while publishing and saving drafts.

Regards,
Hey Martin,

I have tried to create a draft on your site but did not hit any 504 errors, http://take.ms/so6eN . May I know how were you able to replicate this issue?
·
Monday, 02 July 2018 21:11
·
0 Likes
·
0 Votes
·
0 Comments
·
It happens intermittently especially when the blog is long. Try one of the last long drafts that we saved. It also happens in the backend. See screenshot: https://screenshots.firefox.com/5OcteFLU5G8lzxd8/onenip.ug
·
Monday, 02 July 2018 21:25
·
0 Likes
·
0 Votes
·
0 Comments
·
Ah okay, if this is only the case for posts that are larger than usual, it is likely that your hosting environment is throwing an error probably it thinks that there are some sort of attack going on because you are sending data that is larger than usual. Could you check with your hosting provider to get them to look at their logs and whitelist such requests?
·
Monday, 02 July 2018 21:30
·
0 Likes
·
0 Votes
·
0 Comments
·
I use Ipage and the website runs on Dedicated Server. Can this be the case even for Dedicated Servers? Can ISP also be the cause?
·
Monday, 02 July 2018 21:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Martin,

Yes, the server specifications doesn't really matter but it's most likely some sort of security configuration / firewall.
·
Monday, 02 July 2018 21:58
·
0 Likes
·
0 Votes
·
0 Comments
·
You are right, the post_max_size was not matching max_upload_size at 32M
·
Tuesday, 03 July 2018 01:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Martin,

Thanks for getting back to us, is it your issue already resolved after you updated `post_max_size` PHP value to 32M?
·
Tuesday, 03 July 2018 10:13
·
0 Likes
·
0 Votes
·
0 Comments
·
It seems to have worked. Although one computer had the error again. We are still testing.
·
Thursday, 05 July 2018 00:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Martin,

Sure, keep us updated on this. It shouldn't be the browser but it's on the server
·
Thursday, 05 July 2018 00:26
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post