January 15, 20224 yr ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Europe/Athens URL=xrism.ro SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=dns CERTPROVIDER= DNSPLUGIN=cloudflare STAGING=false Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing Wildcard cert for xxxxxxx.xxx will be requested E-mail address entered: [email protected] dns validation via cloudflare plugin is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] 60-renew: executing... The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). [cont-init.d] 60-renew: exited 0. [cont-init.d] 70-templates: executing... **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/collabora.subdomain.conf [cont-init.d] 70-templates: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 Server ready nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6
February 21, 20233 yr Hey not sure if this is still a problem for you, but an update to swag broke the same thing for me. Here's what I did to fix it: Launch to web console from your server's webUI Type the following commands: cd /mnt/user/appdata/swag/nginx/proxy-confs mv collabora.subdomain.conf collabora.subdomain.conf.old cp collabora.subdomain.conf.sample collabora.subdomain.conf Edit anything in the config file if needed (like if your subdomain isn't exactly collabora.your-domain.com or something) Restart swag and you should be good to go!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.