new swag

[theoneakta]

Hi

Seems the swag is not working right even on a fresh new server

I am able to make it run under the old developper branch but not master

Any idea?

it does not bind to port 80 at all... and inside the vm when doing curl on 8080 having a db issue... cannot connect to db...

[carlwillimott]

I’ve not tried this on a fresh install, but when I updated an existing project it worked without any issues for me personally. However, this was a couple of months ago now.

I would suggest perhaps trying a different image tag for swag and maybe even wordpress as they will pull the latest version and there could have been some breaking changes or something.

[theoneakta]

ok thanks Carl I will try that And the renew also fails, i think the path where it renews and the path of the certificate used are different I will fix that for myself manually 🙂

…

________________________________ From: Carl Willimott <[email protected]> Sent: Tuesday, December 29, 2020 3:47 PM To: carlwillimott/docker-compose-wordpress-ssl <[email protected]> Cc: theoneakta <[email protected]>; Author <[email protected]> Subject: Re: [carlwillimott/docker-compose-wordpress-ssl] new swag (#3) I’ve not tried this on a fresh install, but when I updated an existing project it worked without any issues for me personally. However, this was a couple of months ago now. I would suggest perhaps trying a different image tag for swag and maybe even wordpress as they will pull the latest version and there could have been some breaking changes or something. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSYJKABSV5MFT3AVGEPDRDSXI54TANCNFSM4VLWCRGA>.

[jphein]

I ran into this issue, and beat my head against the wall for several days. Thanks to the linux server swag discord channel I was able to figure out the culprit. ./default has to be renamed ./default.conf. Also, in the docker-compose.yml change - ./default:/config/nginx/site-confs/default to - ./default.conf:/config/nginx/site-confs/default.conf
You can read about it here: https://info.linuxserver.io/issues/2022-08-20-nginx-base/

Also, this implementation isn't supported by swag. There is an example .conf file for wordpress latest in the proy-confs folder for reference. Here is my first attempt at doing it the supported way. I haven't tested it yet. https://github.com/jphein/docker-compose-wordpress-ssl