Is there a way to get a letsencrypt certificate for the factory DDNS on the MT6000?


Oh yes, it’s working as per the print.

1 Like

You used upstream 1.1.1.1 with tls.
Can’t to test any dns over tls.
Compare adguard test showing connected dns over tls, but 1.1.1.1 showing not connected dns over tls.
You could test next Dns over tls and you will see no

I got DoT working

yes? Are you using upstream 1.1.1.1 with TLS (DoH, DoT, etc)
Mine not but Adguard is connected



Do you understand how to test with TLS?
TLS itself server router
TLS Cloudfrlare server
TLS Adguard server
TLS NextDNS server
etc…

you are right, using adguard for me shows as DoH. I got DoT alert when using GL script from router:

image

Guys, this is getting off topic here, maybe you can create a new thread or discuss via PM instead?

1 Like

Looks nice.

An idea: If I want DDNS and a LE cert, I think a HTTPS will work within the network (LAN).
So why not add an acme client on the Webserver and let handle everything within the httpd?

Because it’s nginx using lua scripts for the GL stuff.
And webroot is deprecated as an option for acme.sh :frowning:

You could make raspberry pi server. Turn off ddns router and turn on another server ddns from raspberry pi.

It didn’t work for me, could you check?

I know that my ISP blocks http and https ports, that’s why I always say DNS certificates

root@GL-MT6000:~# sh enable-acme.sh
Warning: This script could potentially harm your router!
This script will disable HTTP-only access to the router.
Do you want to continue? (y/N)
Y
Running opkg update ...
Installing luci-app-acme ...
Detected DDNS domain name: pm6ee86.glddns.com
Prefix of the DDNS domain name: pm6ee86
Deleting old ACME configuration file for pm6ee86 ...
Creating ACME configuration file ...
Disabling HTTP access to the router ...
Creating firewall rule to open port 80 on WAN ...
Restarting firewall ...
Warning: Section @zone[1] (wan) cannot resolve device of network 'wan6'
Warning: Section @zone[1] (wan) cannot resolve device of network 'wwan'
Warning: Section @zone[1] (wan) cannot resolve device of network 'secondwan'
Warning: Section @zone[2] (guest) cannot resolve device of network 'guest'
Warning: Option 'wgserver'.masq6 is unknown
Warning: Section 'wgserver' has no forward policy specified, using default
Warning: Option 'sambasharewan'.dest_proto is unknown
Warning: Section 'sambasharewan' does not specify a protocol, assuming TCP+UDP
Warning: Option 'sambasharelan'.dest_proto is unknown
Warning: Section 'sambasharelan' does not specify a protocol, assuming TCP+UDP
Warning: Option 'glnas_ser'.dest_proto is unknown
Warning: Section 'glnas_ser' does not specify a protocol, assuming TCP+UDP
Warning: Option 'webdav_wan'.dest_proto is unknown
Warning: Section 'webdav_wan' does not specify a protocol, assuming TCP+UDP
Warning: Section 'adguard_home' has no target specified, defaulting to DNAT
Warning: Section 'adguard_home_guest' has no target specified, defaulting to DNAT
Warning: Section @zone[2] (guest) has no device, network, subnet or extra options
 * Flushing IPv4 filter table
 * Flushing IPv4 nat table
 * Flushing IPv4 mangle table
 * Flushing IPv4 raw table
 * Flushing IPv6 filter table
 * Flushing IPv6 nat table
 * Flushing IPv6 mangle table
 * Flushing conntrack table ...
 * Populating IPv4 filter table
   * Rule 'Allow-DHCP-Renew'
   * Rule 'Allow-IGMP'
   * Rule 'Allow-IPSec-ESP'
   * Rule 'Allow-ISAKMP'
   * Rule 'Allow-DHCP'
   * Rule 'Allow-DNS'
   * Rule 'wgserver_allow'
   * Rule #12
   * Rule #13
   * Rule #14
   * Rule #15
   * Rule 'GL-ACME'
   * Redirect 'Adguard Home'
   * Redirect 'Adguard Home guest'
   * Forward 'lan' -> 'wan'
   * Forward 'guest' -> 'wan'
   * Forward 'wgserver' -> 'lan'
   * Forward 'wgserver' -> 'wan'
   * Forward 'lan' -> 'wgserver'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Populating IPv4 nat table
   * Redirect 'Adguard Home'
   * Redirect 'Adguard Home guest'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Populating IPv4 mangle table
   * Rule 'process_mark'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Populating IPv4 raw table
   * Zone 'lan'
     - Using automatic conntrack helper attachment
   * Zone 'wan'
   * Zone 'guest'
     - Using automatic conntrack helper attachment
   * Zone 'wgserver'
 * Populating IPv6 filter table
   * Rule 'Allow-DHCPv6'
   * Rule 'Allow-MLD'
   * Rule 'Allow-ICMPv6-Input'
   * Rule 'Allow-ICMPv6-Forward'
   * Rule 'Allow-IPSec-ESP'
   * Rule 'Allow-ISAKMP'
   * Rule 'Allow-DHCP'
   * Rule 'Allow-DNS'
   * Rule #12
   * Rule #13
   * Rule #14
   * Rule #15
   * Rule 'GL-ACME'
   * Forward 'lan' -> 'wan'
   * Forward 'guest' -> 'wan'
   * Forward 'wgserver' -> 'lan'
   * Forward 'wgserver' -> 'wan'
   * Forward 'lan' -> 'wgserver'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Populating IPv6 nat table
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_lan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_lan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_wan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_wan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_guest_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_guest_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_wgserver_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_wgserver_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_rule'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Populating IPv6 mangle table
   * Rule 'process_mark'
   * Zone 'lan'
   * Zone 'wan'
   * Zone 'guest'
   * Zone 'wgserver'
 * Set tcp_ecn to off
 * Set tcp_syncookies to on
 * Set tcp_window_scaling to on
 * Running script '/etc/firewall.user'
 * Running script '/etc/firewall.nat6'
 * Running script '/var/etc/gls2s.include'
   ! Skipping due to path error: No such file or directory
 * Running script '/usr/bin/gl_block.sh'
 * Running script '/etc/firewall.vpn_server_policy.sh'
iptables v1.8.7 (legacy): Couldn't load target `VPN_SER_POLICY':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Restarting nginx ...
Restarting acme ...
Due to some unkown reasons, we need to restart acme again ...
Checking if certificate was issued ...
Certificate was not issued. Please check the log file /var/log/acme/acme.log.

That’s not possible so far.

1 Like