Compatibility with Node 6.9.2? about thailand-post HOT 7 CLOSED

@siamkreative Hi, sorry for the slow response. This might caused from the outdated soap package. I'll get back to you when I have a chance to try it out on latest version of Node. For now you can try updating the soap package.

from thailand-post.

No worries, take your time. I actually think that the issue comes from my setup... Locally, my small app runs fine with Node.js 7.0.0 and npm 3.10.8 but it leads to a 503 on my DigitalOcean droplet.

Because I have limited DevOps experience, I have been trying to figure this out for a week...

from thailand-post.

If I remove trackService, the server runs without a problem instead of timing out.

from thailand-post.

Hi, I just tested locally and everything seems to work fine. My bet is that they (thailandpost server) have blacklisted all connections from VPS providers like DigitalOcean, which makes the client unable to reach through SOAP. Again that is just a guess, I will investigate further and try it with VPN or something. Sorry for the late reply.

from thailand-post.

UPDATE

@siamkreative The problem seems to be related to the machine's timezone which caused the keygen to generate the wrong PublicXmlKey. I released version 2.1.0 to fix this bug.

Now I've successfully run demo.js in DigitalOcean SGP1 on Node v7.4.0.

from thailand-post.

Thanks I will try asap :)

from thailand-post.

How can I contact you? I am unable still unable to run my app on DigitalOcean (using the default node.js image). Maybe there is some firewall issues that I am not aware of?

from thailand-post.