Just to clarify - you cannot serve Galaxy only to localhost over http
and configure Apache to do the SSL and load balancing? I am having a
hard time conceiving of a scenario where I would encourage someone to
have paste deal with the SSL instead of Apache - configuring that in
paste is not going to be as robust, well documented, or secure IMO.
If you really do need to serve paste via SSL - I am not sure what to
do next. I have no experience in configuring Apache to do this and I
have not heard of anyone else doing it (one can imagine it is a lot
harder to act as a proxy for a process when the traffic to and from
that process is encrypted).
On Wed, May 20, 2015 at 10:15 AM, Scott Szakonyi
In our situation we're required to serve Galaxy via SSL. I encountered
problems trying to do this with Paste processes. It appears that when Apache
load balancing sends an incoming request to one of the load balanced
processes, it's no longer under SSL.
Running uWSGI is not a preferred option, as our computing infrastructure is
not set up to support RedHat 7.
Thus, I either need to understand how to configure SSL to work with the load
balanced Paste processes, or run with another setup.
So, if anyone in the community has experience with getting SSL to work with
the Paste processes, or with setting up some other sort of SSL friendly
configuration, I'd appreciate it if you would share your experience.
Scott B. Szakonyi
Center for Research Computing
107 Information Technology Center
Notre Dame, IN 46556
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: