A Million thanks for providing the UTC time option!!!
You're welcome. Click time in right-bottom corner could switch the time zone quickly.
|
|
|
Refresh the page will return the correct data. I have no idea how it happens and it's really rare case, only met twice in all time and seems only happens on Bitstamp. It cannot repeatable so still have no solution to solve it.
|
|
|
I've contacted CloudFlare. It seems they have the issue on ssl certificate replication, now it should be work. Please contact me if the issue still exists. it works perfectly now thanks buddy! Good.
|
|
|
I've contacted CloudFlare. It seems they have the issue on ssl certificate replication, now it should be work. Please contact me if the issue still exists.
|
|
|
Add huobi LTC
Huobi LTC API is not ready yet.
|
|
|
This is exactly what I'm getting also. Not sure if it's useful, but here is a dump of the SSL cert being sent out. Could you provide the traceroute result? My network Tracing route to bitcoinwisdom.com [198.41.184.235] over a maximum of 30 hops: 1 5 ms 3 ms 4 ms DD-WRT [192.168.1.1] 2 * * * Request timed out. 3 12 ms 21 ms 23 ms 69-50-160-1.westerncable.ca [69.50.160.1] 4 88 ms 93 ms 82 ms 69-50-161-2.westerncable.ca [69.50.161.2] 5 142 ms 530 ms 81 ms 66.51.143.33.vrt.2tp.static.cipherkey.com [66.51.143.33] 6 23 ms 43 ms 39 ms 208.110.96.26.core25668.cipherkey.com [208.110.96.26] 7 92 ms 85 ms 92 ms 67.69.228.189 8 17 ms 17 ms 17 ms core1-vancouver_POS3-0.net.bell.ca [64.230.248.57] 9 37 ms 42 ms 29 ms core3-vancouver_pos0-0-0.net.bell.ca [64.230.183.26] 10 32 ms 30 ms 22 ms core2-seattle_pos13-1-0.net.bell.ca [64.230.77.215] 11 25 ms 34 ms 30 ms bx4-seattle_xe7-0-0_0.net.bell.ca [64.230.186.46] 12 29 ms 39 ms 28 ms six.as13335.com [206.81.81.10] 13 81 ms 86 ms 77 ms 198.41.184.235 Trace complete. Neighbors network Tracing route to bitcoinwisdom.com [198.41.184.235] over a maximum of 30 hops: 1 11 ms 4 ms 3 ms 192.168.0.1 2 * * * Request timed out. 3 21 ms 15 ms 14 ms rd3st-tge0-9-5-0-1.vc.shawcable.net [64.59.147.125] 4 26 ms 29 ms 21 ms rc2wh-tge0-5-0-10.vc.shawcable.net [66.163.65.134] 5 26 ms 42 ms 22 ms rc2wh-tge0-14-0-17.vc.shawcable.net [66.163.77.186] 6 18 ms 23 ms 32 ms rc5wt-tge0-2-0-12.wa.shawcable.net [66.163.68.25] 7 36 ms 18 ms 30 ms six.as13335.com [206.81.81.10] 8 19 ms 17 ms 17 ms 198.41.184.235 Trace complete. Thank you. Some more info is needed. https://bitcoinwisdom.com/cdn-cgi/traceand curl --verbose https://bitcoinwisdom.com/ --output /dev/null --silent
|
|
|
This is exactly what I'm getting also. Not sure if it's useful, but here is a dump of the SSL cert being sent out. Could you provide the traceroute result?
|
|
|
First of all - great work on the site!
But... I'm also getting the same SSL error as the others. It's been going on three days or so.
Could it be that my ISP is caching the certificate? I'm with Telus. For the others experiencing the same issue - what ISP are you with?
Thanks
Your site is still not working, Please fix it ASAP ,Thank you.
According to traffic monitor, it shows most of people could visit the site without problem. and I've tested 8 different location servers and all of google first page ssl checker. all of them shows the site returns correct ssl certificate. so it must be some personal cache such as browser cache, route cache or ISP cache. You could try incognito mode or different browser to check the site works or not.
|
|
|
Hello,
Having plans to add Huobi ltc charts as soon as trading ltc starts there?
Yes.
|
|
|
Hoping add BTC38 on your charts, thanks.
I'm sorry I cannot find the https entry.
|
|
|
We could not find any other way except here to contact you,. Our client - Bitcoin stock exchange wants you to add it to your service review. How can this be done and what rules do you have?
Yes, The most important is Good reputation, High Volume, Friendly API. and the exchange must have run for at least serveral weeks to months. Thanks for reply, ok, they already have all these things. What actionplan should they have next to be added? PM me the site, API and bitcointalk announcement page or primary talking thread.
|
|
|
A Million thanks for providing the UTC time option!!!
You're welcome.
|
|
|
Hi guys, would you consider adding Mastercoin data to your site? There is a datafeed from masterxchange.com available : https://masterxchange.com/api/Have been using Bitcoinwisdom for the MA indicator, would love to be able to use for Mastercoin Thanks yeah, he really does have the best charts, kudos on that *edit Here's what I get after clearing Cookies & browsing data... I mean ping or dig the domain. such as ping bitcoinwisdom.com PING bitcoinwisdom.com (198.41.184.235) 56(84) bytes of data. or dig bitcoinwisdom.com bitcoinwisdom.com. 106 IN A 198.41.191.234 bitcoinwisdom.com. 106 IN A 198.41.184.235 I guess it is caused by DNS caching.
|
|
|
Same for me.. I'm on chrome.. the charts are not loading but others are still there =/
What's the IP of BitcoinWisdom you resolved? It's 198.41.184.235 and 198.41.191.234 here.
|
|
|
VoS haven't historical trades API.
|
|
|
hmm certificate revocation on chrome, and cant figure out how to fix
I'm sorry, I tested the site and works well for a while, then switch the whole site to https. I should wait for more time before switching. It is caused by CloudFlare's node is cached and return old certificate. It should be fix when the node refreshed, it will not take long time. Still not working in chrome, but I got it to work in ie by going into internet options, and disabling certificate auth. That's weird. The server should be work now. I've tested with 4 different location servers and several online ssl checker, all of them work.
|
|
|
hmm certificate revocation on chrome, and cant figure out how to fix
I'm sorry, I tested the site and works well for a while, then switch the whole site to https. I should wait for more time before switching. It is caused by CloudFlare's node is cached and return old certificate. It should be fix when the node refreshed, it will not take long time.
|
|
|
can you return https support? https://bitcoinwisdom.com/ won't open (but even some days/week ago it worked fine) my chrome-extension (btc-e terminator) uses https bitcoinwisdom for integration it with btc-e terminal... and there is no way to inject http content into https document-frame(( link to ext with pretty ((past-)screenshot: fhlkghhkmntnx!! The whole site is now moved to https. the issue should be fixed.
|
|
|
Hey, btcwisdom... quick question.
Any chance you could implement two small buttons, "+" and "-" to zoom in exactly 1 step, and zoom out 1 step, respectively? Or maybe just map the same function to the + and - keyboard keys, without visible buttons?
The reason: on most of my devices (phone, Macbook) I use a trackpad, and when zooming in and out it can be really tricky to get the zoom level you want like that... I spend usually a minute or so until I get the right level.
It's not such a huge deal.. if it's too much effort to get it to work, forget it. Just would make usability a tiny bit better, in my opinion.
EDIT: I should maybe add: I'm sure I'm not the only one with a trackpad only device (smart phone or small notebook), so I suspect others might have a similar experience.
The feature is requsted by another member too. I've considered the way to implement for a while, but still have not decided yet.
|
|
|
How are we supposed to place bids when most of the depth is missing like this? Can u fix it please?
The orderbook is extended, but the precision is decreased.
|
|
|
|