erAck

I also use a letsencrypt cert and it is not set to expire until mid-December.  When I go to 'Tools" and click on 'updates' I get "Check for update failed for unknown reasons".  When I go to 'Tools' then 'Maintenance' and click on 'Check for upgrade' I get "Unable to check for upgrade".

The permissions for the two directories are:

drwxrwxrwx.  7 apache apache    68 Sep 28 12:13 upload

drwxrwxrwx.  7 apache apache 56 Sep 28 12:13 2021

The httpd service runs as 'apache'

Bill

Yes, I understand that its not my cert.  I ran the curl cmd and got the following which looks ok to me.


*   Trying 51.38.237.64...
* TCP_NODELAY set
* Connected to piwigo.org (51.38.237.64) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=piwigo.org
*  start date: Sep  4 15:56:12 2021 GMT
*  expire date: Dec  3 15:56:11 2021 GMT
*  subjectAltName: host "piwigo.org" matched cert's "piwigo.org"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
> HEAD / HTTP/1.1
> Host: piwigo.org
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: nginx
Server: nginx
< Date: Fri, 01 Oct 2021 18:33:01 GMT
Date: Fri, 01 Oct 2021 18:33:01 GMT
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Connection: keep-alive
Connection: keep-alive
< Set-Cookie: pwg_id=4ejbpq7cnbo92fqd42178tfugu; path=/; HttpOnly
Set-Cookie: pwg_id=4ejbpq7cnbo92fqd42178tfugu; path=/; HttpOnly
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
Pragma: no-cache

<
* Connection #0 to host piwigo.org left intact

Running  php filename.php resulted in:

"Good connection to piwigo.org"

A few days ago during a routine dnf update I saw what I think was a root certificates update.  But not 100% sure.  I ran "dnf list|grep -i cert" and the only thing I saw that looked relevant was "ca-certificates.noarch".  I was thinking that a cert update had messed things up.

Other than that I'm still scratching my head.

Bill

Surely your firewall has some logging function to find out what is requested?

Anyway, depending on which localization/language you run Piwigo in there may be subdomains involved, like fr.piwigo.org or de.piwigo.org; see upgrade.php for a possible list (search for PHPWG_DOMAIN).

I have solved the upload image permissions issue.  It turns out it was an selinux issue.  The following commands fixed the problem:

semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/yoursite/(/.*)?"
restorecon -R -v /var/www/yoursite/
systemctl restart httpd

Now the only problem is I am unable to update via the web admin interface.  When I click on "Check for upgrade" I get "Unable to check for upgrade"

I am using Piwigo 11.5.0

erAck - With my limited php programing skills I am unable to see the contents of the php $src variable.  I have looked at the php files you suggested to no avail. 

I did a recursive grep for "unknown reasons" and the error seems to be generated from:
./admin/themes/default/template/updates_pwg.tpl as  added a few extra characters to the word 'update' and it display when checking for updates.

I can access piwigo.org from the command line with the php script you pointed me to a while back and with wget, etc.

Last edited by wildbi111 (2022-04-14 20:52:50)

I guess "support" no longer exists for Piwigo as far as my issues.

I just checked this post/thread after being detained in the hospital for the past week.  I need to get this issue fixed asap.

If there is a sure-fire solution to migrate to a new install of Piwigo I'd be willing to attempt that.  I have 112 Albums and 2,987 images that will need to be migrated.  Any suggestions/help would be greatly appreciated.

Bill