We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I ran the following command
netaccess -u my_username -p my_passwd -d 2
and got following error,
thread 'main' panicked at 'Failed to send login request: Error { kind: Io(Error { repr: Custom(Custom { kind: Other, error: Ssl(ErrorStack([Error { code: 336134278, library: "SSL routines", function: "ssl3_get_server_certificate", reason: "certificate verify failed", file: "s3_clnt.c", line: 1264 }])) }) }), url: Some("https://netaccess.iitm.ac.in/account/login/") }', /checkout/src/libcore/result.rs:906:4 note: Run with RUST_BACKTRACE=1 for a backtrace.
RUST_BACKTRACE=1
The text was updated successfully, but these errors were encountered:
Same issue with me.
Sorry, something went wrong.
This is caused due to old OpenSSL version on the CC Network server.
So sir what is the solution? Any change should we make?
Guys, I'm not in IITM anymore and I can't check why it's not working. I have a Python script (https://j-jith.github.io/blog/python-script-for-logging-in-to-iit-madras-netaccess/) which does the same thing. Please see if this is working.
No branches or pull requests
I ran the following command
and got following error,
thread 'main' panicked at 'Failed to send login request: Error { kind: Io(Error { repr: Custom(Custom { kind: Other, error: Ssl(ErrorStack([Error { code: 336134278, library: "SSL routines", function: "ssl3_get_server_certificate", reason: "certificate verify failed", file: "s3_clnt.c", line: 1264 }])) }) }), url: Some("https://netaccess.iitm.ac.in/account/login/") }', /checkout/src/libcore/result.rs:906:4
note: Run with
RUST_BACKTRACE=1
for a backtrace.The text was updated successfully, but these errors were encountered: