Make sure you don't have the POST request method on https://landyvlad.net/piwigo/identification.php forbidden somewhere/somehow, i.e. check .htaccess in piwigo/ and also in the domain's document root or even higher up.

It might also be a mod_security rule problem. If in doubt, ask your hosting provider.

landyvlad wrote:

Where would I find  .htaccess in piwigo? I had a look but couldn't find it ?

It's a hidden file at the root of your piwigo install.

Also I have no idea how to find out if the POST request method is forbidden somewhere/somehow? I wouldn't have done that on purpose, certainly.

Might be in that file somewhere.
Could also be a cPanel setting somewhere?

Has it worked before? If so, what changed between then and now?

PS: The logs you posted seem largely irrelevant.

I can only repeat:

"It might also be a mod_security rule problem. If in doubt, ask your hosting provider."

landyvlad wrote:

Maybe I need an htaccess file.  Is there somewhere I can grab the 'normal' piwigo htacess file to put in that directory and see if it works?

I've never encountered anything like a 'normal' piwigo .htaccess file. But my experience with Piwigo is still limited.
Nevertheless I suspect that your problems have something to do with cPanel - how it manages your server, sites and certificates. I had to jump over several fences to make things work for me consistently.
And as having a specific .htaccess file in public_html solved most of my previous problems, try putting there (in public_html) a .htaccess file containing this:

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteCond %{REQUEST_URI} ^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Sectigo\ DCV)?$ [OR]
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

landyvlad wrote:

In that code though is some of it unique to your directory structure?
(?:\ Sectigo\ DCV)
(?:\ Ballot169)

No, it is not.

Sectigo is Comodo - look into your certificate's 'Certification Path'. It says:

Sectigo (formerly Comodo CA)
   cPanel, Inc. Certification Authority
      landyvlad.net

DCV stands for Domain Control Validation.
See https://duckduckgo.com/?q=sectigo+dcv for explanation of how it works.

Allegedly the .well-known directory appears on all cPanel servers that are using the Comodo (now Sectigo) AutoSSL feature. Your site does use it, right?
Ballot169 refers to the domain validation methods that CAs (certification authorities) may use.
People around the world say that while the line with Ballot169 seems superfluous it is expected by cPanel especially for new/fresh certificates or around the time when they are due to be renewed.

Now - after I looked into your certificate (and compared it with mine) - I am assuming that both our host providers use roughly the same version/implementation of cPanel (and its certification authority). That's why I think that my tip may be useful to you.
But if not... there are so many reasons behind the obnoxious 403 error.
So if my solution does not work for you check this tutorial https://www.hostinger.com/tutorials/wha … -to-fix-it.

Last edited by MartaW (2022-06-14 13:55:40)

landyvlad wrote:

will report back

I am getting curious ;)
Still plenty of time till your certificate expires (on July 27).