# Error using DDNS by noip **URL:** \ **Category:** Help\ **Created:** [November 4, 2017, 1:28pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640 "2017-11-04T13:28:20Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![angelodl](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@angelodl](https://community.letsencrypt.org/u/angelodl)\ **Post date:** [November 4, 2017, 1:28pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/1 "2017-11-04T13:28:20Z")
Hi, I’m trying to get my own private cloud, working fine with access on port 80. However I need SSL authentication but any tutorial I found online didn’t work. Please help… My domain name (DDNS): [asds.noip.me](http://asds.noip.me) I set up a VPS with apache on ubuntu 16.04, nextcloud as cloud server. Port 80 and 443 open on my router firewall. I tried several commands including: 1)sudo letsencrypt --apache --agree-tos --email [struzzoang@gmail.com](mailto:struzzoang@gmail.com) -d [asds.noip.me](http://asds.noip.me) 2)sudo certbot --apache -d [asds.noip.me](http://asds.noip.me) 3)sudo apt-get install software-properties-common sudo add-apt-repository ppa:certbot/certbot sudo apt-get update sudo apt-get install python-certbot-apache sudo certbot --apache What I get is always: "Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for [asds.noip.me](http://asds.noip.me) Enabled Apache ssl module Waiting for verification… Cleaning up challenges Failed authorization procedure. [asds.noip.me](http://asds.noip.me) (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Error getting validation data IMPORTANT NOTES: - The following errors were reported by the server: ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [November 4, 2017, 6:28pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/2 "2017-11-04T18:28:35Z")
The TLS-sni-01 challenge requires port 443. Ensure your firewall is allowing port 80 and 443 inbound. And place a test.txt file (with minimal content) in the challenge folder for testing: [asds.noip.me/.well-known/acme-challenge/test.txt](http://asds.noip.me/.well-known/acme-challenge/test.txt) ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [November 4, 2017, 7:30pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/3 "2017-11-04T19:30:04Z")
> [@rg305](#): > > And place a test.txt file (with minimal content) in the challenge folder for testing: > > [asds.noip.me/.well-known/acme-challenge/test.txt](http://asds.noip.me/.well-known/acme-challenge/test.txt) That won't affect or predict the success of `--apache` because `--apache` only uses TLS-SNI-01, not HTTP-01 challenges. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [November 4, 2017, 8:10pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/4 "2017-11-04T20:10:34Z")
True, but it could verify the path to the file is correct (at least via HTTP) ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [November 4, 2017, 8:26pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/5 "2017-11-04T20:26:10Z")
This is still a less relevant test because there is no file, nor `/.well-known` directory, nor use of a webroot, nor even a completed HTTP request, in TLS-SNI-01. It only creates a self-signed certificate and does not perform a full web request. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [November 4, 2017, 8:36pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/6 "2017-11-04T20:36:26Z")
I have much to learn, sensei ---
**Author:** ![angelodl](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@angelodl](https://community.letsencrypt.org/u/angelodl)\ **Post date:** [November 6, 2017, 4:52pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/7 "2017-11-06T16:52:16Z")
Many thanks for your reply! I checked using [https://www.yougetsignal.com/tools/open-ports/:](https://www.yougetsignal.com/tools/open-ports/:) ports 443 and 80 are open I couldn’t find a “acme-challenge” folder on my root partition or /var/www folder. So I made one new folder ([asds.noip.me/.well-known/acme-challenge/](http://asds.noip.me/.well-known/acme-challenge/)) and put a simple test.txt on it; then chowned using www-data:www-data. I tried to point it from outside: "The requested URL /.well-known/acme-challenge/test.txt was not found on this server." [http://asds.noip.me/.well-known/acme-challenge/test.txt](http://asds.noip.me/.well-known/acme-challenge/test.txt) Sorry, I’m an absolute beginner, I may have misanderstood your suggestion! We need this to share mediacal research stuff (mainly using nextcloud) and set up a stata software server - but we are stuck with SSL authentication. ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [November 6, 2017, 5:21pm UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/8 "2017-11-06T17:21:04Z")
Hi @angelodl, The thing I was discussing above is that the `acme-challenge` directory is only relevant if you use `--webroot`, not if you use `--apache`. The `--webroot` method is less automated than the `--apache` method; for example, it doesn’t install your certificate for you. The experiment you tried shows that `--webroot` won’t work either (without figuring out and fixing whatever went wrong), but it doesn’t explain the error that you saw with `--apache`. I think that error is most likely explained by a firewall (either a network-based firewall or a host-based firewall) dropping the inbound connections to port 443. ---
**Author:** ![angelodl](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@angelodl](https://community.letsencrypt.org/u/angelodl)\ **Post date:** [November 7, 2017, 10:09am UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/9 "2017-11-07T10:09:28Z")
Weird, this is beyond my possibilities, actually I’m a newbie. I can ssh using port 443 from outside, and my lamp-stack is “standard”. I tried to stop my router firewall, no luck. I’m using the main ISP in Italy (Tim), so that shouldn’t be an issue. I may try to reinstall the system, but this would be a panic! Thank you A ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [November 7, 2017, 10:43am UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/10 "2017-11-07T10:43:40Z")
> [@angelodl](#): > > I can ssh using port 443 from outside, and my lamp-stack is “standard”. _That's_ the issue. Port 443 is OpenSSH. Port 443 needs to be Apache. You need to move OpenSSH to a different port, or use a multiplexing program like `sslh` so that OpenSSH and Apache can share the port. (Apache and Certbot would have to be configured carefully, though.) ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [December 7, 2017, 10:43am UTC](https://community.letsencrypt.org/t/error-using-ddns-by-noip/45640/11 "2017-12-07T10:43:48Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.