Remote API issue

Discussion in 'ISPConfig 3 Priority Support' started by Petr Šponer, Jun 26, 2021.

  1. Petr Šponer

    Petr Šponer New Member HowtoForge Supporter

    Hi, I am experiencing a strange issue. I am using the remote API. Works fine on an old server (3.1.14p2). However I installed a new server (3.2.2) recently and updates are not working even when they seem to be ok. Read(get) works fine however when I call for example dns_a_update I get "Response 200 OK" but no update in the db, no indication in UI anything has changed. Any idea what the issue is or how to debug it?
    19:57:22.428 [main] DEBUG org.springframework.web.client.RestTemplate - HTTP POST
    19:57:22.428 [main] DEBUG org.springframework.web.client.RestTemplate - Accept=[text/plain, application/json, application/*+json, */*]
    19:57:22.428 [main] DEBUG org.springframework.web.client.RestTemplate - Writing [{"session_id":"49858e4705914d582b906adf10d112f1","primary_id":"4260","params":{"sysPermOther":"","sysPermGroup":"riud","data":"","aux":"0","stamp":"2021-06-13 11:24:57","active":"Y","type":"A","serverId":"1","ttl":"3600","zone":"4260","serial":"2021061307","name":"","sysUserid":"2","id":"26916","additionalProperties":{},"sysPermUser":"riud","sysGroupid":"2"},"client_id":"2"}] with org.springframework.http.converter.StringHttpMessageConverter
    19:57:22.477 [main] DEBUG org.springframework.web.client.RestTemplate - Response 200 OK
    Last edited: Jun 26, 2021
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I would install the latest ISPConfig before further debugging. Current version is 3.2.5. you wrote you have server (3.2.2).
  3. Petr Šponer

    Petr Šponer New Member HowtoForge Supporter

    Well, with the latest ISPConfig 3.2.5 the issue is the same :-(
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    The fields you pass have wrong names, e.g. you pass:


    but the field name is server_id, there is no camel case used in database field names. Seems as if you somehow automatically converted underscores to camelcase and this broke various field names. There have been no changes on ISPConfig's side as far as I know, at least the tools we use like the migration tool work fine with 3.1 as well s 3.2 versions.
    ahrasis likes this.

Share This Page