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

allowing only a reverse proxy #182

Open
Dialgatrainer02 opened this issue Feb 18, 2024 · 1 comment
Open

allowing only a reverse proxy #182

Dialgatrainer02 opened this issue Feb 18, 2024 · 1 comment

Comments

@Dialgatrainer02
Copy link

Dialgatrainer02 commented Feb 18, 2024

hello, im curently running a reverse proxy setup with multiple containers in docker compose. I have a domain that the reverse proxy uses. I am planning on using authentication via the reverse proxy for all my apps.

However the reverse proxy can be bypassed by entering domain.com:port of specific container this is because my reverse proxy is on the same machine as my other services and i cant shut any ports via the router.

can i use whalewall to restrict the incoming request of all the container to the reverse proxy and would doing this prevent this kind of bypass?
im new to containerization and networking so sorry if its already stated elsewhere

one way that has worked before was to have the reverse proxy on a separate device and ip address but i cant do that anymore and i don't know how i can do that with docker

@capnspacehook
Copy link
Owner

Yes, you should be able to accomplish this by setting whalewall rules for the reverse proxy container and all containers behind the reverse proxy. You would only set mapped port rules and expose ports for the reverse proxy container and then all other containers wouldn't be able to be accessed directly.

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

2 participants