Windows' CURL not uploading Deepstack's alerts

_Peek

Young grasshopper
Joined
Jun 1, 2020
Messages
38
Reaction score
11
Location
South
I have BlueIris and Deepstack running on Windows 10 with no other software of interest.

I also ran Chris Titus's "cleanup" PowerShell script iwr -useb [URL unfurl="true"]https://christitus.com/win[/URL] |iex as to get the best possible performance out of the machine.

However, I'm dumbfounded with CURL intermittently failing to upload alert images. A restart of the machine resolves the issue, but one never knows until it's too late.

Running CURL from the command line after a restart, which successfully uploads the alert image:

Code:
C:\>curl -vv https://api.telegram.org/bot_4/sendPhoto -F chat_id=-3 -F caption="[*&CAM*](&LAN/alerts/&ALERT_DB?fulljpeg) [UI3](&LAN/ui3.htm?rec=&ALERT_DB&maximize=1) \- &MEMO" -F parse_mode=MarkdownV2 -F photo=@"C:\BlueIris\28229.jpg"
*   Trying 2001:67c:4e8:f004::9:443...
*   Trying 149.154.167.220:443...
* Connected to api.telegram.org (2001:67c:4e8:f004::9) port 443 (#0)
* schannel: disabled automatic use of client certificate
* ALPN: offers http/1.1
* ALPN: server accepted http/1.1
> POST /bot_4/sendPhoto HTTP/1.1
> Host: api.telegram.org
> User-Agent: curl/7.83.1
> Accept: */*
> Content-Length: 660110
> Content-Type: multipart/form-data; boundary=------------------------1bd7708ed6e4d65d
>
* We are completely uploaded and fine
* schannel: failed to decrypt data, need more data
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Wed, 10 Aug 2022 23:25:32 GMT
< Content-Type: application/json
< Content-Length: 1220
< Connection: keep-alive
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET, POST, OPTIONS
< Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection
<
{"ok":true,"result":{"message_id":8,"sender_chat":{"id":-3,"title":"InstaInfo","type":"channel"},"chat":{"id":-3,"title":"Info","type":"channel"},"date":1660173932,"photo":[{"file_id":"868p-BA","file_unique_id":"Vd4","file_size":1423,"width":90,"height":67},{"file_id":"868p-BA","file_unique_id":"Vdy","file_size":26542,"width":320,"height":240},{"file_id":"868p-BA","file_unique_id":"Vd9","file_size":133209,"width":800,"height":600},{"file_id":"868p-c24BAAMCAAN5AAMpBA","file_unique_id":"Vd-","file_size":293948,"width":1280,"height":960},{"file_id":"868p-BA","file_unique_id":"Vd8","file_size":659347,"width":2560,"height":1920}],"caption":"&CAM UI3 - &MEMO","caption_entities":[{"offset":0,"length":4,"type":"bold"}]}}* Connection #0 to host api.telegram.org left intact
Running CURL from the command line once noticed that images isn't being uploaded anymore:

Code:
C:\>curl -vv https://api.telegram.org/bot_4/sendPhoto -F chat_id=-3 -F caption="[*&CAM*](&LAN/alerts/&ALERT_DB?fulljpeg) [UI3](&LAN/ui3.htm?rec=&ALERT_DB&maximize=1) \- &MEMO" -F parse_mode=MarkdownV2 -F photo=@"C:\BlueIris\28229.jpg"
*   Trying 2001:67c:4e8:f004::9:443...
*   Trying 149.154.167.220:443...
* Connected to api.telegram.org (2001:67c:4e8:f004::9) port 443 (#0)
* schannel: disabled automatic use of client certificate
* ALPN: offers http/1.1
To date I've tried uninstalling & reinstalling OpenSSH Client under Settings > Apps > Optional Features, yet still being surprised every second week or so with CURL not working again ...
 

_Peek

Young grasshopper
Joined
Jun 1, 2020
Messages
38
Reaction score
11
Location
South
Corrupt cert?
Why would it work fine after a restart for a number of days ? ...

Regardless, that why I've tried by uninstalling and reinstalling OpenSSH client.

Or is there a better way to address cert validation / renewal etc ?
 
Top