Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: NGNIX proxy misbehaving #3297

Closed
1 task done
divyanshchahar opened this issue Jan 2, 2024 · 7 comments
Closed
1 task done

[bug]: NGNIX proxy misbehaving #3297

divyanshchahar opened this issue Jan 2, 2024 · 7 comments
Assignees

Comments

@divyanshchahar
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

NGNIX proxy is having the following issues:

  1. It redirects the user from http://localhost to https://localhost, this is problematic because plane is running on http://localhost
  2. 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

  1. Stop all docker containers
  2. Remove the NGNIX reverse proxy image which is usually named as plane-proxy
  3. Rebuild the project with docker compose -f docker-compose-local.yml up -d command
  4. Check logs of the the docker container running reverse proxy (usually plane-proxy-1)

Browser

Mozilla Firefox

Version

Local

@abidkhan484
Copy link
Contributor

This line is occuring the below error for evnsubst shared in this line.

invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf

This is the case you are getting the error

Any better solution for assigning the variable with envsubst is highly appreciated.

@Arvin-Zi
Copy link

Arvin-Zi commented Jan 9, 2024

@abidkhan484 hey have you found the solution for this? i appreciate your help

@abidkhan484
Copy link
Contributor

here is the solution

@Arvin-Zi
Copy link

@abidkhan484 Yeah i tried that to add the "empty" bit, but still when im dockering it up the same error is happening

@abidkhan484
Copy link
Contributor

It can be due to caching, try removing cache.

@abidkhan484
Copy link
Contributor

@divyanshchahar The issue may not persist with the PR #3296

@mguptahub
Copy link
Collaborator

this is no more an issue. closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants