Instagram crashed, stop your bots

IGJavier

Regular Member
Joined
Jan 31, 2018
Messages
285
Reaction score
119
IG is not working, it's necessary to stop the bots? Or I just panicked too much?
 
5xx Server Error
Code:
* STATE: INIT => CONNECT handle 0xeff160; line 1404 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* STATE: CONNECT => WAITRESOLVE handle 0xeff160; line 1440 (connection #0)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 31.13.81.32...
* TCP_NODELAY set
* STATE: WAITRESOLVE => WAITCONNECT handle 0xeff160; line 1521 (connection #0)
* Connected to www.instagram.com (31.13.81.32) port 443 (#0)
* STATE: WAITCONNECT => SENDPROTOCONNECT handle 0xeff160; line 1573 (connection #0)
* Marked for [keep alive]: HTTP default
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
  CAfile: C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
  CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* STATE: SENDPROTOCONNECT => PROTOCONNECT handle 0xeff160; line 1587 (connection #0)
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [102 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3115 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Menlo Park; O=Facebook, Inc.; CN=*.www.instagram.com
*  start date: Oct 30 00:00:00 2017 GMT
*  expire date: Nov  7 12:00:00 2018 GMT
*  subjectAltName: host "www.instagram.com" matched cert's "www.instagram.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
* STATE: PROTOCONNECT => DO handle 0xeff160; line 1608 (connection #0)
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0xeff160)
} [5 bytes data]
> GET / HTTP/2
> Host: www.instagram.com
> User-Agent: curl/7.59.0
> Accept: */*
>
* STATE: DO => DO_DONE handle 0xeff160; line 1670 (connection #0)
* multi changed, check CONNECT_PEND queue!
* STATE: DO_DONE => WAITPERFORM handle 0xeff160; line 1795 (connection #0)
* STATE: WAITPERFORM => PERFORM handle 0xeff160; line 1811 (connection #0)
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
} [5 bytes data]
* multi changed, check CONNECT_PEND queue!
{ [5 bytes data]
* HTTP/2 found, allow multiplexing
< HTTP/2 503
< content-length: 105
< content-type: text/html; charset=utf-8
< access-control-allow-origin: *
< date: Fri, 13 Jul 2018 19:02:16 GMT
<
{ [105 bytes data]
* nread <= 0, server closed connection, bailing
* STATE: PERFORM => DONE handle 0xeff160; line 1980 (connection #0)
* multi_done
 
Can connect now, and than may I know can I sign up, sign in two account for one ip?
 
I guess it's just the website version not working. My app is running fine without any issues.
 
Back
Top