raaqi

Can't someone make a simple sync script to sort out all the expiry dates? Most of mine are wrong, and alot are just 00/00/00. I'm not a programmer but i know the DIT API is very good... anyone wanna give it a go?

Matt, Thanks. Changing the Next Due Date into the future worked. This was only domain registration, due date was 16/10/07, date paid was 16/10/07. Next due date was automatically set at today 16/10/07. Not sure why. I also bought the mobile addon for WHMCS today, logged in, looks great, works great. Loving it! Thanks a tonne!

How did you solve this? i'm having the same drama.

nice report. thanks!

solution? email support@distributeit.com.au and have the ip address whitelisted

DistributeIT API SAYS: 105 Request coming from incorrect IP address. IP Lock error. See section 1.1 1.1 AUTHENTICATION To connect to the Distribute IT API, the system needs to authenticate you as a valid user, and that the request is coming from a valid source. Account and User information is passed to ‘auth.pl’, which in turn will pass back a session ID. This session ID is then used with subsequent commands without having to authenticate each time. Each session ID will expire after a set period of time. If an error occurs an error response will be returned in place of the session ID. (see Appendix C for a list of valid error codes) We use a number of parameters to achieve this:  AccountNo: This is your Account Number used to access the Distribute IT service.  UserId: This is one of the users associated with your account.  Password: The current password that has been set for the above user. Additionally we force an IP lockdown, allowing only requests sent from IP addresses that you have Specified against the above account. Please ensure that after testing, all unnecessary IP addresses are removed so as to tighten up on security. Due to the nature of the IP lockdown all requests must come from a machine/s that has/have a fixed IP. You can have multiple sessions open, however the session ID will expire after fifteen minutes of Inactivity, you will then have to re-authenticate to receive a new session ID. See 3.7 Query KeepAlive for more information about ‘keeping alive’ this session ID. Command: Response: OK: (Session ID) or ERR: Error Code (see Appendix C for a list of valid error codes). This session id MUST be used with all future commands to the API.

I just set up domain rego with distribute it, whmcs keeps giving me this error. Anyone know what it is? An Error Occured ERR: 105 203.31.191.174