Problem with creating LE-SSL Cert

[bobdig]

Steps to reproduce

1.Installed new ncvm today after fresh dl today
2.run it

Expected behaviour

It should create LE-SSL Cert

Actual behaviour

it is not doing it. Not in the initial setup process and not after manual start afterwards.

Is this correct?XXX ([y]es or [N]o): y
Checking if XXX exists and is reachable...
Doing a DNS lookup for XXX...
DNS seems correct when checking with nslookup!
DNS lookup failed with dig. The external IP (XXX) address of this serve r is not the same as the A-record.
Please check your DNS settings! Maybe the domain isn't propagated?
Please check https://www.whatsmydns.net/#A/XXX if the IP seems cor rect.
ncadmin@nextcloud:~$ Nope, it's not there. You have to create XXX and point

I use a subdomain (xxx.dyndns.org).
https://www.whatsmydns.net showed no problems.
Worked before. So there is something not ok.

[bobdig]

I was just curious, wanted to find out if the included setup for LE would allow for an wildcard cert, but it wont even do the setup, so I couldn't check it out at all. Would like to have such an option if possible, because I get my first own domain in a few days. ;)

[enoch85]

The script does checks to check if everything is prepared for the script to succeed. If things aren't setup correctly it will stop executing, by design.

That is so that you don't install any unnecessary packages, and is left with a failing setup. If the checks pass, it's almost guaranteed that it will work.

You could hash them out in the code just for testing though.

Wilcards should be supported with the DNS option which is implemented in the scripts as well.

[enoch85]

I can also add that I've made the checks stricter now than before, hence it might not proceed in some edge cases anymore.

[bobdig]

But I have no edge case, just a subdomain with dyndns. Tested it three times. Why you closed it?
I am a big fan of your work and recommend your vm when ever I can but how you handle issues is not ok. Last time I told you about a problem you sad you've tested it 5 times, 3 days later you apologized, because someone mailed you with the exact same problem...

[enoch85]

I was closing since the error says:

DNS lookup failed with X The external IP (XXX) address of this serve r is not the same as the A-record.

So in my world that means that the DNS isn't propagated yet.

The thing is also that I helped a customer yesterday with setting up SSL and it worked out of the box, and since nothing changed that tells me that it's a configuration issue on the end-users end.

I will run some tests and leave this open until I've confirmed it's working or not. Sorry for being so quick on the close button, I get theese types of reports from time to time, and in 99% of the cases, it's either:

1. Propagation not done yet
2. Some other error caused by the end-user.

[enoch85]

This is the logic if you want to test for yourself. Thanks. :)

[bobdig]

-not relevant-

[enoch85]

OK, so can you post the result of: http://mittip.se?

[bobdig]

-not relevant-

[bobdig]

-not relevant-

[enoch85]

What happens if you comment out (put a # in front) the test and run the script?

You can check open ports here: https://www.yougetsignal.com/tools/open-ports/, it seems like they are open and the script should recognize that in the second test.

[enoch85]

Also, since the IP now seems to be propagated, could you please test the original script "as is" just to check if the original issue was a propagation issue?

Thanks.

[bobdig]

What happens if you comment out (put a # in front) the test and run the script?

Hard for me to do, to be honest. Don't have the right to replace it. It also looks different then the link you gave before.

Also, since the IP now seems to be propagated, could you please test the original script "as is" just to >check if the original issue was a propagation issue?

It doesn't do it.

But there is one more thing I forgot to mention. Many Cable-ISP do, and so does mine, some sort of NAT, so that the Router can not see the external WAN-IP, but a 100.6something IP. So if your script also checks against the router, it will fail. But I as a user can open Ports with no problem. You can believe me, I am happy nextclouding with your vm for years and have no problem with WAN-Access. I can bring my original nextcloudingVm up, if you don't believe it. But I see, the new one is already up and reachable but without SSL. ;)