Thanks Christofer.I am not sure what new information Telnet client would give us, it is the same as testing any other way of access - it will be difficult to separate the issue of my network being firewalled (problem with my network) and remote server being too busy (timeout of connection).It turned out it was my network - a firewall was patched and the 6868 is no longer usable for me.Thanks again for suggestions and help,Nikolay On Thursday, July 2, 2015 11:33 AM, Christopher Cook <christopher.cook@webprofusion.com> wrote: If you ever need to test your connection to anything (web/smtp/databases etc) try using a telnet client (an installable feature on windows) telnet <hostname> <port> If you get a timeout then the host or port is not accessible to you (firewalled). A blank screen on the other hand indicates a successful connection. Chris Sent from my Samsung Galaxy smartphone.-------- Original message --------From: Nikolay Shishkov <nshishkov@yahoo.com> Date: 01/07/2015 11:01 am (GMT+00:00) To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] web api I was able to log in fine from another network... I will chase down if it is our IT or the internet provider that is blocking traffic.Thanks again for the help,Nikolay On Wednesday, July 1, 2015 11:54 AM, Nikolay Shishkov <nshishkov@yahoo.com> wrote: Thanks Mark, I am getting ERR_CONNECTION_TIMED_OUT I will try from another network... I am starting to have a suspission that our IT blocked some ports... Nikolay On Wednesday, July 1, 2015 11:49 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Here’s my test: $ curl -s -X GET -c ~/Downloads/ovms-cookie -v "https://tmc.openvehicles.com:6869/api/cookie?username=USER&password=PASSWORD... Hostname was NOT found in DNS cache* Trying 54.243.136.230...* Connected to tmc.openvehicles.com (54.243.136.230) port 6869 (#0)* TLS 1.2 connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA256* Server certificate: tmc.openvehicles.com* Server certificate: COMODO RSA Domain Validation Secure Server CA* Server certificate: COMODO RSA Certification Authority* Server certificate: AddTrust External CA Root> GET /api/cookie?username=USER&password=PASSWORD HTTP/1.1> User-Agent: curl/7.37.1> Host: tmc.openvehicles.com:6869> Accept: */*>* HTTP 1.0, assume close after body< HTTP/1.0 200 Authentication ok< Content-Type: text/plain< Expires: Wed, 01 Jul 2015 09:46:18 GMT* Added cookie ovmsapisession=“<REDACTED>" for domain tmc.openvehicles.com, path /api/, expire 0< Set-Cookie: ovmsapisession=<REDACTED>< Connection: close< Cache-Control: max-age=0< Content-Length: 9< Access-Control-Allow-Origin: *< Date: Wed, 01 Jul 2015 09:46:18 GMT<Login ok Also tried 6868 for http, and ok. What is the error you are getting? Regards, Mark. On 1 Jul, 2015, at 5:41 pm, Nikolay Shishkov <nshishkov@yahoo.com> wrote: The following one:http://tmc.openvehicles.com:6868/api/cookie Should I use another one? On Wednesday, July 1, 2015 11:39 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Seems ok for me. What URL are you using? On 1 Jul, 2015, at 4:25 pm, Nikolay Shishkov <nshishkov@yahoo.com> wrote: Hi Mark, The web api seem to be inaccessible. Is it me or is it the server? Nikolay_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev