I am attempting to use SWAG to get valid certs for my Nextcloud installation. I am using docker containers provided by Linuxserver (frankly, they are so far better than most others for many reasons!) using a docker-compose.yaml file that is based on examples provided at
The docker-compose.yml I am using (with redactions of sensitive information) is listed below:
image: Package swag · GitHub
Note that in a departure from the example, I am using http as my validation. The example uses duckdns,but I have no key for that and according to the documentation I can use http to get regular certs through certbot. Also: I own the domain.
When I do a docker-compose up, everything starts smoothly. SWAG successfully gets its cert from LetsEncrypt, the database starts up without problems, and Nextcloud starts up. The startup log I have is somewhat long, so I will include it in a seperate post if someone thinks they need to see it.
I am encountering two problems:
Despite the successful acquisition of the valid cert and key from LetsEncrypt, when I access my system I get the “invalid cert” warning. It is as if the installed valid cert is invisible to the system.
When I click on “advanced” and select "continue to page (unsafe), the front page I get is not Nextcloud! I get a page that says “Welcone to SWAG”. My Nextcloud container is running but is invisible.
Aside from the use of http as my validator, I am following the example provided for the SWAG setup. Am I missing something? Is there a typo somewhere in my docker-compose.yml file? Or is there something else I need todothat is not covered in the examples?
Someone lease advise.