What's new

DDNS Afraid + WOW = WOW KO + error log

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

BEF33

Occasional Visitor
Hello everyone,

I have got a NAS synology and a router Asus RT-AC88U with asuswrt-merlin
My DDNS synology was wrong for WOW my NAS.
So I used the guide DDNS Afraid for asuswrt-merlin of htpc guides
It was working well yesterday and today it goes wrong with error in the router log.
If I made a modification of the hostname, it works again but log errors remains....
More over it seems that the host name must not include number. and mine do.
So I think I'm going to try to create another one without number....
Could you please help me ?
FB

the router log:
Feb 16 16:30:02 kernel: /usr/sbin/acme-client: fc88u.ignorelist.com (freedns.afraid.org): bad domain syntax
Feb 16 16:35:00 rc_service: service 15491:notify_rc restart_letsencrypt
Feb 16 16:35:02 kernel: /usr/sbin/acme-client: fc88u.ignorelist.com (freedns.afraid.org): bad domain syntax
Feb 16 16:36:50 dnsmasq-dhcp[300]: DHCPREQUEST(br0) 192.168.110.105 45:10:b5:10:f4:78
Feb 16 16:36:50 dnsmasq-dhcp[300]: DHCPACK(br0) 192.168.101.102 45:08:b1:10:f4:78 Chromecast-Ultra
Feb 16 16:40:00 rc_service: service 15725:notify_rc restart_letsencrypt
Feb 16 16:40:02 kernel: /usr/sbin/acme-client: fc88u.ignorelist.com (freedns.afraid.org): bad domain syntax
Feb 16 16:45:00 rc_service: service 15955:notify_rc restart_letsencrypt
Feb 16 16:45:02 kernel: /usr/sbin/acme-client: fc88u.ignorelist.com (freedns.afraid.org): bad domain syntax
Feb 16 16:46:12 WLCEVENTD: eth2: Assoc 14:8G:3C:E2:C2:36
Feb 16 16:46:13 dnsmasq-dhcp[300]: DHCPDISCOVER(br0) 14:f9:c3:d1:d4:63
Feb 16 17:45:00 rc_service: service 19295:notify_rc restart_letsencrypt
Feb 16 17:45:10 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 16 17:45:10 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
Feb 16 17:50:00 rc_service: service 19540:notify_rc restart_letsencrypt
Feb 16 17:50:12 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 16 17:50:12 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
Feb 16 17:55:00 rc_service: service 19774:notify_rc restart_letsencrypt
Feb 16 17:55:20 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acm...2682921773: bad response
Feb 16 17:55:20 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://fc88u.ignorelist.com/.well-know...yKODFxmLMg: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/fwXj9eaZKg-7VYNs92zf77dw/12682921773", "token": "Ky1S5gXNiNFsyCT
Feb 16 18:00:01 rc_service: service 20029:notify_rc restart_letsencrypt
Feb 16 18:00:08 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 16 18:00:08 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top