seawall proxy route add
A proxy host in NPM for a stack, with its certificate.
A proxy host in NPM for a stack, with its certificate
A certificate seawall's NPM user owns that covers the domain, or a new Let's Encrypt one. It acts as seawall's own NPM user (seawall proxy login), never NPM's admin.
Usage
seawall proxy route add [OPTIONS] <STACK> <DOMAIN>
Changes the host
Without --yes it prints the plan and changes nothing.
Arguments
<STACK>The stack, by Portainer name or directory
<DOMAIN>The domain it answers on
Options
--to <CONTAINER:PORT>The container and port to forward to (default: the stack's one on the ingress network, and the one port its image exposes)
--websocketsLet websockets through
--allow <CIDR>Let only these addresses in, through an NPM access list (comma-separated IPs or CIDRs); needed for anything root on this host
--yesCarry out the plan (without it, this is a dry run)
Examples
seawall proxy route add blog blog.example.org
seawall proxy route add blog blog.example.org --yes
seawall proxy route add wiki wiki.example.org --to wiki-app-1:3000 --websockets --yes