I run OMV on a RockPro64 (4GB RAM).
OMV version 4.1.23-1 (Arrakis)
Kernel: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524
Processor: ARMv8 Processor rev 2 (v8l)
--
I tried to get Let's Encrypt running with DuckDNS following the TechnoDad tutorial (https://www.youtube.com/watch?v=TkjAcp8q0W0). Used the linuxserver dockers without any additional tags.
After running the Let's Encrypt docker, and running docker logs -f letsencrypt I get the following output. There we goo now:
root@rockpro64:~# docker logs -f letsencrypt
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 1000
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
generating self-signed keys in /config/keys, you can replace these with your own keys if required
Generating a RSA private key
..............+++++
..............+++++
writing new private key to '/config/keys/cert.key'
-----
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
Variables set:
PUID=1000
PGID=100
TZ=[Timezone]
URL=duckdns.org
SUBDOMAINS=[domain1,domain2,domain3,domain4,domain5]
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=true
DHLEVEL=2048
VALIDATION=http
DNSPLUGIN=
EMAIL=[emailaddress]
STAGING=
Created donoteditthisfile.conf
Creating DH parameters for additional security. This may take a very long time. There will be another message once this process is completed
Generating DH parameters, 2048 bit long safe prime, generator 2
This is going to take a long time
[.*+]
DH parameters successfully created - 2048 bits
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Only subdomains, no URL in cert
Sub-domains processed are: -d domain1.duckdns.org -d domain2.duckdns.org -d domain3.duckdns.org -d domain4.duckdns.org -d domain5.duckdns.org
E-mail address entered: [emailaddress]
http validation is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for domain1.duckdns.org
http-01 challenge for domain2.duckdns.org
http-01 challenge for domain3.duckdns.org
http-01 challenge for domain4.duckdns.org
http-01 challenge for domain5.duckdns.org
Waiting for verification...
Challenge failed for domain domain1.duckdns.org
Challenge failed for domain domain2.duckdns.org
Challenge failed for domain domain3.duckdns.org
Challenge failed for domain domain4.duckdns.org
Challenge failed for domain domain5.duckdns.org
http-01 challenge for domain1.duckdns.org
http-01 challenge for domain2.duckdns.org
http-01 challenge for domain3.duckdns.org
http-01 challenge for domain4.duckdns.org
http-01 challenge for domain5.duckdns.org
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: domain1.duckdns.org
Type: connection
Detail: Fetching
http://domain1.duckdns.org/.well-known/acme-challenge/[B1c]:
Timeout during connect (likely firewall problem)
Domain: domain2.duckdns.org
Type: connection
Detail: Fetching
http://domain2.duckdns.org/.well-known/acme-challenge/[C2d]:
Timeout during connect (likely firewall problem)
Domain: domain3.duckdns.org
Type: connection
Detail: Fetching
http://domain3.duckdns.org/.well-known/acme-challenge/[D3e]:
Timeout during connect (likely firewall problem)
Domain: domain4.duckdns.org
Type: connection
Detail: Fetching
http://domain4.duckdns.org/.well-known/acme-challenge/[E4f]:
Timeout during connect (likely firewall problem)
Domain: domain5.duckdns.org
Type: connection
Detail: Fetching
http://domain5.duckdns.org/.well-known/acme-challenge/[F5g]]:
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.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
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
Alles anzeigen
--
So I have an idea that this could be an issue with my router settings. My router is a ZyXEL VMG8324-B10A.
I go to Network Settings > NAT. There I found no existing rules.
I added two new rules following this scheme:
Service Name : Lets Encrypt (80 [/443])
WAN Interface : ADSL_via_[ISP]
WAN IP :
Trigger Start Port : 80 [/ 443]
End Port : 80 [/ 443]
Translation Start Port : 90 [/ 450]
Translation End Port : 90 [/ 450]
Server IP Address : 192.168.1.2
Protocol : TCP/UDP
I did nothing with the WOL settings.
When I saved the port forwarding for 80->90 I needed to confirm the following:
Since TCP port 80 is used.
The router WEB server port will be moved to 8080.
For the 443->450 rule it was:
Since TCP port 443 is used.
The router HTTPS server port will be moved to 4433.
In both cases I clicked to confirm.
What could be the problem here? Something with my Port Forwarding settings?
All the best,