Protocol mismatch behind reverse proxy about password-manager HOT 5 CLOSED

Have you updated APP_URL in .env to reflect the final url?

from password-manager.

Yes, my configuration:

.ENV
APP_URL=https://sub.tld.com/
ASSET_URL=https://sub.tld.com

Nginx
location / {
#sub_filter 'http://sub.' 'https://sub.';
#sub_filter_once off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Cookie $http_cookie;
proxy_pass http://10.10.10.10:8080/;
}

from password-manager.

Ok, let me do some tests with same setup :)

from password-manager.

I have added TrustProxies middleware.

1. Backup the .env file stored inside container:

sudo docker cp passwordmanager:/var/www/passwordmanager/.env .env

2. Update the project code.

git pull

3. Build again the docker instance.

sudo docker-compose -f docker/docker-compose.yml build

4. Run the docker instance.

sudo docker-compose -f docker/docker-compose.yml up

5. It works?

from password-manager.

Step: 5.
sudo docker cp .env passwordmanager:/var/www/passwo rdmanager/.env

6. It works!

I can confirm that the issue is solved. Thank you so much for the quick support.

from password-manager.