Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to log into instance behind reverse proxy #1146
I think I am experiencing the same issue described here #1130.
My configuration is the next one:
When I connect to shaarli throw 192.168.1.1:80, I am able to log in successfully.
Moreover, to do the installation, when I delete data/config.json.php and reload from example.com, I am redirected to 192.168.1.1 until I finish to configure it successfully. I got an error message about php session but If I say try again I am able to configure it.
When it is finally configured, I can now accessed from example.com and 192.168.1.1 but login works only from 192.168.1.1
I set "session_protection_disabled": false, to true but it doesn't change anything.
Hi, I suspect there is an issue with your webservers configuration.
You can obfuscate the real domain as long as it stays coherent. :)
I didn't know about $SERVER, thank you :)
I did it and it appears that ["HTTP_COOKIE"] is not sent when I am connecting from example.com ;
I am not sure it was from my side. I use the same reverse proxy configuration from a lot of different services with cookie like Nextcloud or Pluxml and I have no errors.
Thank you for your help :)
--------- from 192.168.1.1
--------- virtual host
reverse proxy configuration
I'm not sure what's causing the issue, and I don't have much time to run an Apache config test right now, but I think that your issue is that when you're connecting through
It should be
@mirabellette Have you tried setting
instead of the IP address in the VM's apache configuration? Otherwise you should probably investigate settings in https://httpd.apache.org/docs/2.4/mod/mod_proxy.html. Unfortunately not much time to reproduce your setup right now.
You were right, the error was about the web server configuration with the reverse proxy. It didn't transmit correctly the server name host to the virtual machine.
To fix it, you should add this parameter to the Apache2 configuration.
Thank you very much for your help and sorry for the inconvenience.