SOLVED: ddnsclient and ispconfig

Discussion in 'ISPConfig 3 Priority Support' started by Turgut Kalfaoglu, Feb 19, 2025.

  1. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    Hello. In order to get ddnsclient and ispconfig addon working, I configured the client like:
    Code:
    # Configuration file for ddclient generated by debconf
    # /etc/ddclient.conf
    protocol=dyndns2 \
    use=web, web=http://checkip.dyndns.org/ \
    server=server.kalfaoglu.net:8080 \
    login=none \
    password='xxxxxxxxxxxxxxxxxxxxfd9' \
    host.kalfaoglu.net
    
    and the server from https://github.com/mhofer117/ispconfig-ddns-module
    which I just followed its readme and eventually created a token (which I put as password= above)

    When the client runs, it gets the IP address correctly, but the server always responds with Error 400.
    Code:
    (.........)
    INFO:     setting IP address to 3.14.14.26 for host.kalfaoglu.net
    UPDATE:   updating host.kalfaoglu.net
    CONNECT:  server.kalfaoglu.net:8080
    CONNECTED:  using HTTP
    SENDING:  GET /nic/update?system=dyndns&hostname=host.kalfaoglu.net&myip=3.14.14.26 HTTP/1.1
    SENDING:  Host: server.kalfaoglu.net:8080
    SENDING:  Authorization: Basic bm9xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk=
    SENDING:  User-Agent: ddclient/3.10.0
    SENDING:  Connection: close
    SENDING: 
    RECEIVE:  HTTP/1.1 400 Bad Request
    RECEIVE:  Date: Wed, 19 Feb 2025 19:22:17 GMT
    RECEIVE:  Server: Apache
    RECEIVE:  Content-Length: 126
    RECEIVE:  Connection: close
    RECEIVE:  Content-Type: text/html; charset=iso-8859-1
    RECEIVE: 
    RECEIVE:  <script>document.location.href='https://'+location.hostname+':'+location.port;</script><h1>Error 400 - trying to redirect
    
    There is nothing visible in /var/log/ispconfig/* , nothing in syslog. I'm not sure how to debug this at all.
    Any help would be appreciated.
    PS: Much of the data has been changed above for privacy.
     
  2. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    SOLVED:
    It turns out if I set the protocol to dyndns1 in the client, it works great :)
     

Share This Page