adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-11-03 07:22:22 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

Cookies are blocked issue #792

New Issue
Open
opened 2026-10-05 00:17:32 +02:00 by adam · 7 comments
adam commented 2026-10-05 00:17:32 +02:00
Owner
Copy link
Copy source

I cant login while I correctly installed Piwigo.
On all my browsers such as Chrome and Safari will show a message saying that I dont allow Cookies.
But when i check my prefrences, not any cookie is blocked.
So my question is can you fix this or how can i fix this?

I cant login while I correctly installed Piwigo. On all my browsers such as Chrome and Safari will show a message saying that I dont allow Cookies. But when i check my prefrences, not any cookie is blocked. So my question is can you fix this or how can i fix this? <!-- github-sync-id:331250709 -->
adam commented 2026-10-05 00:17:33 +02:00
Author
Owner
Copy link
Copy source

Ping, I have the same problem, any news reguarding this issue ?

I can access the local install of piwigo, through local network, but can't access it through my reverse proxy (Nginx).

Ping, I have the same problem, any news reguarding this issue ? I can access the local install of piwigo, through local network, but can't access it through my reverse proxy (Nginx). <!-- github-comment-id:706523640 -->
adam commented 2026-10-05 00:17:33 +02:00
Author
Owner
Copy link
Copy source

So unresolved after 2 years??? Uninstall

So unresolved after 2 years??? Uninstall <!-- github-comment-id:803071036 -->
adam commented 2026-10-05 00:17:34 +02:00
Author
Owner
Copy link
Copy source

So unresolved after 2 years??? Uninstall

changing hosting usually helps. Sorry but we can't reproduce that. And posting such messages with no details about the server doesn't help too.
Since thousands don't get that tricky bug, it will still remain as is.

But one day it will be fixed

> So unresolved after 2 years??? Uninstall changing hosting usually helps. Sorry but we can't reproduce that. And posting such messages with no details about the server doesn't help too. Since thousands don't get that tricky bug, it will still remain as is. But one day it will be fixed <!-- github-comment-id:803082016 -->
adam commented 2026-10-05 00:17:35 +02:00
Author
Owner
Copy link
Copy source

I believe this is an issue with running piwigo on a server behind proxy. In my setup, I have pigiwo on machine1 outside of public internet, have VPN between machine1 and machine2 and machine2 being visible from internet and having ProxyPass and ProxyPassReverse set in apache configuration to machine1.

Logging in when accessing piwigo through machine1 (locally) works correctly. But doesn't work when accessing through machine2 (remotely).

I believe this is an issue with running piwigo on a server behind proxy. In my setup, I have pigiwo on `machine1` outside of public internet, have VPN between `machine1` and `machine2` and `machine2` being visible from internet and having `ProxyPass` and `ProxyPassReverse` set in apache configuration to `machine1`. Logging in when accessing piwigo through `machine1` (locally) works correctly. But doesn't work when accessing through `machine2` (remotely). <!-- github-comment-id:1792736026 -->
adam commented 2026-10-05 00:17:36 +02:00
Author
Owner
Copy link
Copy source

I have this problem rare enough to forget the solution, today again.
The login process following the e-mail requesting me to upgrade to newest piwigo version always works. I compared the two identification.php addresses and it turned out, that there is sometimes a double slash in the address :

https://hpburkhard.ch//mypix/pg2022b/identification.php 
                     ==

If you remove one of them and reload the page, then you are able to log in.
Hope, this works also for you ;-)
I was not able to locate the problem in the source code.
Regards, Hampi

I have this problem rare enough to forget the solution, today again. The login process following the e-mail requesting me to upgrade to newest piwigo version always works. I compared the two identification.php addresses and it turned out, that there is sometimes a double slash in the address : ``` https://hpburkhard.ch//mypix/pg2022b/identification.php == ``` If you remove one of them and reload the page, then you are able to log in. Hope, this works also for you ;-) I was not able to locate the problem in the source code. Regards, Hampi <!-- github-comment-id:1872185726 -->
adam commented 2026-10-05 00:17:36 +02:00
Author
Owner
Copy link
Copy source

I have this same issue on GoDaddy VPS hosting. I started having issues after upgrading to Piwigo v14 and the ContactForm doesn't work -- so I found a thread indicating it could be because cookie consenting needs setup. So I installed that plugin; however browser console log shows the net::ERR_BLOCKED_BY_CLIENT message.

I have this same issue on GoDaddy VPS hosting. I started having issues after upgrading to Piwigo v14 and the ContactForm doesn't work -- so I found a thread indicating it could be because cookie consenting needs setup. So I installed that plugin; however browser console log shows the net::ERR_BLOCKED_BY_CLIENT message. <!-- github-comment-id:1898502341 -->
adam commented 2026-10-05 00:17:37 +02:00
Author
Owner
Copy link
Copy source

I don't think its reasonable to blame the hosting... this is bad coding. I run various e-commerce sites that all utilize asynchronous javascript calls on the same hosting.

I don't think its reasonable to blame the hosting... this is bad coding. I run various e-commerce sites that all utilize asynchronous javascript calls on the same hosting. <!-- github-comment-id:1898505048 -->
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#792