Just thought I'd follow up, even though it's been a few days. See
below...
On Tue, 2012-09-18 at 10:54 +0200, Robin Baumgartner wrote:
> Here is our configuration for nginx, maybe it helps:
>
Thanks for the reply--it was actually very helpful!
> server {
> listen 8000;
> server_name <SERVER_NAME>;
>
> ssl on;
> ssl_certificate <PATH_TO_CERT>;
> ssl_certificate_key <PATH_TO_KEY>;
>
> location / {
> proxy_pass http://<SERVER_IP>:8000;
> }
> }
>
Perhaps I just needed more sleep or a fresh look, because it never came
to mind to do the most absolute minimal configuration like this! I had
a "template" site config to do reverse proxy that had many more settings
concerning keep-alive, timeouts, injecting extra headers and so forth.
The template was modeled on the way it was done in countless examples
shown on wikis and forums.
Though it worked in non-SSL it seems that those settings combined with
SSL made Tryton not work (though I have not determined the root cause).
Perhaps once I have this install fully set up I shall contribute a
"recipe" to build my setup as documentation to the Tryton site. It has
been noted that there are few who offer Tryton as a hosted
service--perhaps if those of us do so (or aspire to) did a "Tryton
Hosting Cookbook" it might spur some adoption of Tryton (if all goes
well I might offer such a service in western Canada and US where I live)
--
--
[email protected] mailing list
