Error on new post submmision

Hi,

Today, when I have tried to sumit a new post, I have got this message:
 

The information you’re about to submit is not secure

Because this form is being submitted using a connection that’s not secure, your information will be visible to others.

When I click on Send anyway, I revied another message as bellow
 

Please help.

Hi, I'm not really the person best qualified to solve this one. Has anything changed with your hosting environment if this is a sudden issue? (perhaps check with your provider if not sure). If you have access to your php.ini you can check the post_max_size value and alter accordingly. I believe Composr also has a setting which you can search for and change. I think the 2nd issue is a product of the first. The not secure thing sounds like it could be an SSL issue. Developers are otherwise engaged currently, so I would suggest check with your hosting provider if this is still an issue.

To give a little insight…

If a server such as Cloudflare is utilized most of the time it's related to the setup in the DNS records. If you have not changed anything and using Cloudflare, the issue seems to correct itself after a few days.

I have experienced this firsthand.

Master Rat

Hi
Thanks for your reply.

I contacted my hosting provider, he has increased the value of the (post_max_size) to 1024M in PHP.INI, he has configured my website to use HTTPS with SSL/TLS as well, but still the problem has not been solved!

Did you install the SSL addon to the site? That would be my first guess as to the issue.

If my thought is correct when you are posting it is sending it to the HTTP form not to the HTTPS form if you do not have the SSL addon installed within the site (Composr).

Just my guess.

Very late reply I know, but usually this kind of problem is caused by a .htaccess redirect. It's very common for server admins (for example) to naively code up redirects to send every hit to HTTPS, without realizing this squashes any HTTP POST data attached to the original request.

Sites should not be HTTP nowadays, so the ultimate solution would probably not be removing that redirect but making the base_url setting in _config.php use https.