Verify failed please reload and try again бинанс

Binance SSL: CERTIFICATE_VERIFY_FAILED #882

Comments

scoshil commented Dec 18, 2017

I’m trying to connect to binance, and just testing the load_markets function, but I’m getting an SSL error.

Not having issues with other exchanges, and this key/secret pair works without ccxt

The text was updated successfully, but these errors were encountered:

kroitor commented Dec 18, 2017

Are you located in China?

scoshil commented Dec 18, 2017

I am located in Australia

kroitor commented Dec 18, 2017

@scoshil can you access it via a public CORS-proxy?

kroitor commented Dec 18, 2017

Looks like an issue with Anaconda Python certificates or root CA settings. Did you see any options regarding SSL certificates upon installing it? Can you verify that it has access to your system / OpenSSL certificates?

kroitor commented Dec 18, 2017 •

and this key/secret pair works without ccxt

Did you test that keypair with any other software? Can you clarify how exactly it «works» ?

scoshil commented Dec 18, 2017

I tested that pair with the lib at https://github.com/sammchardy/python-binance and it worked smoothly. haven’t looked to see if that lib does anything special with proxies yet, but I didn’t configure it any differently to normal.

I will look into those links and see if I can fix it this way.

kroitor commented Dec 18, 2017

@scoshil ok, I will check their sources on this issue, to see if there’s a workaround for this. Thx! Will get back to you with a followup.

kroitor commented Dec 18, 2017 •

@scoshil can you paste here your code snippet that you used with https://github.com/sammchardy/python-binance for testing, please?

scoshil commented Dec 18, 2017

do you mean from python-binance?

kroitor commented Dec 18, 2017

Does this help with ccxt?

scoshil commented Dec 18, 2017

@kroitor I tried that and it still gives me the same error unfortunately

kroitor commented Dec 18, 2017 •

@scoshil python-binance works because it uses the requests python package, and that in turn also links against non-default SSL certificates from certifi package. ccxt uses pure built-in HTTP and for some reason a particular installation of conda won’t find its default SSL/CA certificates. If none of the above links and suggestions help, we may switch to requests as well. Can you find out where it stores certificates on your system?

kroitor commented Dec 18, 2017

If nothing helps, I will do a clean install of Anaconda Python on a virtual Windows PC and will test/fix it then.

kroitor commented Dec 19, 2017 •

@scoshil can you, please, try reinstalling the anaconda python? (a fresh distrib from their site, if that’s ok for you). you would help us rule out one possible cause of it.

scoshil commented Dec 19, 2017

Thanks I’ll try the things you mentioned and report back. may take me a little while to do a clean anaconda install though

scoshil commented Dec 19, 2017

Ok so I tried the following:

• Clean install of Anaconda on my existing PC — same error message
• All the solutions mentioned in https://stackoverflow.com/questions/33699577/conda-update-failed-ssl-error-ssl-certificate-verify-failed-certificate-ver — same error message
• Running from a VM located in North America — same error message

Really out of ideas at this point.

kroitor commented Dec 19, 2017

@scoshil ok, thanks so much for your effort and for reporting back! We will have to migrate to requests+certifi for their SSL certificates, I’ll let you know on the progress, hopefully very soon.

scoshil commented Dec 19, 2017

kroitor commented Dec 19, 2017 •

@scoshil I can’t reproduce the problem from my Windows 10 machine from Russia, I can access Binance normally.

As you see, a fresh install of Anaconda3 works on my side. So, maybe you have some certificates that are outdated or something. However, I don’t know if it makes sense, because you did a clean reinstall.

After installing anaconda I found these two certificates on my setup C:\Users\myusername\AppData\local\Continuum\anaconda3\ssl :

You can try copying them into your ssl folder to see if they make any difference (save a backup copy of existing certificates beforehand). The fix is on the way.

kroitor commented Dec 19, 2017 •

Also, if you can, please run the following to see if the issue is indeed related to default SSL certificates:

Does the above snippet work?

hexdump2002 commented Dec 19, 2017 •

I have executed what you suggested and this is the output:

It seems to work correctly. I’m the one that reported #904

kroitor commented Dec 19, 2017

@hexdump2002 thanks! That confirms my initial thought. Ok, the fix for this is coming very soon.

hexdump2002 commented Dec 19, 2017

Thanks a lot. We really need it because the library crashes in such basic thing. By he way, your work with the lib is awesome. Thanks for sharing it!

kroitor commented Dec 19, 2017 •

@hexdump2002 thank you! Btw, just for completeness, if it’s not a secret, what is your country/region/continent?

hexdump2002 commented Dec 19, 2017

Europe/Spain , I will provide anything you need 🙂

hexdump2002 commented Dec 19, 2017

@kroitor : With no intention of rushing you or anything, do you have any ETA for this bug to be fixed? We are at this stucked now :).

kroitor commented Dec 19, 2017

scoshil commented Dec 20, 2017

@kroitor I can confirm I have the same output as @hexdump2002 for the requests code you provided

I also tried replacing my ssl certificates and it didn’t change anything

scoshil commented Dec 20, 2017

@kroitor also just wanted to echo the thanks for sharing the lib! The work that’s been done so far has been great!

hexdump2002 commented Dec 20, 2017

Following up the «switching to requests library» suggestions you commented yesterday. Will this affect the cctx.async part of the library? I mean, requests is not compatible with async, so we will have sync calls whenever we use async or not. Could you give a bit of information about this?

kroitor commented Dec 20, 2017 •

Will this affect the cctx.async part of the library?

No, if you mean breaking the async version, it will not affect the ccxt.async. But yes, if you mean switching the async to an async-compatible implementation of requests — it will affect the implementation only. The interface remains the same.

I mean, requests is not compatible with async

Yes, but we are not going to use the synchronous version of requests in our async subpackage, of course. We are going to integrate an async-aware implementation of requests, like requests-futures , or some other implementation that fits best for this job.

so we will have sync calls whenever we use async or not.

Nope, you will still have both sync and true-async modes available.

Hope it answers your question, let me know if you have more )

Источник

Binance registration problem. 2FA not working

It’s already the second day of failure at Binance. One of the best stock exchanges has been paralyzed, as a result of many transactions and many new registrations.
>A news appeared on Binance, from which we learn that new registrations are pending until further notice.

“Due to the overwhelming surge in popularity, Binance will have to temporarily disable new user registrations to allow for an infrastructure upgrade. We apologize for any inconvenience caused. Thank you for your support!”

Registrations and 2FA not working

New registrations are not the only problem. The Binance Exchane also has a problem with 2fa (two factor authorization) and password recovery. Binance already knew this problem and published advice:
After opening a ticket, please attach the following to it:

1) The front your ID card or passport, with the personal information clearly visible.
2) A picture of the back of your ID card. If using a passport, include a picture of the cover.
3) A picture of yourself with the current date/time on a handwritten note, including your request (“Reset 2FA”), with the front side of your ID card clearly visible.
After you have completed this, we will reset your 2FA as soon as we are able. Once reset, you will be unable to withdraw for 48 hours. This is for the security of your account.

Before the failure, Binance was updating the application.

When will they fix it all?

Binance usually reacts quickly to similar problems. So far, the exchange has had small breakdowns and immediately reported it on Twitter. At the time of writing this news, we have no problems with the Exchange, so maybe it’s the end of problems.

What people say?

“i wish they were more clear, is this what the message: “Verify failed, please reload and try again” means? because I’ve been freaking out like someone stole my login ... But it’s odd i can still get on the desktop site and view the markets, i just cant login.” (Reddit, ga1actic_muffin)

“I had this problem earlier last night before the majority of the States woke up. The outbound transfer of ETH from my coinbase wallet was pending for around 2 hours. It is not Binance, Coinbase had huge network congestion. You might be able to see the amount of confirmations where it would say pending on your btc/eth wallet through the mobile application. It didn’t show it to me on pc” (Reddit, The_Crowned_King).

Источник

Oops! Something went wrong on the server. Please reload the page and try again. #607

Comments

ghost commented Oct 27, 2015

Hey All,
I have followed the guide over here about troubleshooting Flarum > http://flarum.org/docs/troubleshooting/

Unfortunately, I still do not understand what these errors mean.
I click Network > then console and see
Failed to load resource: the server responded with a status of 501 (Not Implemented)

Trying everything I receive this error. Whether it be changed a person’s group, making a new group, creating tags, it all. I receive the same error.

I know there is a definite way around this but I just am too silly to see it. Any ideas?
http://prntscr.com/8vtymr
Thanks,
Mas

The text was updated successfully, but these errors were encountered:

franzliedke commented Oct 27, 2015

I’m pretty sure this is a problem with your web server not supporting PATCH requests. Which server software are you using?

This was fixed in #502, which will be in the next beta version (due to be released this week, probably).

franzliedke commented Oct 27, 2015

Yep, pretty sure this is it. Closing this.

In the meantime, you will have to either change hosting, or wait for the next release. 🙂

ghost commented Mar 24, 2017

Hey,
I am having this error.
But i can log in on flarum forum, but not on my own forum.
But i can on my phone and tablet. And someone else also can.
(So i can not log in or sign up on my forum without the error.)
I am using Google Chrome browser.

luceos commented Mar 27, 2017

@dangerORclose please open a support question on the official forums, most likely something is wrong with your set up; this ticket is not about specific per-user problems.

Источник

Failed to verify code signature? #94

Comments

hbbxmjbb commented Jan 30, 2020

Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.XhVlHm/extracted/AltStore.app : 0xe8008001 (An unknown error has occurred.)

The text was updated successfully, but these errors were encountered:

Sirtz commented Feb 11, 2020 •

Same problem here, is there a workaround?

crest1993 commented Mar 30, 2020

almost the same when installing altstore windows
but instead 0xe8008018 (The identity used to sign the executable is no longer valid)

MinecraftPublisher commented Apr 29, 2020

Not Working For Me Too.
I Reinstalled AltStore And This Happened.

noah978 commented May 22, 2020

This issue should be fixed on the latest versions of AltStore/AltServer. Closing this issue.

vamgan commented May 23, 2020

Still not fixed on the latest version

noah978 commented May 23, 2020 •

@vamgan Please provide the following information if you can:

Are you having the exact same issue as @hbbxmjbb? Lastly, can you try uninstalling AltServer and using the latest beta AltServer.

vamgan commented May 23, 2020 •

Exact same issue

Installed and reinstalled many times the latest version: 1.3.2 beta 3

noolaan commented May 24, 2020 •

Also having this issue on latest version 1.3.2, iPhone 7 13.5 on Windows 10

noah978 commented May 24, 2020

Please try deleting the “adi” folder in iTunes’ file directory, then restart your computer and try again.

noolaan commented May 24, 2020 •

The first time I attempted it, AltServer exited while «installing» without any error prompt. I tried it a second time (after deleting the file again and restarting) and it continues to give me the same error. The file reappears after each reboot. I’ve already restored my phone, tried a new Apple ID, reinstalled ITunes/ICloud a few times, disabled my firewall, and a few other things.

noah978 commented May 24, 2020

Please make sure that your iOS Time + Date and Windows Time + Date are correct and in sync. This should fix your issue.

noolaan commented May 24, 2020

Solved! I guess my BIOS never had its system time set correctly and this managed to solve it after enabling automatic time setting, automatic timezones, and syncing with windows again. Thank you for the help, this was extremely frustrating.

dlcode14 commented May 24, 2020

If you have Reprovision installed try downgrading it to previous version or uninstall it..downgrading worked for me. )

Источник