No. I'll clarify. I'm no longer trying to use an Amazon elastic load balancer. I ended up terminating SSL right at Jenkins (local SSL cert). The iptables rule allows me to run the Jenkins [Java] process as a non-root user bound to a high port (8443), but still expose only port 443 (the standard port for the HTTPS scheme) to the Internet.
On Wed, Nov 27, 2013 at 10:07 AM, Dustin O'Brien <[email protected]> wrote: > Adam, > > This allowed you to setup you initial goal of an ELB terminating SSL and > forward to jenkins only listening on http? Can you elaborate if so? > > Dustin > > > On Friday, April 26, 2013 4:57:01 PM UTC-4, Adam Monsen wrote: >> >> I used this instead: >> >> iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports >> 8443 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
