Piwigo works fine over https.

Problem can be on your client side if you're on Windows and some odd software constellation, worst some AntiVirus snake oil hijacking your TLS connection but not able to handle TLS 1.3, then disable its https scanning. Or rather, disable it anyway because it's stupid to install a Man-In-The-Middle.

Other than that, problem is more likely on the server side: Something on your site is forcing https to port 80, which it shouldn't. Check your httpd.conf <VirtualHost> sections, also the server of course must listen to all ports given there for the correct protocol. Make sure it hands out TLS 1.2 (best not TLS 1.0 and not TLS 1.1). Or ask your hosting provider if all that is out of your reach. You can try if already the handshake fails using

openssl s_client -connect yourdomain.tld:443

and watch the output. (Just press Ctrl+D if successful and it's waiting for further input). You can force TLS 1.2 with the -tls1_2 option to that command.

Oh and btw, your PHP 5.3.29 is way old and outdated. Better upgrade to 7.1

Hi, my son found a solution:

"Jag har skapat två filer i
~/mydomain.com/public_html – dels (den dolda) ".user.ini":

   ; Fixa SERVER_PORT så att redirects i Piwigo funkar.
   auto_prepend_file =
/storage/content/96/******/mydomain.com/public_html/https_port_fix.php

...och dels "https_port_fix.php":

   <?php
   // Fixa SERVER_PORT så att redirects i Piwigo funkar.
   $_SERVER['SERVER_PORT'] = 443;
   $_SERVER['HTTPS'] = 'on';

Detta gör att PHP-snutten ovan laddas först i varje PHP-skript och fixar
inställningarna så att Piwigo inte blir förvirrat.
Referens: http://php.net/manual/en/ini.core.php#i … epend-file

Det var för övrigt en buggrapport och diskussion om detta i Piwigo för
ett tag sedan – det är inte bara Binero som har lite konstig config:
[Github] Piwigo issue #681

My translation:

"I've created two files in:
~/mydomain.com/public_html – first (the hidden) ".user.ini":

   ; Fix SERVER_PORT making redirects work in Piwigo.
   auto_prepend_file =
/storage/content/96/******/mydomain.com/public_html/https_port_fix.php

... and second: "https_port_fix.php":

   <?php
   // Fix SERVER_PORT  making redirects work in Piwigo.
   $_SERVER['SERVER_PORT'] = 443;
   $_SERVER['HTTPS'] = 'on';

The fix results in making the PHP snippet above load first in every PHP-script to fix the settings, to not confuse Piwigo.
Reference: http://php.net/manual/en/ini.core.php#i … epend-file

BTW it was a bug report and the following discussion in Piwigo a while ago (it's not just Binero that has a  bit strange configuration):

[Github] Piwigo issue #681

This workaround solved the problem. Maybe it would be a good idea to put some information in some help file/installation instructions for Piwigo?

Hi,
I've got the following reply from Binero:

"Då vi har en lastbalanserad miljö så sker alla anrop mot lastbalanseringen över port 443. Internt på webbservern används sedan port 80 så därav säger variablerna sådär olika värden.
Du kan därav inte nå sidan genom https://yourdomain.com:80/your_piwigo_folder/ utan det ska vara https://yourdomain.com:443/your_piwigo_folder/.

Fint att ni kommit till en lösning på det. Ska ta det vidare och se om det är något vi kan skiva (sic!) ner någonstans för att underlätta för andra med liknande problem."

My translation:

"Due to having a load balancing environment, all calls to the load balancing are made over port 443. However, internally on the web server calls are made over port 80; that's why the variables have different values. This is the reason why you cannot reach the page by  https://yourdomain.com:80/your_piwigo_folder/  it should be https://yourdomain.com:443/your_piwigo_folder/.

It's great you've found a solution to the problem. I will forward this, we'll see if we can write this down somewhere to the benefit of others with similar problems."

Hi,

Apparently the issue is still there. And it's not just with logging in.

E-mail send to users also use the :80 in the link, so do not work at all.

The first thing i noticed though was that newly added images were all broken when pages load for the first time, but then appear fine after refreshing the page. This applies to album covers, galleries with half of the images broken, the photo pages themselves, and images/thumbnails in the admin panel (like when uploading new files) all show a broken image icon.

While everything appears fine after refreshing all pages one by one the first time, that's probably just the local cache i'm seeing. When changing the image or thumbnail size .. it's all broken yet again.

One user also mentioned the Android App not showing images over HTTPS.

So first i tried the auto prepend solution mentioned here and that did nothing for me:
[Github] Piwigo issue #681

Then i tried the 'functions_url.inc.php' modification and this did fix all of the issues above:
[Github] Piwigo issue #982

But of course what happens when updating Piwigo? I may have to do it again or might not work at all the next time. I think it would be best if a configuration option was added to Piwigo natively (as mentioned in the comments on github).

It may be a thing with many hosting providers around the planet, because the users that end up mentioning it in the forum is likely only a very small percentage.

Cheers,
M