Error setting up new SWAG ports dont seem to be open

Help
1

I have installed SWAG on docker this week, and it starts, but i cant access the default page

I ran this command:
docker create --name=swag
--cap-add=NET_ADMIN
--net=lsio
-e PUID=1000
-e PGID=1000
-e TZ=Europe/London
-e URL=myddns.ddns.net
-e SUBDOMAINS=www,ombi
-e VALIDATION=http
-p 6001:443
-p 6000:80
-v /home/docker/swag:/config
--restart unless-stopped
lscr.io/linuxserver/swag

It produced this output:

2023-02-24T20:16:45.118157254Z Generating new certificate
2023-02-24T20:16:46.864850428Z Saving debug log to /var/log/letsencrypt/letsencrypt.log
2023-02-24T20:16:47.667663156Z Requesting a certificate for myddns.ddns.net and 2 more domains
2023-02-24T20:16:50.442054859Z
2023-02-24T20:16:50.442089264Z Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
2023-02-24T20:16:50.442097449Z Domain: ombi.myddns.ddns.net
2023-02-24T20:16:50.442104743Z Type: dns
2023-02-24T20:16:50.442111596Z Detail: DNS problem: NXDOMAIN looking up A for ombi.myddns.ddns.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for ombi.myddns.ddns.net - check that a DNS record exists for this domain
2023-02-24T20:16:50.442138417Z
2023-02-24T20:16:50.442144659Z Domain: www.myddns.ddns.net
2023-02-24T20:16:50.442150670Z Type: dns
2023-02-24T20:16:50.442156722Z Detail: DNS problem: NXDOMAIN looking up A for www.myddns.ddns.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.myddns.ddns.net - check that a DNS record exists for this domain
2023-02-24T20:16:50.442163334Z
2023-02-24T20:16:50.442169245Z Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
2023-02-24T20:16:50.442175868Z
2023-02-24T20:16:50.645803499Z Some challenges have failed.
2023-02-24T20:16:50.645967248Z Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
2023-02-24T20:16:50.900586921Z ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

I can ssh into the docker container but running curl localhost:80 or 443 doesnt show it exist, i can ping IPs on network and google

my routers port forwarding works fine, as I have tested them against another conatiner that has a web page

I have been on the below
https://letsdebug.net/

http-01 both fail
dan-01 is ok

tls-alpn-01 fails

Im doing basic http, my dns hos my external IP and works for everything else

Any ideas what to try next?

2

For some reason you're concentrating on the latter part of the "The issue may be due to incorrect dns or port forwarding settings." message, while you should focus on the former part of the message: your DNS entries do not exist.

I'm pretty sure "myddns" is not the actual DDNS.net subdomain for your site, right? If you'd have used the questionnaire presented to you when you opened this thread in the Help section, you would have seen that providing the actual hostname of your site is mandatory to get help. Please fill out all the questions of the questionnaire to the best of your knowledge:

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

That said: I'm not sure you even can use sub-subdomains on a DDNS.net subdomain?

5 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.