SWAG validation

[pm1961]

Hi,

 

I hope this fits in the general category.....

 

I'm trying to setup Swag but can't get past the initial setup. I find the following error when I check the log files.

 

I must add that I have DuckDNS working fine on my PC/Server/pfSense and I have OpenVPN also working flawlessly.

 

I can also successfully ping my DuckDNS address from the server console..... I think that tells me that I don't have a problem either with DNS or Port Forwarding....

 

Or is that too simplistic?

 

TIA

 

Paul

 

 

 

 

Challenge failed for domain pm1961nextcloud.duckdns.org
http-01 challenge for pm1961nextcloud.duckdns.org
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: pm1961nextcloud.duckdns.org
Type: connection
Detail: Fetching
http://pm1961nextcloud.duckdns.org/.well-known/acme-challenge/l989LN5Is6-ZQZlkyOb34c3NOlBO45SaUdEZnVq2aAg:
Timeout during connect (likely firewall problem)

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
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

Edited December 2, 2020 by pm1961

[dgs2001]

pm1961

 

did you get this sorted?

 

One thing I have noticed previously with swag / docker / unraid / duckdns / cloudflare / pfsense ... etc

 

When making changes or getting things set up it takes time for dns changes to propogate throught the various interfaces etc.

I have countless times been looking for problems that simply dissapear when all the networkimng interfaces catch up with themselves.

 

 

Nowadays as somebody who tinkers if I am changing things to do with or that require dns and forwarding I tend to reboot my pfsense box and my pc before checking whether things are working.

 

I am sure there are commands that will release and renew leases and dns but i just find its simpler to reboot and then I know its not a cached dns problem.

 

dgs2001

[pm1961]

Thanks for the reply,

 

No, unfortunately not yet.....

 

My system is in pieces at the moment. I've just acquired a rack to rehome/tidy the rats nest that my attic has become!

 

The reboot will be an opportune time to see if that works for me.

 

ATB