[BUG] Piwigo jumps in and out of logged in user when using reverse proxy (SWAG)

[GD-Dal]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I run Piwigo as a docker in Unraid.
I also run the SWAG reverse proxy in Unraid
Since they both use the same custom bridge based network, SWAG connects to Piwigo by hostname.
I simply copied the piwigo.subdomain.conf.sample to piwigo.subdomain.conf
I suppose this is fairly standard setup, and has worked well for me on lots of other containers.

But with Piwigo it does not work properly.
The site opens just fine, and I can log in.
When when I start flickering through albums, I am sometimes logged in and sometimes not.
Sometimes I'm able to get into the Administration page, sometimes not.

If I open Piwigo directly without going through the reverse proxy, it works fine

Anyone else experiencing problems when going through SWAG?

Thanks

Expected Behavior

No response

Steps To Reproduce

It is reproduced simply by accessing the application through SWAG

Environment

- OS: Unraid 6.12.4
- How docker service was installed: Through UNRAID

CPU architecture

x86-64

Docker creation

docker run
  -d
  --name='piwigo'
  --net='frontend'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Unraid"
  -e HOST_CONTAINERNAME="piwigo"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:80]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/piwigo-logo.png'
  -p '8084:80/tcp'
  -v '/mnt/user/felles/bilder/':'/gallery/galleries':'ro,slave'
  -v '/mnt/user/appdata/docker-containers/piwigo':'/config':'rw' 'lscr.io/linuxserver/piwigo'

Container logs

..

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity