Lets Encrypt Collabora Subdomain "resolver directive is duplicate

LSIO Discussion Container Support
1

nginx: [emerg] “resolver” directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:11

2

Do you really expect a sensible reply when that’s all you’ve given us?

You have a duplicate in line 11 is all I can tell you in the collabora.subdomain.conf file, and there isn’t a duplicate line in the version in our repo.

3

Sorry I was in a rush at the time let me clarify, I have collabora up so that the page says “OK”, I ran these commands:

cp collabora.subdomain.conf.sample collabora.subdomain.conf
docker restart letsencrypt

I changed the subdomain to office.* because I like it better, but changed it back to collabora (so that it is 100% untouched) with same result:

Line 11 is: resolver 127.0.0.11 valid=30s;

I also removed all the .sample files, pulled the latest image, then re-ran with a fresh one.

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name office.*;

include /config/nginx/ssl.conf;

resolver 127.0.0.11 valid=30s;
set $upstream_collabora collabora;

# static files
location ^~ /loleaflet {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Host $http_host;
}

# WOPI discovery URL
location ^~ /hosting/discovery {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Host $http_host;
}

# Capabilities
location ^~ /hosting/capabilities {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Host $http_host;
}

# main websocket
location ~ ^/lool/(.*)/ws$ {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $http_host;
    proxy_read_timeout 36000s;
}

# download, presentation and image upload
location ~ ^/lool {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Host $http_host;
}
# Admin Console websocket
location ^~ /lool/adminws {
    proxy_pass https://$upstream_collabora:9980;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $http_host;
    proxy_read_timeout 36000s;
}
}
4

Can you post your docker run/compose file for LetsEncrypt and full docker logs please

5

Commented it out and it worked.

6

I have the exact same config you posted and it works perfectly without commenting anything out. You have to have a duplicate somewhere else.

7

Where would that be? I have pasted the entire file above.

8

@linkthepirate I just posted PR to resolve the issue. in your particular setup the issue is because

include /config/nginx/ssl.conf;

resolver 127.0.0.11 valid=30s;

in ssl.conf line 27 that same resolver line is there. you can simply comment out the resolver line as you have, but a more appropriate fix would be to move the resolver line from the current location and put it inside each location block. This would allow you to modify the resolver line in the ssl.conf without impacting the ability of letsencrypt’s features to work properly.

the resolver changes were relatively recent and this was likely just missed.