Kovah / LinkAce

LinkAce is a self-hosted archive to collect links of your favorite websites.
https://www.linkace.org
GNU General Public License v3.0
2.63k stars 163 forks source link

1.11.2 Form insecure using proxy #625

Closed akalderon closed 1 year ago

akalderon commented 1 year ago

Bug Description

Using NGINX proxy with SSL termination at the frontend yields connection insecure error when logging into linkace. This is not an issue in 1.11.1 nor is it an issue with any other SSL terminations on same servers.

Browser acknowledges that connection is secure by virtue of the valid SSL certificate on the front-end with the Proxy

Yielding an insecure form notification at login and a warning message that connection is insecure post credential submission requesting acknowledgment with 'Send Anyway' button. Clicking 'Send Anyway' proceeds to dashboard screen.

On iOS does not progress past login screen - just discards credentials and reloads the login screen

docker compose down, pulling 1.11.1-simple and docker compose up with no changes to compose file reverts to normal behavior with no issues on SSL offloading/termination via front-end proxy

How to reproduce

Expected behavior

In 1.11.1 this was not an issue. SSL was accepted on the backend and post credentials login dashboard would show up as per normal behavior

Logs

No response

Screenshots

No response

LinkAce version

v1.11.2

Setup Method

Docker

Operating System

Linux (Ubuntu, CentOS,...)

Client details

Kovah commented 1 year ago

Could you please confirm that your proxy is correctly configured to send the headers specified in the docs?

https://www.linkace.org/docs/v1/setup/setup-with-docker/advanced-configuration/#running-linkace-behind-a-proxy-load-balancer

917huB commented 1 year ago

subscribing. I'm seeing the same with TraefikEE. Will verify headers are correct.

Kovah commented 1 year ago

I have release a fix version. I missed the fact that trusted proxies are properly handled in the framework. Please try again with the v1.11.3.

akalderon commented 1 year ago

Confirmed v1.11.3 fixes the issue - thank you!