We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I'm trying to run beef behind apache reverse proxy.
Apache and beef run on the same machine. Requests to beef.my.domain:80 will be proxied to localhost:3000 (which is beef)
Problem is that hook.js tries to communicate to beef.my.domain:3000 (blocked by firewall) instead of beef.my.domain:80
How could I make hook.js aware of the proxy? Any suggestions?
Thanks
The text was updated successfully, but these errors were encountered:
The NAT configuration options in 'config.yaml' now also mention reverse proxies.
Closing this issue.
Sorry, something went wrong.
bcoles
No branches or pull requests
Hi,
I'm trying to run beef behind apache reverse proxy.
Apache and beef run on the same machine. Requests to beef.my.domain:80 will be proxied to localhost:3000 (which is beef)
Problem is that hook.js tries to communicate to beef.my.domain:3000 (blocked by firewall) instead of beef.my.domain:80
How could I make hook.js aware of the proxy? Any suggestions?
Thanks
The text was updated successfully, but these errors were encountered: