You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have caddy installed via opnsense on its own machine and would like to use it to proxy traffic for all of the servers in my network. on each server i have docker containers running, but i don't want to expose all of their ports in order for my opnsense caddy machine to be able to proxy to them.
if i set up docker-socket-proxy, can i limit the access to only my opnsense machine and then direct all of the caddy reverse proxy configurations to it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i have caddy installed via opnsense on its own machine and would like to use it to proxy traffic for all of the servers in my network. on each server i have docker containers running, but i don't want to expose all of their ports in order for my opnsense caddy machine to be able to proxy to them.
if i set up docker-socket-proxy, can i limit the access to only my opnsense machine and then direct all of the caddy reverse proxy configurations to it?
Beta Was this translation helpful? Give feedback.
All reactions