On 02/15/2014 09:16 AM, Rob Kemp wrote:
> On 02/14/2014 09:02 PM, mayak wrote:
>> On 02/14/2014 07:30 PM, Rob Kemp wrote:
>> <snipHi Rob,
>>
>> If I have understood you correctly, you probably want use to use virtual
>> hosts:
>>
>> a.domain.com
>> b.domain.com
>> c.domain.com
>>
>> Each of these would have a `container` describing SSL certs, home
>> directory, etc ...
>>
>> Cheers
>>
>> M
>
> That's right, and with a, b, and c being the same domain. I've tried
> to set it up that way, but on restarting nginx the non-SOGo virtual
> hosts throw up a warning that they are duplicates and are being
> ignored. I'll go back to the nginx documentation.
>
> Thanks
>
> Rob
Hi Rob,
a) verify DNS -- that you have these named resolving correctly
b) each nginx container should look something like this (i keep these in
separate .conf files) -- make sure `server_name` is unique across your
config files -- make sure confs are readable by nginx user:
server {
listen 443;
server_name sogo.domain.com;
access_log /var/log/nginx/sogo-access.log;
error_log /var/log/nginx/sogo-error.log;
location ^~ /SOGo {
}
}
server {
listen 443;
server_name redmine.domain.com;
access_log /var/log/nginx/redmine-access.log;
error_log /var/log/nginx/redmine-error.log;
location / {
}
}
server {
listen 443;
server_name another.domain.com;
access_log /var/log/nginx/another-access.log;
error_log /var/log/nginx/another-error.log;
location / {
}
}
c) post the error message here in the forum
thanks
m
--
[email protected]
https://inverse.ca/sogo/lists
