MIgrate from Letsencrypt to SWAG

Today it worked, don’t now why, I’m up with swag :slight_smile:

I am trying to migrate from linuxserver/letsencrypt to linuxserver/swag but just changing docker repository did not work for me… Is there more to it than just changing the repository? Using unRAID 6.12.6

i mean… 3 years ago it was just changing the repo… you’ve been running an unsupported/unmaintained container that has received no security updates for 3 years dude… lol

share your logs and compose/run

1 Like

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
───────────────────────────────────────

  β–ˆβ–ˆβ•—     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— 
  β–ˆβ–ˆβ•‘     β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β•β–ˆβ–ˆβ•—
  β–ˆβ–ˆβ•‘     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘
  β–ˆβ–ˆβ•‘     β•šβ•β•β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘
  β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•
  β•šβ•β•β•β•β•β•β•β•šβ•β•β•β•β•β•β•β•šβ•β• β•šβ•β•β•β•β•β• 

Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Certbot: link removed

To support LSIO projects visit:
link removed

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID: 99
User GID: 100
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=99
PGID=100
TZ=America/New_York
URL=asdf.asdf
SUBDOMAINS=***
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=true
VALIDATION=http
CERTPROVIDER=
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
DNSPLUGIN=cloudflare
EMAIL=*@gmail.com
STAGING=false
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
Using Let’s Encrypt as the cert provider
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
SUBDOMAINS entered, processing
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
Sub-domains processed are: *****
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
E-mail address entered: *@gmail.com
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
http validation is selected
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
Certificate exists; parameters unchanged; starting nginx
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
/config/nginx/ldap.conf exists.
Please apply any customizations to /config/nginx/ldap-server.conf
Ensure your configs are updated and remove /config/nginx/ldap.conf
If you do not use this config, simply remove it.
**** The following active 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 the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ old date β”‚ new date β”‚ path β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚ 2023-11-27 β”‚ /config/nginx/site-confs/default.conf β”‚
β”‚ 2018-08-10 β”‚ 2022-08-20 β”‚ /config/nginx/ldap-server.conf β”‚
β”‚ 2020-05-31 β”‚ 2023-04-27 β”‚ /config/nginx/authelia-location.conf β”‚
β”‚ 2020-05-31 β”‚ 2023-04-27 β”‚ /config/nginx/authelia-server.conf β”‚
β”‚ 2019-03-10 β”‚ 2023-08-13 β”‚ /config/nginx/ssl.conf β”‚
β”‚ 2019-04-07 β”‚ 2023-02-09 β”‚ /config/nginx/proxy.conf β”‚
β”‚ 2018-04-07 β”‚ 2023-04-13 β”‚ /config/nginx/nginx.conf β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default
[custom-init] No custom files found, skipping…
[ls.io-init] done.
Server ready
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] β€œstream” directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

If I had to guess, add .conf to defaults? <β€” NVM. it is already .conf

EDIT: logs are self explanatory… :smiley: I removed all the .conf files and renamed the conf.sample to .conf and it all started working.

Thanks.