adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-10-30 21:52:00 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

piwigo.org connectivity #2218

New Issue
Open
opened 2026-10-05 01:10:06 +02:00 by adam · 2 comments
adam commented 2026-10-05 01:10:06 +02:00
Owner
Copy link
Copy source

Thank you for this great app in 1st place!

I have noticed that with latest 16.4.0 version Piwigo (possibly few versions lower) is intermittently freezing (http 504) , sometimes only admin.php / identification.php , sometimes even gallery does not load at all.

After few hours of troubleshooting i found the reason - Piwigo is now connecting to https://piwigo.org/ and when it's blocked by firewall (like in my case), everything get stuck up to timeout. When trying curl instead of browser from my PC, i could see part of page coming thru , then get stuck up until to timeout.

My setup:
nginx as reverse proxy , forwarding to https apache2 on raspios12 , php-fpm8.4
Raspios12 have firewall (DROP rule) implemented for apache user outgoing connections

Can the behaviour be changed in a way to not affect Piwigo functionality when piwigo.org is not reachable? Or is it possible to configure piwigo to use authenticated http proxy (like squid) ?

Thanks a lot!

Thank you for this great app in 1st place! I have noticed that with latest 16.4.0 version Piwigo (possibly few versions lower) is intermittently freezing (http 504) , sometimes only admin.php / identification.php , sometimes even gallery does not load at all. After few hours of troubleshooting i found the reason - Piwigo is now connecting to https://piwigo.org/ and when it's blocked by firewall (like in my case), everything get stuck up to timeout. When trying curl instead of browser from my PC, i could see part of page coming thru , then get stuck up until to timeout. My setup: nginx as reverse proxy , forwarding to https apache2 on raspios12 , php-fpm8.4 Raspios12 have firewall (DROP rule) implemented for apache user outgoing connections Can the behaviour be changed in a way to not affect Piwigo functionality when piwigo.org is not reachable? Or is it possible to configure piwigo to use authenticated http proxy (like squid) ? Thanks a lot! <!-- github-sync-id:4572689740 -->
adam commented 2026-10-05 01:10:07 +02:00
Author
Owner
Copy link
Copy source

Try adding the LocalFiles Editor plugin and set

$conf['send_piwigo_infos'] = false;
$conf['show_piwigo_latest_news'] = false;

in the local/config/config.inc.php

Try adding the LocalFiles Editor plugin and set $conf['send_piwigo_infos'] = false; $conf['show_piwigo_latest_news'] = false; in the local/config/config.inc.php <!-- github-comment-id:5527286510 -->
adam commented 2026-10-27 11:34:35 +01:00
Author
Owner
Copy link
Copy source

I can confirm that I experienced the same issue with Piwigo 16.4.0 running on Nginx with PHP-FPM.

Before logging in, accessing admin.php correctly redirected me to the login page. However, after logging in, accessing the admin dashboard resulted in a 504 Gateway Timeout.

The issue was resolved by adding the following settings to local/config/config.inc.php:

$conf['send_piwigo_infos'] = false;
$conf['show_piwigo_latest_news'] = false;

After disabling both features, I was able to access the admin dashboard normally again.

This suggests that the timeout may be related to outgoing requests to piwigo.org, possibly when sending site information or retrieving the latest news. It's also worth noting that access to piwigo.org may be blocked by firewalls in some countries or regions.

I can confirm that I experienced the same issue with Piwigo 16.4.0 running on Nginx with PHP-FPM. Before logging in, accessing `admin.php` correctly redirected me to the login page. However, after logging in, accessing the admin dashboard resulted in a **504 Gateway Timeout**. The issue was resolved by adding the following settings to `local/config/config.inc.php`: ```php $conf['send_piwigo_infos'] = false; $conf['show_piwigo_latest_news'] = false; ``` After disabling both features, I was able to access the admin dashboard normally again. This suggests that the timeout may be related to outgoing requests to `piwigo.org`, possibly when sending site information or retrieving the latest news. It's also worth noting that access to piwigo.org may be blocked by firewalls in some countries or regions. <!-- github-comment-id:6337470458 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#2218