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]: NGINX proxy container not starting #3357

Closed
1 task done
benaissazaki opened this issue Jan 11, 2024 · 4 comments
Closed
1 task done

[bug]: NGINX proxy container not starting #3357

benaissazaki opened this issue Jan 11, 2024 · 4 comments

Comments

@benaissazaki
Copy link

benaissazaki commented Jan 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

I cloned the project on my machine by following exactly the steps in README.

All containers start and work correctly except plane-proxy.

This is what docker logs plane-proxy-1 outputs:
2024/01/11 17:08:40 [emerg] 1#1: invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf:22 2024-01-11T17:08:40.609447860Z nginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/nginx.conf:22

Steps to reproduce

  1. Clone the code locally using git clone https://github.com/makeplane/plane.git
  2. Switch to the code folder cd plane
  3. Open terminal and run ./setup.sh
  4. Run the docker command to initiate various services docker compose -f docker-compose-local.yml up -d
  5. Run docker run ps which outputs:
    image
  6. Run docker logs plane-proxy-1 which outputs:
    image

Browser

Other

Version

Local

@mguptahub
Copy link
Collaborator

Not sure if you are still facing this issue.

In case you are, then kindly share the log by running docker logs plane-proxy-1

@benaissazaki
Copy link
Author

Not sure if you are still facing this issue.

In case you are, then kindly share the log by running docker logs plane-proxy-1

I just retried it (after reinstalling the containers) and unfortunately it still persists with the same error logs as in my original message.

@abidkhan484
Copy link
Contributor

abidkhan484 commented Feb 19, 2024

closed #3296

@mguptahub
Copy link
Collaborator

closing this issue (refer: PR #3296)

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

No branches or pull requests

3 participants