Open vik-y opened 1 week ago
The same thing happens to me, I get an error when connecting to the bashhub API.
Hi, thanks for reporting. There's an outage due to an upgrade with MongoDB's driver. Will investigate more later this week to see if there's a reasonable fix and report back.
I faced the same issue and feel a bit duped now—I can't remember the command I executed earlier! 🤣
Same here.
The SSL certificate for bashhub.com appears to be expired, which will cause secure HTTPS connections to fail. Below are the details of the certificate:
Until the certificate is renewed, the script will give this error. It happened a year or two ago too.
I think there certificate expired recently. Earlier it was returning 410, which it returns now also if you override the cert expiry error.
❯ curl -kv https://bashhub.com/xyz
* Host bashhub.com:443 was resolved.
* IPv6: (none)
* IPv4: 52.4.104.79
* Trying 52.4.104.79:443...
* Connected to bashhub.com (52.4.104.79) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / [blank] / UNDEF
* ALPN: server accepted http/1.1
* Server certificate:
* subject: CN=bashhub.com
* start date: Oct 27 00:00:00 2023 GMT
* expire date: Nov 26 23:59:59 2024 GMT
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* using HTTP/1.x
> GET /xyz HTTP/1.1
> Host: bashhub.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 410 Gone
< Server: nginx
< Date: Thu, 28 Nov 2024 12:05:26 GMT
< Content-Length: 0
< Connection: keep-alive
< Report-To: {"group":"heroku-nel","max_age":3600,"endpoints":[{"url":"https://nel.heroku.com/reports?ts=1732795526&sid=af571f24-03ee-46d1-9f90-ab9030c2c74c&s=rK6GG6Sl9lQd8cRDxiBZnFa%2FWHhkJY8ngAeAlQ5O6Cg%3D"}]}
< Reporting-Endpoints: heroku-nel=https://nel.heroku.com/reports?ts=1732795526&sid=af571f24-03ee-46d1-9f90-ab9030c2c74c&s=rK6GG6Sl9lQd8cRDxiBZnFa%2FWHhkJY8ngAeAlQ5O6Cg%3D
< Nel: {"report_to":"heroku-nel","max_age":3600,"success_fraction":0.005,"failure_fraction":0.05,"response_headers":["Via"]}
< Via: 1.1 vegur
<
* Connection #0 to host bashhub.com left intact
Need to find alternatives to this tool. It's abandoned.
Looks like the ssl certificate was renewed
Not sure if it's a "me" issue, but I seem to still be experiencing issues despite the cert being renewed.. Not sure if I'm dealing with a networking issue of my own or what not. Maybe not, since I seem to not be able to "reset password" via https://bashhub.com/ ?
The issue is still not resolved.
Have you stopped maintaining this? @rcaloras
Hey all, thanks for continuing to support and use Bashhub. As mentioned, there's an outage due a deprecated driver for MongoDB on Bashhub's server. More specifically, MongoDB recently had an EOL for v5.0 which is causing the need to upgrade the driver.
I spent some time this weekend trying to upgrade the backend, but haven't been able to complete yet as it's required upgrading a number of dependencies (not just the Mongo Driver). No immediate ETA, but anticipate investing time the next couple weeks.
If anyone is interested to help with the upgrade and looking to contribute, I can give access to Bashhub's server repo which is a Scala/Play app. As a long time freely maintained project, contributors/maintainers are certainly appreciated. Let me know here or via message ryan@bashhub.com cc @kootenpv as long time follower invested in the project.
@rcaloras
I just sent you a message.
❯❯❯ bashhub status Sorry, an error occurred communicating with Bashhub. Response Code: 410
Also, bashhub.com/username -> shows 410
Anyone else facing this problem?
Looks like the issue has been there since 16th of November.