Page 2 of 3

Re: Posting Json values from different application

Posted: Mon Jul 23, 2018 12:20 pm
by davidtrillo
I do not get any response from the API at all.

I have updated all my .net frameworks to ensure I am sending TLS1.2 and I am cofident the script is correct.

Is there any chance that the IP address I will be using in Sri Lanka are in some way blocked by the API rules. I have set any IP address on my Beds24 configuration but maybe youare doing some high level whitelisting.

I have send the code to a friend in the UK who is using the same POS system and he has tested from the UK and it works perfectly. Is there some geo tag or IP group that prevents this working.

My Public IP is 112.134.151.61 although i do not have a static IP, this is generated by my ISP

Re: Posting Json values from different application

Posted: Mon Jul 23, 2018 1:46 pm
by markkinchin
The IP whitelisting can be set by you for the APIKey at menu Settings > Account > Account Access

Can you get it to work if you disable the whitelist for your ApiKey?

Re: Posting Json values from different application

Posted: Mon Jul 23, 2018 3:13 pm
by davidtrillo
I have whitelist switched off. It should work with any IP address.

I wondered if beds24 applied a higher level of access particularly to particular geographic areas. As I deatiled in the previous posting, i have tested the same script, from the same POS system through a PC located in the UK and this worked. The test returned a good connection and the script updated Beds24 as intended. From here I get nothing, not even an error message.

I have experienced other systems needing to be activated for my region (Sri Lanka). Just wondering if this is also the case for your API. Access to Beds24 is not affected and I can use the system fine except for this Integration.

Re: Posting Json values from different application

Posted: Tue Jul 24, 2018 7:27 am
by markkinchin
There is no specific geo blocking policy in place.

Do you get a response if you ping api.beds24.com from your server?

Re: Posting Json values from different application

Posted: Tue Jul 24, 2018 8:39 am
by davidtrillo
I have just tried to ping both the following

www.api.beds24.com

www.beds24.com/api/

api.beds24.com/json/modifyProperty

On all these it says the ping request cannot find the host.

I can access through a browser no problem.

Re: Posting Json values from different application

Posted: Tue Jul 24, 2018 9:17 am
by markkinchin
Perhaps it is the DNS on your server, try putting the domain and IP address in your hosts file

Re: Posting Json values from different application

Posted: Tue Jul 24, 2018 10:45 am
by davidtrillo
Well I can ping api.beds24.com and www.beds24.com and they work.

However if I try to ping www.beds24.com/api/ this does not work. Neither will api.beds24.com/json/modifyProperty/

Respose is host not reachable.

Re: Posting Json values from different application

Posted: Tue Jul 24, 2018 11:10 am
by markkinchin
ping will only work on the domain. If the following work from your server, then you are not being blocked.

ping www.beds24.com

ping api.beds24.com

Re: Posting Json values from different application

Posted: Thu Aug 16, 2018 6:50 am
by davidtrillo
I am still experiencing issues with access to the API from my POS application.

I have spent a long time ensuring that TLS 1.2 is set and I now seem to get some communication going. I am monitoring on Netmon and seem to get an encrypted Alert responce - maybe a Cipher issue?

I get a client hello and a response back from the api
i get TLS:TLS Rec Layer-1 HandShake: Client Key Exchange.; TLS Rec Layer-2 Cipher Change Spec; TLS Rec Layer-3 HandShake: Encrypted Handshake Message.
followed by TLS:TLS Rec Layer-1 HandShake: Encrypted Handshake Message.; TLS Rec Layer-2 Cipher Change Spec; TLS Rec Layer-3 HandShake: Encrypted Handshake Message.
Then some data interchange finally get the following
TLS:TLS Rec Layer-1 Encrypted Alert


Any ideas if this is a valid post or what the problem may be.

Re: Posting Json values from different application

Posted: Thu Aug 16, 2018 7:50 am
by markkinchin
I found this by googling your error.

https://blogs.msdn.microsoft.com/tdever ... ted-alert/

It sounds like there may still be a weak Cipher being used by your application