18 Nov 2012 4:31 PM #1
Cannot access support.sencha.com
Having bought the Sencha Complete, I am told in a email to activate it on support.sencha.com , but I cannot even access the site.
ping support.sencha.com, gives no answer. I can add the IP adress it resolves too, on request.
I already sent a email as suggested in the FAQ, but I am getting impatient. As I cannot find anyone else having same problem. Except a premium topic https://www.sencha.com/forum/showthread.php?t=245914 :Support Site is down Ext: Feature Requests
I have been unable to connect to support.sencha.com for the past few days, is there another way for us to access the subscriber only downloads?
Created: Saturday 13th October 2012 4:50pm | Score: 0.39533532
19 Nov 2012 6:04 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
I have been able to access it yesterday morning and this morning. I had not tried to access last night.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
19 Nov 2012 2:37 PM #3
I still cannot access it, from multiple devices, but I tried from my mobile phone which is in a complete different network, and it worked. This is very annoying, as it seems right now, I can only use support.sencha.com from my mobile phone network - sure I can connect that to my pc, but its very slow.
Could it be that my IP is banned by sencha??
Edit: it is solved, Apparently my Cablecom modem has a firewall which blocked the support site. Awkward cause it is the first time I have any problem with the firewall. Now having it changed to off from the setting 'low' , I can access support.sencha.com from my network.
Last edited by Civera; 19 Nov 2012 at 2:48 PM. Reason: Solved it.
23 Nov 2012 7:30 PM #4