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

Issues with Multiple Reverse Proxy #93

Closed
nazarhussain opened this issue Mar 3, 2016 · 7 comments
Closed

Issues with Multiple Reverse Proxy #93

nazarhussain opened this issue Mar 3, 2016 · 7 comments
Labels

Comments

@nazarhussain
Copy link
Contributor

I am facing problem with multiple reverse proxies. It is not functioning as per described in Readme.

I have following Procfile.

app: node app.js | bunyan
api: node api.js | bunyan

Now I run it with:

nf start -x 3000,4000 app=3,api=2

And the output that came out and cause error onward.

[WARN] No ENV file found
[OKAY] Trimming display Output to 136 Columns
[OKAY] Starting Proxy Server [app] 3000 -> (5000-5002)
[OKAY] Starting Proxy Server [api] 3000 -> (5000-5001)

As you can see cleary there are two issues:

  1. It does not pick right port group for right process, only uses first that was specified
  2. Second it uses same output port group for all jobs.

It seems something is clearly broken. Please help me out to troubleshoot the issue.

Thanks.

@nazarhussain
Copy link
Contributor Author

Any one had looked into this issue?

@nazarhussain
Copy link
Contributor Author

Just confirmed this bug is only in npm version 1.4.1 but is fixed in git repo. Please release the source code soon.

@rmg
Copy link
Member

rmg commented Apr 30, 2016

@nazarhussain you can install the pre-release that was published in November. It was tagged as next instead of latest so it isn't the default. Just do npm install -g foreman@next and you'll get most of the changes since 1.4.1.

@rmg
Copy link
Member

rmg commented Apr 30, 2016

I've just released v2.0.0-1 as the next tag. @nazarhussain if you are able to try it out and confirm, it would help with preparing a 2.0.0 final release.

@nazarhussain
Copy link
Contributor Author

@rmg will check it on Monday and let you know.

@nazarhussain
Copy link
Contributor Author

@rmg Yes it works. Thanks for working on this issue. Here is node repo that contains minimal code to test this issue. https://github.com/nazarhussain/foreman-multi-proxy-test/

rmg added a commit that referenced this issue May 8, 2016
The test setup is based on the behaviour described in #93, but with the
required modifications to support testing without using any fixed ports.
jdx pushed a commit to heroku/node-foreman that referenced this issue Aug 25, 2017
The test setup is based on the behaviour described in strongloop#93, but with the
required modifications to support testing without using any fixed ports.
@stale
Copy link

stale bot commented Jul 1, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 1, 2018
@stale stale bot closed this as completed Jul 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants