Archived from the Transloadit support forum. Originally posted on April 30, 2012; details may be outdated, see our docs for current behavior. Original thread
I am unable to get to the jQuery plugin. Did something change on your end?
Thanks,
Mark
Archived from the Transloadit support forum. Originally posted on April 30, 2012; details may be outdated, see our docs for current behavior. Original thread
I am unable to get to the jQuery plugin. Did something change on your end?
Thanks,
Mark
I have the same problem. I’ve tried to wget the plugin on several VPSs and dedicated servers in different locations but to no avail.
wget:
wget https://assets.transloadit.com/js/jquery.transloadit2.js
--2012-04-30 13:59:38-- https://assets.transloadit.com/js/jquery.transloadit2.js
Resolving assets.transloadit.com... failed: Name or service not known.
wget: unable to resolve host address `assets.transloadit.com'
But dig seems to get a valid DNS response:
dig assets.transloadit.com
; <<>> DiG 9.7.3 <<>> assets.transloadit.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46021
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;assets.transloadit.com. IN A
;; ANSWER SECTION:
assets.transloadit.com. 442 IN CNAME crm-151774863.us-east-1.elb.amazonaws.com.
;; AUTHORITY SECTION:
elb.amazonaws.com. 4 IN SOA ns-935.amazon.com. root.amazon.com. 1335790739 3600 900 7776000 60
;; Query time: 27 msec
;; SERVER: 192.168.16.4#53(192.168.16.4)
;; WHEN: Mon Apr 30 14:00:35 2012
;; MSG SIZE rcvd: 147
Same problema here ![]()
http://assets.transloadit.com/js/jquery.transloadit2.js should be available again.
Sorry for any inconvenience.
I can get it now.
What was it caused by? Is this something we will have to worry about in the future?
Thanks,
Mark
What was it caused by?
We did an infrastructure upgrade today, but we missed a critical DNS entry update : /.
Is this something we will have to worry about in the future?
No, this was a one time mistake. The jQuery plugin should always be hosted reliably on our end, this will not happen again.
Sorrry for the problems.
Felix Geisendörfer, co-founder
Closing this for now, please feel free to reopen the ticket and reply.