Is there an existing issue for this?
Current behavior
NGNIX proxy is having the following issues:
- It redirects the user from
http://localhost to https://localhost, this is problematic because plane is running on http://localhost
- Upon inspecting the logs of the NGNIX's docker container the following message was encountered 2024/01/02 07:33:18 [emerg] 1#1: invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf:22
nginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf:22
Steps to reproduce
- Stop all docker containers
- Remove the NGNIX reverse proxy image which is usually named as
plane-proxy
- Rebuild the project with
docker compose -f docker-compose-local.yml up -d command
- Check logs of the the docker container running reverse proxy (usually
plane-proxy-1)
Browser
Mozilla Firefox
Version
Local
Is there an existing issue for this?
Current behavior
NGNIX proxy is having the following issues:
http://localhosttohttps://localhost, this is problematic because plane is running onhttp://localhostnginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf:22
Steps to reproduce
plane-proxydocker compose -f docker-compose-local.yml up -dcommandplane-proxy-1)Browser
Mozilla Firefox
Version
Local