[2025-09-13 20:25:15] [INFO] 

Webhook processing started
[2025-09-13 20:25:15] [INFO] Group message from ZarAli in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי
[2025-09-13 20:25:16] [DEBUG] Raw AI classification response: '{
    "intent": "Other"
}'
[2025-09-13 20:25:16] [DEBUG] Handling Other message - Other
[2025-09-13 20:25:16] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 20:25:16] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f580070d2d0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 20:25:16 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 20:25:16] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 20:25:16] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f580070d2d0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 20:25:16 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 20:25:32] [INFO] 

Webhook processing started
[2025-09-13 20:25:32] [INFO] Group message from ZarAli in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): /
[2025-09-13 20:25:33] [DEBUG] Raw AI classification response: '{
    "intent": "Other"
}'
[2025-09-13 20:25:33] [DEBUG] Handling Other message - Other
[2025-09-13 20:25:33] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 20:25:33] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800cda120)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 20:25:33 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 20:25:33] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 20:25:33] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800cda120)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 20:25:33 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:54] [INFO] 

Webhook processing started
[2025-09-13 22:19:54] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי ברברה
[2025-09-13 22:19:56] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "ברברה",
    "category": "",
    "brand": "ברברה",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:19:56] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:19:56] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:19:56] [INFO] Loading WordPress
[2025-09-13 22:19:56] [INFO] Loaded wp-load.php
[2025-09-13 22:19:56] [INFO] WordPress loaded
[2025-09-13 22:19:56] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:19:56] [INFO] Normalizing products.
[2025-09-13 22:19:56] [DEBUG] Classification Product: ברברה
[2025-09-13 22:19:56] [DEBUG] Classification Category: 
[2025-09-13 22:19:56] [DEBUG] Classification Brand: ברברה
[2025-09-13 22:19:56] [DEBUG] Classification Features: 
[2025-09-13 22:19:56] [DEBUG] Classification Gender: 
[2025-09-13 22:19:56] [DEBUG] Classification Filters: 
[2025-09-13 22:19:56] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:19:56] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11936 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:56 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:56] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:19:56] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11936 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:56 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:56] [DEBUG] Searching for: 'ברברה'
[2025-09-13 22:19:56] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:19:56] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:19:56] [INFO] Normalizing products.
[2025-09-13 22:19:56] [DEBUG] No results found using strategy: Original Product Search
[2025-09-13 22:19:56] [DEBUG] Searching by category: '' brand: 'ברברה' and gender ''
[2025-09-13 22:19:56] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:19:56] [INFO] WordPress wc_get_products found 0 products for: ' ברברה'
[2025-09-13 22:19:56] [INFO] Normalizing products.
[2025-09-13 22:19:56] [DEBUG] No results found using strategy: Category + Brand Search
[2025-09-13 22:19:56] [DEBUG] Searching by brand: 'ברברה' and gender ''
[2025-09-13 22:19:56] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:19:56] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:19:56] [INFO] Normalizing products.
[2025-09-13 22:19:56] [DEBUG] No results found using strategy: Brand Search
[2025-09-13 22:19:56] [DEBUG] Searching by category: '' and gender ''
[2025-09-13 22:19:56] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:19:56] [INFO] WordPress wc_get_products found 10 products for: ''
[2025-09-13 22:19:56] [INFO] Normalizing products.
[2025-09-13 22:19:56] [INFO] Found 10 products using strategy: Category Search
[2025-09-13 22:19:56] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a7%d7%a4%d7%95%d7%a6%d7%95%d7%9f/">מעיל קפוצון</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

2. <a href="https://dealimzoharim.com/product/%d7%98%d7%a8%d7%a0%d7%a5-%d7%96%d7%90%d7%a8%d7%94/">טרנץ זארה</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

3. <a href="https://dealimzoharim.com/product/%d7%92%d7%a7%d7%98%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94/">ג'קט ספורטיבי אלו יוגה</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

4. <a href="https://dealimzoharim.com/product/%d7%91%d7%99%d7%a8%d7%a7%d7%a0%d7%a9%d7%98%d7%95%d7%a7-%d7%9e%d7%95%d7%92%d7%91%d7%94%d7%95%d7%aa/">בירקנשטוק מוגבהות</a>
<b>בירקנשטוק מוגבהות</b>
מידות 35-44


[2025-09-13 22:19:56] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:19:56] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/4e4c683a-ca0c-4ad2-b1e5-8b436ec7979f.jpeg
[2025-09-13 22:19:56] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/9b7e89d5-96b5-40b7-ba09-6b2967c33fb1.jpeg
[2025-09-13 22:19:56] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg
[2025-09-13 22:19:56] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/07/02aa3d3d-e1720188597988.jpeg
[2025-09-13 22:19:56] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:19:56] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/4e4c683a-ca0c-4ad2-b1e5-8b436ec7979f.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/4e4c683a-ca0c-4ad2-b1e5-8b436ec7979f.jpeg
[2025-09-13 22:19:56] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:19:56] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/9b7e89d5-96b5-40b7-ba09-6b2967c33fb1.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/9b7e89d5-96b5-40b7-ba09-6b2967c33fb1.jpeg
[2025-09-13 22:19:56] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:19:56] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg
[2025-09-13 22:19:56] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:19:56] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2024/07/02aa3d3d-e1720188597988.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2024/07/02aa3d3d-e1720188597988.jpeg
[2025-09-13 22:19:57] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:19:57] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:19:57] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:19:57] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:19:57] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:19:57] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:19:57] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1811083
content-type: multipart/form-data; boundary=------------------------f379c64109b3805c

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:57 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:57] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:19:57] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1811083
content-type: multipart/form-data; boundary=------------------------f379c64109b3805c

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:57 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:57] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:19:57] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2424
content-type: application/json; boundary=------------------------5bc4cdfe58ad6c36

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:57 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:19:57] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:19:57] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2424
content-type: application/json; boundary=------------------------5bc4cdfe58ad6c36

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:19:57 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:13] [INFO] 

Webhook processing started
[2025-09-13 22:20:13] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי ברברי
[2025-09-13 22:20:15] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "ברברי",
    "category": "",
    "brand": "ברברי",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:20:15] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:20:15] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:20:15] [INFO] Loading WordPress
[2025-09-13 22:20:15] [INFO] Loaded wp-load.php
[2025-09-13 22:20:15] [INFO] WordPress loaded
[2025-09-13 22:20:15] [INFO] WordPress wc_get_products found 10 products for: 'ברברי'
[2025-09-13 22:20:15] [INFO] Normalizing products.
[2025-09-13 22:20:15] [DEBUG] Classification Product: ברברי
[2025-09-13 22:20:15] [DEBUG] Classification Category: 
[2025-09-13 22:20:15] [DEBUG] Classification Brand: ברברי
[2025-09-13 22:20:15] [DEBUG] Classification Features: 
[2025-09-13 22:20:15] [DEBUG] Classification Gender: 
[2025-09-13 22:20:15] [DEBUG] Classification Filters: 
[2025-09-13 22:20:15] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11937 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:15] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11937 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:15] [DEBUG] Searching for: 'ברברי'
[2025-09-13 22:20:15] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:20:15] [INFO] WordPress wc_get_products found 10 products for: 'ברברי'
[2025-09-13 22:20:15] [INFO] Normalizing products.
[2025-09-13 22:20:15] [INFO] Found 10 products using strategy: Original Product Search
[2025-09-13 22:20:15] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%98%d7%a8%d7%a0%d7%a5-%d7%91%d7%a8%d7%91%d7%a8%d7%99/">מעיל טרנץ ברברי</a>
<b>מעיל טרנץ ברברי</b>
<b>עד הברך</b>
מידות S-4XL

2. <a href="https://dealimzoharim.com/product/%d7%a7%d7%a8%d7%93%d7%99%d7%92%d7%9f-%d7%91%d7%a8%d7%91%d7%a8%d7%99-3/">קרדיגן ברברי</a>

3. <a href="https://dealimzoharim.com/product/%d7%92%d7%a7%d7%98-%d7%91%d7%a8%d7%91%d7%a8%d7%99-3/">ג'קט ברברי</a>

4. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a7%d7%9c-%d7%91%d7%a8%d7%91%d7%a8%d7%99/">מעיל קל ברברי</a>


[2025-09-13 22:20:15] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:20:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/09/bb65ec9c.jpeg
[2025-09-13 22:20:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/e8345758.jpg
[2025-09-13 22:20:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/12/ab3b64a6.jpg
[2025-09-13 22:20:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/08/9031c27a-scaled.jpg
[2025-09-13 22:20:15] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_a26be7a2b8f910b1af5471c37d31348e.jpg
[2025-09-13 22:20:15] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_a26be7a2b8f910b1af5471c37d31348e.jpg
[2025-09-13 22:20:15] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_a26be7a2b8f910b1af5471c37d31348e.jpg
[2025-09-13 22:20:15] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:20:15] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fb4110)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 4224444
content-type: multipart/form-data; boundary=------------------------518fb13a34ae0fce

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:15] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fb4110)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 4224444
content-type: multipart/form-data; boundary=------------------------518fb13a34ae0fce

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:15] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1352
content-type: application/json; boundary=------------------------d82678988819905a

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:20:15] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:20:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c52520)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1352
content-type: application/json; boundary=------------------------d82678988819905a

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:20:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:14] [INFO] 

Webhook processing started
[2025-09-13 22:25:14] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי אלו
[2025-09-13 22:25:15] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "אלו",
    "category": "",
    "brand": "אלו",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:25:15] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:25:15] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:25:15] [INFO] Loading WordPress
[2025-09-13 22:25:15] [INFO] Loaded wp-load.php
[2025-09-13 22:25:15] [INFO] WordPress loaded
[2025-09-13 22:25:15] [INFO] WordPress wc_get_products found 10 products for: 'אלו'
[2025-09-13 22:25:15] [INFO] Normalizing products.
[2025-09-13 22:25:15] [DEBUG] Classification Product: אלו
[2025-09-13 22:25:15] [DEBUG] Classification Category: 
[2025-09-13 22:25:15] [DEBUG] Classification Brand: אלו
[2025-09-13 22:25:15] [DEBUG] Classification Features: 
[2025-09-13 22:25:15] [DEBUG] Classification Gender: 
[2025-09-13 22:25:15] [DEBUG] Classification Filters: 
[2025-09-13 22:25:15] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:25:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11938 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:15] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:25:15] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11938 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:15 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:15] [DEBUG] Searching for: 'אלו'
[2025-09-13 22:25:15] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:25:15] [INFO] WordPress wc_get_products found 10 products for: 'אלו'
[2025-09-13 22:25:15] [INFO] Normalizing products.
[2025-09-13 22:25:15] [INFO] Found 10 products using strategy: Original Product Search
[2025-09-13 22:25:15] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%92%d7%a7%d7%98%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94/">ג'קט ספורטיבי אלו יוגה</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

2. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94-4/">מעיל אלו יוגה</a>

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94/">מעיל אלו יוגה</a>
✨ איכות ללא פשרות
✨ טקיטים מקוריים
✨ אתר מאובטח לקנייה
✨ מחירים מיוחדים בשבילנו
✨ הקולקציות הכי חדשות

4. <a href="https://dealimzoharim.com/product/%d7%aa%d7%99%d7%a7-%d7%a1%d7%a4%d7%95%d7%a8%d7%98-%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94-2/">תיק ספורט אלו יוגה</a>


[2025-09-13 22:25:15] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:25:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg
[2025-09-13 22:25:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1757372976570_14.jpg
[2025-09-13 22:25:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/01/d7813d99-0abe-410f-8464-e70fce9f982e-e1757389322908.jpeg
[2025-09-13 22:25:15] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1756661464356_0.jpg
[2025-09-13 22:25:15] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:25:15] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg
[2025-09-13 22:25:15] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:25:15] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1757372976570_14.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/wsxc1757372976570_14.jpg
[2025-09-13 22:25:15] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:25:15] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2024/01/d7813d99-0abe-410f-8464-e70fce9f982e-e1757389322908.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2024/01/d7813d99-0abe-410f-8464-e70fce9f982e-e1757389322908.jpeg
[2025-09-13 22:25:15] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:25:15] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1756661464356_0.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/wsxc1756661464356_0.jpg
[2025-09-13 22:25:17] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_2f6666f6c1a93c9d737a0fad5f6bacea.jpg
[2025-09-13 22:25:17] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_2f6666f6c1a93c9d737a0fad5f6bacea.jpg
[2025-09-13 22:25:17] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_2f6666f6c1a93c9d737a0fad5f6bacea.jpg
[2025-09-13 22:25:17] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_2f6666f6c1a93c9d737a0fad5f6bacea.jpg
[2025-09-13 22:25:17] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:25:17] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:25:17] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2031213
content-type: multipart/form-data; boundary=------------------------307edc38f0603c67

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:17 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:17] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:25:17] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2031213
content-type: multipart/form-data; boundary=------------------------307edc38f0603c67

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:17 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:17] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:25:17] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1857
content-type: application/json; boundary=------------------------11a368ff7eebd31c

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:17 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:25:17] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:25:17] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4b1f0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1857
content-type: application/json; boundary=------------------------11a368ff7eebd31c

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:25:17 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:38] [INFO] 

Webhook processing started
[2025-09-13 22:26:38] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): אליס תמצאי לי ברברה
[2025-09-13 22:26:40] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "ברברה",
    "category": "",
    "brand": "ברברה",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:26:40] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:26:40] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:26:40] [INFO] Loading WordPress
[2025-09-13 22:26:40] [INFO] Loaded wp-load.php
[2025-09-13 22:26:40] [INFO] WordPress loaded
[2025-09-13 22:26:40] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:26:40] [INFO] Normalizing products.
[2025-09-13 22:26:40] [DEBUG] Classification Product: ברברה
[2025-09-13 22:26:40] [DEBUG] Classification Category: 
[2025-09-13 22:26:40] [DEBUG] Classification Brand: ברברה
[2025-09-13 22:26:40] [DEBUG] Classification Features: 
[2025-09-13 22:26:40] [DEBUG] Classification Gender: 
[2025-09-13 22:26:40] [DEBUG] Classification Filters: 
[2025-09-13 22:26:40] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fce0c0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11939 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:40] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fce0c0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11939 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:40] [DEBUG] Searching for: 'ברברה'
[2025-09-13 22:26:40] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:26:40] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:26:40] [INFO] Normalizing products.
[2025-09-13 22:26:40] [DEBUG] No results found using strategy: Original Product Search
[2025-09-13 22:26:40] [DEBUG] Searching by category: '' brand: 'ברברה' and gender ''
[2025-09-13 22:26:40] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:26:40] [INFO] WordPress wc_get_products found 0 products for: ' ברברה'
[2025-09-13 22:26:40] [INFO] Normalizing products.
[2025-09-13 22:26:40] [DEBUG] No results found using strategy: Category + Brand Search
[2025-09-13 22:26:40] [DEBUG] Searching by brand: 'ברברה' and gender ''
[2025-09-13 22:26:40] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:26:40] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:26:40] [INFO] Normalizing products.
[2025-09-13 22:26:40] [DEBUG] No results found using strategy: Brand Search
[2025-09-13 22:26:40] [DEBUG] Searching by category: '' and gender ''
[2025-09-13 22:26:40] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:26:40] [INFO] WordPress wc_get_products found 10 products for: ''
[2025-09-13 22:26:40] [INFO] Normalizing products.
[2025-09-13 22:26:40] [INFO] Found 10 products using strategy: Category Search
[2025-09-13 22:26:40] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a7%d7%a4%d7%95%d7%a6%d7%95%d7%9f/">מעיל קפוצון</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

2. <a href="https://dealimzoharim.com/product/%d7%98%d7%a8%d7%a0%d7%a5-%d7%96%d7%90%d7%a8%d7%94/">טרנץ זארה</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

3. <a href="https://dealimzoharim.com/product/%d7%92%d7%a7%d7%98%d7%90%d7%9c%d7%95-%d7%99%d7%95%d7%92%d7%94/">ג'קט ספורטיבי אלו יוגה</a>
איכות ללא פשרות – בדיוק כמו בתמונות!
כל מוצר נבדק בקפידה לפני שנשלח, כדי שתקבלו בדיוק את מה שהזמנתם.
שירות לקוחות זמין ומהיר – לכל שאלה, בקשה או תמונות נוספות.
זמני אספקה: טיפול בהזמנה 3–7 ימי עסקי

4. <a href="https://dealimzoharim.com/product/%d7%91%d7%99%d7%a8%d7%a7%d7%a0%d7%a9%d7%98%d7%95%d7%a7-%d7%9e%d7%95%d7%92%d7%91%d7%94%d7%95%d7%aa/">בירקנשטוק מוגבהות</a>
<b>בירקנשטוק מוגבהות</b>
מידות 35-44


[2025-09-13 22:26:40] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:26:40] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/4e4c683a-ca0c-4ad2-b1e5-8b436ec7979f.jpeg
[2025-09-13 22:26:40] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/9b7e89d5-96b5-40b7-ba09-6b2967c33fb1.jpeg
[2025-09-13 22:26:40] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/a3e354ac-ee09-452f-a071-97df458020dd.jpeg
[2025-09-13 22:26:40] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/07/02aa3d3d-e1720188597988.jpeg
[2025-09-13 22:26:40] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:26:40] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:26:40] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b0ea65b6fedd934ea160c2e97df646d5.jpg
[2025-09-13 22:26:40] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:26:40] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fc0550)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1811083
content-type: multipart/form-data; boundary=------------------------677500bd72165851

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:40] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fc0550)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1811083
content-type: multipart/form-data; boundary=------------------------677500bd72165851

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:40] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fc0550)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2424
content-type: application/json; boundary=------------------------8436a73ccd928a9b

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:26:40] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:26:40] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fc0550)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2424
content-type: application/json; boundary=------------------------8436a73ccd928a9b

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:26:40 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:35] [INFO] 

Webhook processing started
[2025-09-13 22:27:35] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי כפכפי ברברה
[2025-09-13 22:27:37] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "כפכפי ברברה",
    "category": "כפכפים",
    "brand": "ברברה",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:27:37] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:27:37] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:27:37] [INFO] Loading WordPress
[2025-09-13 22:27:37] [INFO] Loaded wp-load.php
[2025-09-13 22:27:37] [INFO] WordPress loaded
[2025-09-13 22:27:37] [INFO] WordPress wc_get_products found 0 products for: 'כפכפי ברברה'
[2025-09-13 22:27:37] [INFO] Normalizing products.
[2025-09-13 22:27:37] [DEBUG] Classification Product: כפכפי ברברה
[2025-09-13 22:27:37] [DEBUG] Classification Category: כפכפים
[2025-09-13 22:27:37] [DEBUG] Classification Brand: ברברה
[2025-09-13 22:27:37] [DEBUG] Classification Features: 
[2025-09-13 22:27:37] [DEBUG] Classification Gender: 
[2025-09-13 22:27:37] [DEBUG] Classification Filters: 
[2025-09-13 22:27:37] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:27:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11940 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:37] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:27:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11940 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:37] [DEBUG] Searching for: 'כפכפי ברברה'
[2025-09-13 22:27:37] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:27:37] [INFO] WordPress wc_get_products found 0 products for: 'כפכפי ברברה'
[2025-09-13 22:27:37] [INFO] Normalizing products.
[2025-09-13 22:27:37] [DEBUG] No results found using strategy: Original Product Search
[2025-09-13 22:27:37] [DEBUG] Searching by category: 'כפכפים' brand: 'ברברה' and gender ''
[2025-09-13 22:27:37] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:27:37] [INFO] WordPress wc_get_products found 0 products for: 'כפכפים ברברה'
[2025-09-13 22:27:37] [INFO] Normalizing products.
[2025-09-13 22:27:37] [DEBUG] No results found using strategy: Category + Brand Search
[2025-09-13 22:27:37] [DEBUG] Searching by brand: 'ברברה' and gender ''
[2025-09-13 22:27:37] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:27:37] [INFO] WordPress wc_get_products found 0 products for: 'ברברה'
[2025-09-13 22:27:37] [INFO] Normalizing products.
[2025-09-13 22:27:37] [DEBUG] No results found using strategy: Brand Search
[2025-09-13 22:27:37] [DEBUG] Searching by category: 'כפכפים' and gender ''
[2025-09-13 22:27:37] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:27:37] [INFO] WordPress wc_get_products found 10 products for: 'כפכפים'
[2025-09-13 22:27:37] [INFO] Normalizing products.
[2025-09-13 22:27:37] [INFO] Found 10 products using strategy: Category Search
[2025-09-13 22:27:37] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-ugg-%d7%99%d7%9c%d7%93%d7%99%d7%9d-6/">כפכפים UGG ילדים</a>
מידות 24-35

2. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-ugg-%d7%99%d7%9c%d7%93%d7%99%d7%9d-3/">כפכפים UGG ילדים</a>
מידות 21-35

3. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-ugg-16/">כפכפים UGG</a>

4. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99%d7%95%d7%aa-%d7%91%d7%99%d7%a8%d7%a7%d7%a0%d7%a9%d7%98%d7%95%d7%a7-%d7%94%d7%a2%d7%aa%d7%a7/">כפכפים פרוותיות בירקנשטוק</a>
מידות 35-44


[2025-09-13 22:27:37] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:27:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/Y1PAQ07YLFWI1S8I6ZEG.jpg
[2025-09-13 22:27:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/主图-18.jpg
[2025-09-13 22:27:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/61b7d3.jpeg
[2025-09-13 22:27:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/01/e4124c98.jpg
[2025-09-13 22:27:37] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:27:37] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/Y1PAQ07YLFWI1S8I6ZEG.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/Y1PAQ07YLFWI1S8I6ZEG.jpg
[2025-09-13 22:27:37] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:27:37] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/主图-18.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/主图-18.jpg
[2025-09-13 22:27:37] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:27:37] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/08/61b7d3.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/08/61b7d3.jpeg
[2025-09-13 22:27:37] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:27:37] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/01/e4124c98.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/01/e4124c98.jpg
[2025-09-13 22:27:38] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_750d74d806338b22a7abf35825cd5bee.jpg
[2025-09-13 22:27:38] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_750d74d806338b22a7abf35825cd5bee.jpg
[2025-09-13 22:27:38] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_750d74d806338b22a7abf35825cd5bee.jpg
[2025-09-13 22:27:38] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_750d74d806338b22a7abf35825cd5bee.jpg
[2025-09-13 22:27:38] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:27:38] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:27:38] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2837758
content-type: multipart/form-data; boundary=------------------------200034aed60a0535

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:38 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:38] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:27:38] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2837758
content-type: multipart/form-data; boundary=------------------------200034aed60a0535

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:38 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:38] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:27:38] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1617
content-type: application/json; boundary=------------------------0532d5c98bb07e10

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:38 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:27:38] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:27:38] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f04610)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1617
content-type: application/json; boundary=------------------------0532d5c98bb07e10

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:27:38 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:45] [INFO] 

Webhook processing started
[2025-09-13 22:43:45] [INFO] Callback query received: ראלף לורן from chat -1002637696817
[2025-09-13 22:43:45] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:45] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c9d070)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:45 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:45] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:43:45] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c9d070)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:45 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:45] [INFO] STS - Before searchProducts ראלף לורן
[2025-09-13 22:43:45] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:43:45] [INFO] Loading WordPress
[2025-09-13 22:43:45] [INFO] Loaded wp-load.php
[2025-09-13 22:43:45] [INFO] WordPress loaded
[2025-09-13 22:43:45] [INFO] WordPress wc_get_products found 10 products for: 'ראלף לורן'
[2025-09-13 22:43:45] [INFO] Normalizing products.
[2025-09-13 22:43:45] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%a1%d7%95%d7%95%d7%98%d7%a9%d7%99%d7%a8%d7%98-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f/">סווטשירט  ראלף לורן</a>
מידות : <b>S-L</b>

2. <a href="https://dealimzoharim.com/product/%d7%aa%d7%99%d7%a7-%d7%a9%d7%a7-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-10/">תיק שק ראלף לורן</a>

3. <a href="https://dealimzoharim.com/product/%d7%a1%d7%a8%d7%99%d7%92-%d7%a0%d7%a9%d7%99%d7%9d-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-5/">סריג נשים ראלף לורן</a>
S-XL

4. <a href="https://dealimzoharim.com/product/%d7%a7%d7%a4%d7%95%d7%a6%d7%95%d7%9f-%d7%a4%d7%95%d7%9c%d7%95-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-2/">קפוצון  ראלף לורן</a>
מידות : <b>M-2XL</b>


[2025-09-13 22:43:45] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:43:45] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1756927529404_1.jpg
[2025-09-13 22:43:45] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/1d0b2de9.jpg
[2025-09-13 22:43:45] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1757448206114_2.jpg
[2025-09-13 22:43:45] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/41.jpeg
[2025-09-13 22:43:45] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:43:45] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1756927529404_1.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/wsxc1756927529404_1.jpg
[2025-09-13 22:43:45] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:43:45] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/1d0b2de9.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/1d0b2de9.jpg
[2025-09-13 22:43:45] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:43:45] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1757448206114_2.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/wsxc1757448206114_2.jpg
[2025-09-13 22:43:45] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:43:45] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/09/41.jpeg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/09/41.jpeg
[2025-09-13 22:43:46] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:46] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:46] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:46] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:46] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:43:46] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:46] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4bc90)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2703898
content-type: multipart/form-data; boundary=------------------------180672e20cdf1cc6

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:46 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:46] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:43:46] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4bc90)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2703898
content-type: multipart/form-data; boundary=------------------------180672e20cdf1cc6

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:46 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:46] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:46] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f96bc0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%2595%25d7%2595%25d7%2598%25d7%25a9%25d7%2599%25d7%25a8%25d7%2598-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f%2F%22%3E%D7%A1%D7%95%D7%95%D7%98%D7%A9%D7%99%D7%A8%D7%98++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3ES-L%3C%2Fb%3E%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25aa%25d7%2599%25d7%25a7-%25d7%25a9%25d7%25a7-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-10%2F%22%3E%D7%AA%D7%99%D7%A7+%D7%A9%D7%A7+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%25a8%25d7%2599%25d7%2592-%25d7%25a0%25d7%25a9%25d7%2599%25d7%259d-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-5%2F%22%3E%D7%A1%D7%A8%D7%99%D7%92+%D7%A0%D7%A9%D7%99%D7%9D+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0AS-XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a7%25d7%25a4%25d7%2595%25d7%25a6%25d7%2595%25d7%259f-%25d7%25a4%25d7%2595%25d7%259c%25d7%2595-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-2%2F%22%3E%D7%A7%D7%A4%D7%95%D7%A6%D7%95%D7%9F++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3EM-2XL%3C%2Fb%3E%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:46 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:46] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:43:46] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f96bc0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%2595%25d7%2595%25d7%2598%25d7%25a9%25d7%2599%25d7%25a8%25d7%2598-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f%2F%22%3E%D7%A1%D7%95%D7%95%D7%98%D7%A9%D7%99%D7%A8%D7%98++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3ES-L%3C%2Fb%3E%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25aa%25d7%2599%25d7%25a7-%25d7%25a9%25d7%25a7-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-10%2F%22%3E%D7%AA%D7%99%D7%A7+%D7%A9%D7%A7+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%25a8%25d7%2599%25d7%2592-%25d7%25a0%25d7%25a9%25d7%2599%25d7%259d-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-5%2F%22%3E%D7%A1%D7%A8%D7%99%D7%92+%D7%A0%D7%A9%D7%99%D7%9D+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0AS-XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a7%25d7%25a4%25d7%2595%25d7%25a6%25d7%2595%25d7%259f-%25d7%25a4%25d7%2595%25d7%259c%25d7%2595-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-2%2F%22%3E%D7%A7%D7%A4%D7%95%D7%A6%D7%95%D7%9F++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3EM-2XL%3C%2Fb%3E%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:46 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [INFO] 

Webhook processing started
[2025-09-13 22:43:55] [INFO] Callback query received: ראלף לורן from chat -1002637696817
[2025-09-13 22:43:55] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f0e5e0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f0e5e0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [INFO] STS - Before searchProducts ראלף לורן
[2025-09-13 22:43:55] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:43:55] [INFO] Loading WordPress
[2025-09-13 22:43:55] [INFO] Loaded wp-load.php
[2025-09-13 22:43:55] [INFO] WordPress loaded
[2025-09-13 22:43:55] [INFO] WordPress wc_get_products found 10 products for: 'ראלף לורן'
[2025-09-13 22:43:55] [INFO] Normalizing products.
[2025-09-13 22:43:55] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%a1%d7%95%d7%95%d7%98%d7%a9%d7%99%d7%a8%d7%98-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f/">סווטשירט  ראלף לורן</a>
מידות : <b>S-L</b>

2. <a href="https://dealimzoharim.com/product/%d7%aa%d7%99%d7%a7-%d7%a9%d7%a7-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-10/">תיק שק ראלף לורן</a>

3. <a href="https://dealimzoharim.com/product/%d7%a1%d7%a8%d7%99%d7%92-%d7%a0%d7%a9%d7%99%d7%9d-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-5/">סריג נשים ראלף לורן</a>
S-XL

4. <a href="https://dealimzoharim.com/product/%d7%a7%d7%a4%d7%95%d7%a6%d7%95%d7%9f-%d7%a4%d7%95%d7%9c%d7%95-%d7%a8%d7%90%d7%9c%d7%a3-%d7%9c%d7%95%d7%a8%d7%9f-2/">קפוצון  ראלף לורן</a>
מידות : <b>M-2XL</b>


[2025-09-13 22:43:55] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:43:55] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1756927529404_1.jpg
[2025-09-13 22:43:55] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/1d0b2de9.jpg
[2025-09-13 22:43:55] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/wsxc1757448206114_2.jpg
[2025-09-13 22:43:55] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/41.jpeg
[2025-09-13 22:43:55] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:55] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:55] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_b3eb547e32767ff0762e267d990b490f.jpg
[2025-09-13 22:43:55] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:43:55] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f21770)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2703898
content-type: multipart/form-data; boundary=------------------------88940a5962b3299d

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f21770)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2703898
content-type: multipart/form-data; boundary=------------------------88940a5962b3299d

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f21770)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%2595%25d7%2595%25d7%2598%25d7%25a9%25d7%2599%25d7%25a8%25d7%2598-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f%2F%22%3E%D7%A1%D7%95%D7%95%D7%98%D7%A9%D7%99%D7%A8%D7%98++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3ES-L%3C%2Fb%3E%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25aa%25d7%2599%25d7%25a7-%25d7%25a9%25d7%25a7-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-10%2F%22%3E%D7%AA%D7%99%D7%A7+%D7%A9%D7%A7+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%25a8%25d7%2599%25d7%2592-%25d7%25a0%25d7%25a9%25d7%2599%25d7%259d-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-5%2F%22%3E%D7%A1%D7%A8%D7%99%D7%92+%D7%A0%D7%A9%D7%99%D7%9D+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0AS-XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a7%25d7%25a4%25d7%2595%25d7%25a6%25d7%2595%25d7%259f-%25d7%25a4%25d7%2595%25d7%259c%25d7%2595-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-2%2F%22%3E%D7%A7%D7%A4%D7%95%D7%A6%D7%95%D7%9F++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3EM-2XL%3C%2Fb%3E%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:43:55] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:43:55] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f21770)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%2595%25d7%2595%25d7%2598%25d7%25a9%25d7%2599%25d7%25a8%25d7%2598-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f%2F%22%3E%D7%A1%D7%95%D7%95%D7%98%D7%A9%D7%99%D7%A8%D7%98++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3ES-L%3C%2Fb%3E%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25aa%25d7%2599%25d7%25a7-%25d7%25a9%25d7%25a7-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-10%2F%22%3E%D7%AA%D7%99%D7%A7+%D7%A9%D7%A7+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a1%25d7%25a8%25d7%2599%25d7%2592-%25d7%25a0%25d7%25a9%25d7%2599%25d7%259d-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-5%2F%22%3E%D7%A1%D7%A8%D7%99%D7%92+%D7%A0%D7%A9%D7%99%D7%9D+%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0AS-XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%25a7%25d7%25a4%25d7%2595%25d7%25a6%25d7%2595%25d7%259f-%25d7%25a4%25d7%2595%25d7%259c%25d7%2595-%25d7%25a8%25d7%2590%25d7%259c%25d7%25a3-%25d7%259c%25d7%2595%25d7%25a8%25d7%259f-2%2F%22%3E%D7%A7%D7%A4%D7%95%D7%A6%D7%95%D7%9F++%D7%A8%D7%90%D7%9C%D7%A3+%D7%9C%D7%95%D7%A8%D7%9F%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+%3A+%3Cb%3EM-2XL%3C%2Fb%3E%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:43:55 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:47] [INFO] 

Webhook processing started
[2025-09-13 22:46:47] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי כפכפי ברברי
[2025-09-13 22:46:48] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "כפכפי ברברי",
    "category": "נעליים",
    "brand": "ברברי",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:46:48] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:46:48] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:46:48] [INFO] Loading WordPress
[2025-09-13 22:46:49] [INFO] Loaded wp-load.php
[2025-09-13 22:46:49] [INFO] WordPress loaded
[2025-09-13 22:46:49] [INFO] WordPress wc_get_products found 2 products for: 'כפכפי ברברי'
[2025-09-13 22:46:49] [INFO] Normalizing products.
[2025-09-13 22:46:49] [DEBUG] Classification Product: כפכפי ברברי
[2025-09-13 22:46:49] [DEBUG] Classification Category: נעליים
[2025-09-13 22:46:49] [DEBUG] Classification Brand: ברברי
[2025-09-13 22:46:49] [DEBUG] Classification Features: 
[2025-09-13 22:46:49] [DEBUG] Classification Gender: 
[2025-09-13 22:46:49] [DEBUG] Classification Filters: 
[2025-09-13 22:46:49] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11941 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:49] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11941 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:49] [DEBUG] Searching for: 'כפכפי ברברי'
[2025-09-13 22:46:49] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:46:49] [INFO] WordPress wc_get_products found 2 products for: 'כפכפי ברברי'
[2025-09-13 22:46:49] [INFO] Normalizing products.
[2025-09-13 22:46:49] [INFO] Found 2 products using strategy: Original Product Search
[2025-09-13 22:46:49] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99-%d7%91%d7%a8%d7%91%d7%a8%d7%99/">כפכפים ברברי</a>
<b>כפכפי ברברי</b>
מידות 36-45

2. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%91%d7%a8%d7%91%d7%a8%d7%99-5/">כפכפים ברברי</a>
<b>כפכפים ברברי</b>
מידות 36-45


[2025-09-13 22:46:49] [INFO] Starting image stitching process with 2 images
[2025-09-13 22:46:49] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2021/07/eef9e700.jpg
[2025-09-13 22:46:49] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/06/fe7a1c9a-600x800-1.jpg
[2025-09-13 22:46:49] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:46:49] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2021/07/eef9e700.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2021/07/eef9e700.jpg
[2025-09-13 22:46:49] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-13 22:46:49] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2023/06/fe7a1c9a-600x800-1.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2023/06/fe7a1c9a-600x800-1.jpg
[2025-09-13 22:46:49] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_d65131d62d729cf6a7ad1e9de62efe70.jpg
[2025-09-13 22:46:49] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_d65131d62d729cf6a7ad1e9de62efe70.jpg
[2025-09-13 22:46:49] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_d65131d62d729cf6a7ad1e9de62efe70.jpg
[2025-09-13 22:46:49] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_d65131d62d729cf6a7ad1e9de62efe70.jpg
[2025-09-13 22:46:49] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:46:49] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 305294
content-type: multipart/form-data; boundary=------------------------0167e9ca3de4e901

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:49] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 305294
content-type: multipart/form-data; boundary=------------------------0167e9ca3de4e901

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:49] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1256
content-type: application/json; boundary=------------------------b887bf13a631bae2

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:46:49] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:46:49] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c98fe0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1256
content-type: application/json; boundary=------------------------b887bf13a631bae2

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:46:49 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:17] [INFO] 

Webhook processing started
[2025-09-13 22:58:17] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי ugg
[2025-09-13 22:58:18] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "ugg",
    "category": "",
    "brand": "אג",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-13 22:58:18] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-13 22:58:18] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:58:18] [INFO] Loading WordPress
[2025-09-13 22:58:18] [INFO] Loaded wp-load.php
[2025-09-13 22:58:18] [INFO] WordPress loaded
[2025-09-13 22:58:18] [INFO] WordPress wc_get_products found 10 products for: 'ugg'
[2025-09-13 22:58:18] [INFO] Normalizing products.
[2025-09-13 22:58:19] [DEBUG] Classification Product: ugg
[2025-09-13 22:58:19] [DEBUG] Classification Category: 
[2025-09-13 22:58:19] [DEBUG] Classification Brand: אג
[2025-09-13 22:58:19] [DEBUG] Classification Features: 
[2025-09-13 22:58:19] [DEBUG] Classification Gender: 
[2025-09-13 22:58:19] [DEBUG] Classification Filters: 
[2025-09-13 22:58:19] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f2bd40)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11942 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:19] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f2bd40)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11942 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:19] [DEBUG] Searching for: 'ugg'
[2025-09-13 22:58:19] [INFO] Using WordPress built-in function for production mode
[2025-09-13 22:58:19] [INFO] WordPress wc_get_products found 10 products for: 'ugg'
[2025-09-13 22:58:19] [INFO] Normalizing products.
[2025-09-13 22:58:19] [INFO] Found 10 products using strategy: Original Product Search
[2025-09-13 22:58:19] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99-%d7%91%d7%99%d7%aa-ugg-7/">נעלי בית UGG</a>

2. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99%d7%99%d7%9d-ugg-%d7%99%d7%9c%d7%93%d7%99%d7%9d/">נעליים UGG ילדים</a>
מידות 21-43

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%92%d7%a4%d7%99%d7%99%d7%9d-ugg-%d7%99%d7%9c%d7%93%d7%99%d7%9d/">מגפיים UGG ילדים</a>
מידות 21-43

4. <a href="https://dealimzoharim.com/product/ugg-%d7%9c%d7%aa%d7%99%d7%a0%d7%95%d7%a7%d7%95%d7%aa/">UGG לתינוקות</a>


[2025-09-13 22:58:19] [INFO] Starting image stitching process with 4 images
[2025-09-13 22:58:19] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/07cd8e29.jpg
[2025-09-13 22:58:19] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/主图-19-1024x1024-1.jpg
[2025-09-13 22:58:19] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/主图-5-1024x1024-1.jpeg
[2025-09-13 22:58:19] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/VPB062UPDKPP1O6_SF1XK.jpg
[2025-09-13 22:58:19] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_edc333df1245162b56cfc074f48f3072.jpg
[2025-09-13 22:58:19] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_edc333df1245162b56cfc074f48f3072.jpg
[2025-09-13 22:58:19] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_edc333df1245162b56cfc074f48f3072.jpg
[2025-09-13 22:58:19] [DEBUG] Uploading files with multipart/form-data
[2025-09-13 22:58:19] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f859c0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1037883
content-type: multipart/form-data; boundary=------------------------d31c54ea58a24912

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:19] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f859c0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1037883
content-type: multipart/form-data; boundary=------------------------d31c54ea58a24912

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:19] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f2bd40)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1249
content-type: application/json; boundary=------------------------7d0f0c7a0d2bd36b

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-13 22:58:19] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-13 22:58:19] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f2bd40)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1249
content-type: application/json; boundary=------------------------7d0f0c7a0d2bd36b

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sat, 13 Sep 2025 22:58:19 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 00:18:43] [INFO] 

Webhook processing started
[2025-09-14 00:18:57] [INFO] 

Webhook processing started
[2025-09-14 00:18:57] [INFO] Group message from אריק מזרחי in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תיק לואי ויטון
[2025-09-14 00:18:59] [DEBUG] Raw AI classification response: '{
    "intent": "Other"
}'
[2025-09-14 00:18:59] [DEBUG] Handling Other message - Other
[2025-09-14 00:18:59] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 00:18:59] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5ad30)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 00:18:59 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 00:18:59] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 00:18:59] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5ad30)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 00:18:59 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:12] [INFO] 

Webhook processing started
[2025-09-14 04:17:12] [INFO] Group message from Me E in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי נעלי אלו
[2025-09-14 04:17:13] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "נעלי אלו",
    "category": "נעליים",
    "brand": "אלו",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-14 04:17:13] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-14 04:17:13] [INFO] Using WordPress built-in function for production mode
[2025-09-14 04:17:13] [INFO] Loading WordPress
[2025-09-14 04:17:14] [INFO] Loaded wp-load.php
[2025-09-14 04:17:14] [INFO] WordPress loaded
[2025-09-14 04:17:14] [INFO] WordPress wc_get_products found 10 products for: 'נעלי אלו'
[2025-09-14 04:17:14] [INFO] Normalizing products.
[2025-09-14 04:17:14] [DEBUG] Classification Product: נעלי אלו
[2025-09-14 04:17:14] [DEBUG] Classification Category: נעליים
[2025-09-14 04:17:14] [DEBUG] Classification Brand: אלו
[2025-09-14 04:17:14] [DEBUG] Classification Features: 
[2025-09-14 04:17:14] [DEBUG] Classification Gender: 
[2025-09-14 04:17:14] [DEBUG] Classification Filters: 
[2025-09-14 04:17:14] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07efa6b0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11945 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:14] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07efa6b0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11945 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:14] [DEBUG] Searching for: 'נעלי אלו'
[2025-09-14 04:17:14] [INFO] Using WordPress built-in function for production mode
[2025-09-14 04:17:14] [INFO] WordPress wc_get_products found 10 products for: 'נעלי אלו'
[2025-09-14 04:17:14] [INFO] Normalizing products.
[2025-09-14 04:17:14] [INFO] Found 10 products using strategy: Original Product Search
[2025-09-14 04:17:14] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99-%d7%91%d7%99%d7%aa-ugg-7/">נעלי בית UGG</a>

2. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99%d7%99%d7%9d-ugg-%d7%99%d7%9c%d7%93%d7%99%d7%9d/">נעליים UGG ילדים</a>
מידות 21-43

3. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99-%d7%a4%d7%95%d7%9e%d7%94-%d7%99%d7%9c%d7%93%d7%99%d7%9d-2/">נעלי פומה ילדים</a>
מידות 22-35

4. <a href="https://dealimzoharim.com/product/%d7%a0%d7%a2%d7%9c%d7%99%d7%99%d7%9d-%d7%90%d7%a1%d7%99%d7%a7%d7%a1-%d7%99%d7%9c%d7%93%d7%99%d7%9d/">נעליים אסיקס ילדים</a>
מידות 26-35


[2025-09-14 04:17:14] [INFO] Starting image stitching process with 4 images
[2025-09-14 04:17:14] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/07cd8e29.jpg
[2025-09-14 04:17:14] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/主图-19-1024x1024-1.jpg
[2025-09-14 04:17:14] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/808006b2.jpg
[2025-09-14 04:17:14] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/09/54582012.jpeg
[2025-09-14 04:17:14] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_820e8d2376dbc7f90333aa80148049b2.jpg
[2025-09-14 04:17:14] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_820e8d2376dbc7f90333aa80148049b2.jpg
[2025-09-14 04:17:14] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_820e8d2376dbc7f90333aa80148049b2.jpg
[2025-09-14 04:17:14] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 04:17:14] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07ec54b0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2607453
content-type: multipart/form-data; boundary=------------------------ae0a32c2aad03516

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:14] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07ec54b0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 2607453
content-type: multipart/form-data; boundary=------------------------ae0a32c2aad03516

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:14] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07efa6b0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1529
content-type: application/json; boundary=------------------------b4cdd475d8de7cf6

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 04:17:14] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 04:17:14] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07efa6b0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1529
content-type: application/json; boundary=------------------------b4cdd475d8de7cf6

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 04:17:14 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:21:42] [INFO] 

Webhook processing started
[2025-09-14 06:36:08] [INFO] 

Webhook processing started
[2025-09-14 06:36:08] [INFO] Private message from ZarAli (509736022): /start
[2025-09-14 06:36:09] [DEBUG] Raw AI classification response: '{
    "intent": "Other"
}'
[2025-09-14 06:36:09] [DEBUG] Handling Other message - Other
[2025-09-14 06:36:09] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:36:09] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c480)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=509736022&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:36:09 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:36:09] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:36:09] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c480)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=509736022&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:36:09 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:24] [INFO] 

Webhook processing started
[2025-09-14 06:37:24] [INFO] Callback query received: אג from chat -1002637696817
[2025-09-14 06:37:24] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:24] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f0fa60)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:24 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:24] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:24] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f0fa60)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:24 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:24] [INFO] STS - Before searchProducts אג
[2025-09-14 06:37:24] [INFO] Using WordPress built-in function for production mode
[2025-09-14 06:37:24] [INFO] Loading WordPress
[2025-09-14 06:37:25] [INFO] Loaded wp-load.php
[2025-09-14 06:37:25] [INFO] WordPress loaded
[2025-09-14 06:37:25] [INFO] WordPress wc_get_products found 10 products for: 'אג'
[2025-09-14 06:37:25] [INFO] Normalizing products.
[2025-09-14 06:37:25] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99-ugg-4/">מעיל פרוותי UGG</a>
<b>מעיל פרוותי האג מדהים חדש</b>
מידות XS-L

2. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a1%d7%92%d7%a8%d7%95%d7%aa-%d7%9c%d7%9e%d7%a9%d7%a7%d7%a4%d7%99-%d7%a8%d7%90%d7%99%d7%94-%d7%95%d7%a8%d7%a1%d7%a6%d7%94/">מסגרות למשקפי ראיה בלנסיאגה</a>

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%90%d7%a8%d7%96-%d7%91%d7%95%d7%a7%d7%a1%d7%a8%d7%99%d7%9d-%d7%91%d7%9c%d7%a0%d7%a1%d7%99%d7%90%d7%92%d7%94/">מארז בוקסרים בלנסיאגה</a>
מידות M-2XL

4. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c%d7%99%d7%9d-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99%d7%99%d7%9d-%d7%9e%d7%9e%d7%95%d7%aa%d7%92%d7%99%d7%9d-%d7%a4%d7%a0%d7%93%d7%99-%d7%93%d7%99%d7%95%d7%a8-%d7%91%d7%9c%d7%a0/">מעילים פרוותיים ממותגים</a>
<b>מעילים פרוותיים ממותגים פנדי דיור בלנסיאגה </b>
מידות M-5XL


[2025-09-14 06:37:25] [INFO] Starting image stitching process with 4 images
[2025-09-14 06:37:25] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/08/c09b6c28.jpg
[2025-09-14 06:37:25] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/03/d79a8bc4.jpg
[2025-09-14 06:37:25] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/1389f9a2.jpg
[2025-09-14 06:37:25] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/09/3fe92caa.jpg
[2025-09-14 06:37:25] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:25] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:25] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:25] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 06:37:25] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:25] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66590)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------23368723bea0bf9b

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:25 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:25] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-14 06:37:25] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66590)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------23368723bea0bf9b

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:25 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:25] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:25] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66590)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:25 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:25] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:25] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66590)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:25 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [INFO] 

Webhook processing started
[2025-09-14 06:37:27] [INFO] Callback query received: אג from chat -1002637696817
[2025-09-14 06:37:27] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5ca50)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5ca50)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [INFO] STS - Before searchProducts אג
[2025-09-14 06:37:27] [INFO] Using WordPress built-in function for production mode
[2025-09-14 06:37:27] [INFO] Loading WordPress
[2025-09-14 06:37:27] [INFO] Loaded wp-load.php
[2025-09-14 06:37:27] [INFO] WordPress loaded
[2025-09-14 06:37:27] [INFO] WordPress wc_get_products found 10 products for: 'אג'
[2025-09-14 06:37:27] [INFO] Normalizing products.
[2025-09-14 06:37:27] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99-ugg-4/">מעיל פרוותי UGG</a>
<b>מעיל פרוותי האג מדהים חדש</b>
מידות XS-L

2. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a1%d7%92%d7%a8%d7%95%d7%aa-%d7%9c%d7%9e%d7%a9%d7%a7%d7%a4%d7%99-%d7%a8%d7%90%d7%99%d7%94-%d7%95%d7%a8%d7%a1%d7%a6%d7%94/">מסגרות למשקפי ראיה בלנסיאגה</a>

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%90%d7%a8%d7%96-%d7%91%d7%95%d7%a7%d7%a1%d7%a8%d7%99%d7%9d-%d7%91%d7%9c%d7%a0%d7%a1%d7%99%d7%90%d7%92%d7%94/">מארז בוקסרים בלנסיאגה</a>
מידות M-2XL

4. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c%d7%99%d7%9d-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99%d7%99%d7%9d-%d7%9e%d7%9e%d7%95%d7%aa%d7%92%d7%99%d7%9d-%d7%a4%d7%a0%d7%93%d7%99-%d7%93%d7%99%d7%95%d7%a8-%d7%91%d7%9c%d7%a0/">מעילים פרוותיים ממותגים</a>
<b>מעילים פרוותיים ממותגים פנדי דיור בלנסיאגה </b>
מידות M-5XL


[2025-09-14 06:37:27] [INFO] Starting image stitching process with 4 images
[2025-09-14 06:37:27] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/08/c09b6c28.jpg
[2025-09-14 06:37:27] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/03/d79a8bc4.jpg
[2025-09-14 06:37:27] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/1389f9a2.jpg
[2025-09-14 06:37:27] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/09/3fe92caa.jpg
[2025-09-14 06:37:27] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:27] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:27] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:27] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 06:37:27] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c37d30)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------b9f34df7b23c92fc

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c37d30)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------b9f34df7b23c92fc

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:27] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:27] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:27 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:36] [INFO] 

Webhook processing started
[2025-09-14 06:37:36] [INFO] Callback query received: אג from chat -1002637696817
[2025-09-14 06:37:36] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:36] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:36 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:36] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:36] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9E%D7%99%D7%93+%D7%9E%D7%97%D7%A4%D7%A9%D7%AA+%D7%A2%D7%91%D7%95%D7%A8%D7%9A+%D7%A2%D7%95%D7%93+%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D...&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:36 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:36] [INFO] STS - Before searchProducts אג
[2025-09-14 06:37:36] [INFO] Using WordPress built-in function for production mode
[2025-09-14 06:37:36] [INFO] Loading WordPress
[2025-09-14 06:37:37] [INFO] Loaded wp-load.php
[2025-09-14 06:37:37] [INFO] WordPress loaded
[2025-09-14 06:37:37] [INFO] WordPress wc_get_products found 10 products for: 'אג'
[2025-09-14 06:37:37] [INFO] Normalizing products.
[2025-09-14 06:37:37] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99-ugg-4/">מעיל פרוותי UGG</a>
<b>מעיל פרוותי האג מדהים חדש</b>
מידות XS-L

2. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a1%d7%92%d7%a8%d7%95%d7%aa-%d7%9c%d7%9e%d7%a9%d7%a7%d7%a4%d7%99-%d7%a8%d7%90%d7%99%d7%94-%d7%95%d7%a8%d7%a1%d7%a6%d7%94/">מסגרות למשקפי ראיה בלנסיאגה</a>

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%90%d7%a8%d7%96-%d7%91%d7%95%d7%a7%d7%a1%d7%a8%d7%99%d7%9d-%d7%91%d7%9c%d7%a0%d7%a1%d7%99%d7%90%d7%92%d7%94/">מארז בוקסרים בלנסיאגה</a>
מידות M-2XL

4. <a href="https://dealimzoharim.com/product/%d7%9e%d7%a2%d7%99%d7%9c%d7%99%d7%9d-%d7%a4%d7%a8%d7%95%d7%95%d7%aa%d7%99%d7%99%d7%9d-%d7%9e%d7%9e%d7%95%d7%aa%d7%92%d7%99%d7%9d-%d7%a4%d7%a0%d7%93%d7%99-%d7%93%d7%99%d7%95%d7%a8-%d7%91%d7%9c%d7%a0/">מעילים פרוותיים ממותגים</a>
<b>מעילים פרוותיים ממותגים פנדי דיור בלנסיאגה </b>
מידות M-5XL


[2025-09-14 06:37:37] [INFO] Starting image stitching process with 4 images
[2025-09-14 06:37:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/08/c09b6c28.jpg
[2025-09-14 06:37:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/03/d79a8bc4.jpg
[2025-09-14 06:37:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/1389f9a2.jpg
[2025-09-14 06:37:37] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/09/3fe92caa.jpg
[2025-09-14 06:37:37] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:37] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:37] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_789fd9f5e687538856b68de0662848f5.jpg
[2025-09-14 06:37:37] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 06:37:37] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------341eb682f92df6c0

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:37] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-14 06:37:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1002854
content-type: multipart/form-data; boundary=------------------------341eb682f92df6c0

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:37] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 06:37:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 06:37:37] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 06:37:37] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07fba920)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%F0%9F%93%8B+%3Cb%3E%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D+%D7%A9%D7%90%D7%9C%D7%99%D7%A1+%D7%9E%D7%A6%D7%90%D7%94+%D7%A2%D7%91%D7%95%D7%A8%D7%9A%3A%3C%2Fb%3E%0A%0A1.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599-ugg-4%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+UGG%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99+%D7%94%D7%90%D7%92+%D7%9E%D7%93%D7%94%D7%99%D7%9D+%D7%97%D7%93%D7%A9%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+XS-L%0A%0A2.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a1%25d7%2592%25d7%25a8%25d7%2595%25d7%25aa-%25d7%259c%25d7%259e%25d7%25a9%25d7%25a7%25d7%25a4%25d7%2599-%25d7%25a8%25d7%2590%25d7%2599%25d7%2594-%25d7%2595%25d7%25a8%25d7%25a1%25d7%25a6%25d7%2594%2F%22%3E%D7%9E%D7%A1%D7%92%D7%A8%D7%95%D7%AA+%D7%9C%D7%9E%D7%A9%D7%A7%D7%A4%D7%99+%D7%A8%D7%90%D7%99%D7%94+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%0A3.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%2590%25d7%25a8%25d7%2596-%25d7%2591%25d7%2595%25d7%25a7%25d7%25a1%25d7%25a8%25d7%2599%25d7%259d-%25d7%2591%25d7%259c%25d7%25a0%25d7%25a1%25d7%2599%25d7%2590%25d7%2592%25d7%2594%2F%22%3E%D7%9E%D7%90%D7%A8%D7%96+%D7%91%D7%95%D7%A7%D7%A1%D7%A8%D7%99%D7%9D+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94%3C%2Fa%3E%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-2XL%0A%0A4.+%3Ca+href%3D%22https%3A%2F%2Fdealimzoharim.com%2Fproduct%2F%25d7%259e%25d7%25a2%25d7%2599%25d7%259c%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a8%25d7%2595%25d7%2595%25d7%25aa%25d7%2599%25d7%2599%25d7%259d-%25d7%259e%25d7%259e%25d7%2595%25d7%25aa%25d7%2592%25d7%2599%25d7%259d-%25d7%25a4%25d7%25a0%25d7%2593%25d7%2599-%25d7%2593%25d7%2599%25d7%2595%25d7%25a8-%25d7%2591%25d7%259c%25d7%25a0%2F%22%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D%3C%2Fa%3E%0A%3Cb%3E%D7%9E%D7%A2%D7%99%D7%9C%D7%99%D7%9D+%D7%A4%D7%A8%D7%95%D7%95%D7%AA%D7%99%D7%99%D7%9D+%D7%9E%D7%9E%D7%95%D7%AA%D7%92%D7%99%D7%9D+%D7%A4%D7%A0%D7%93%D7%99+%D7%93%D7%99%D7%95%D7%A8+%D7%91%D7%9C%D7%A0%D7%A1%D7%99%D7%90%D7%92%D7%94+%3C%2Fb%3E%0D%0A%D7%9E%D7%99%D7%93%D7%95%D7%AA+M-5XL%0A%0A&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 06:37:37 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 07:03:52] [INFO] 

Webhook processing started
[2025-09-14 07:03:52] [INFO] Group message from Natali Haya in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): Prada
[2025-09-14 07:03:53] [DEBUG] Raw AI classification response: '{
    "intent": "Other"
}'
[2025-09-14 07:03:53] [DEBUG] Handling Other message - Other
[2025-09-14 07:03:53] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 07:03:53] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07d92f90)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 07:03:53 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 07:03:53] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 07:03:53] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07d92f90)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%D7%9B%D7%93%D7%99+%D7%9C%D7%A2%D7%96%D7%95%D7%A8+%D7%9C%D7%90%D7%9C%D7%99%D7%A1+%D7%94%D7%A2%D7%95%D7%96%D7%A8%D7%AA+%D7%A9%D7%9C+%D7%93%D7%99%D7%90%D7%A0%D7%94+%D7%90%D7%A0%D7%90+%D7%A8%D7%A9%D7%9E%D7%95+%3Cb%3E%D7%AA%D7%9E%D7%A6%D7%90%D7%99+%D7%9C%D7%99+%2B+%D7%94%D7%9E%D7%95%D7%A6%D7%A8+%D7%A9%D7%90%D7%AA%D7%9D+%D7%9E%D7%97%D7%A4%D7%A9%D7%99%D7%9D%3C%2Fb%3E&parse_mode=HTML HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 07:03:53 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:14:58] [INFO] 

Webhook processing started
[2025-09-14 08:14:58] [INFO] Group message from עיצוב הבית in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי שעונים
[2025-09-14 08:14:59] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "שעונים",
    "category": "שעונים",
    "brand": "",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-14 08:14:59] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-14 08:14:59] [INFO] Using WordPress built-in function for production mode
[2025-09-14 08:14:59] [INFO] Loading WordPress
[2025-09-14 08:15:00] [INFO] Loaded wp-load.php
[2025-09-14 08:15:00] [INFO] WordPress loaded
[2025-09-14 08:15:00] [INFO] WordPress wc_get_products found 10 products for: 'שעונים'
[2025-09-14 08:15:00] [INFO] Normalizing products.
[2025-09-14 08:15:00] [DEBUG] Classification Product: שעונים
[2025-09-14 08:15:00] [DEBUG] Classification Category: שעונים
[2025-09-14 08:15:00] [DEBUG] Classification Brand: 
[2025-09-14 08:15:00] [DEBUG] Classification Features: 
[2025-09-14 08:15:00] [DEBUG] Classification Gender: 
[2025-09-14 08:15:00] [DEBUG] Classification Filters: 
[2025-09-14 08:15:00] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c4d0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11947 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:15:00] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c4d0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11947 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:15:00] [DEBUG] Searching for: 'שעונים'
[2025-09-14 08:15:00] [INFO] Using WordPress built-in function for production mode
[2025-09-14 08:15:00] [INFO] WordPress wc_get_products found 10 products for: 'שעונים'
[2025-09-14 08:15:00] [INFO] Normalizing products.
[2025-09-14 08:15:00] [INFO] Found 10 products using strategy: Original Product Search
[2025-09-14 08:15:00] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%a9%d7%a2%d7%95%d7%a0%d7%99-%d7%a7%d7%a8%d7%98%d7%99%d7%99%d7%94-2/">שעון קרטייה</a>
<b>שעונים קרטייה </b>
&nbsp;
&nbsp;

2. <a href="https://dealimzoharim.com/product/%d7%a9%d7%a2%d7%95%d7%a0%d7%99%d7%9d-%d7%a7%d7%a8%d7%98%d7%99%d7%99%d7%94-6/">שעונים קרטייה</a>

3. <a href="https://dealimzoharim.com/product/%d7%a9%d7%a2%d7%95%d7%a0%d7%99%d7%9d-%d7%91%d7%95%d7%9c%d7%92%d7%a8%d7%99/">שעונים בולגרי</a>

4. <a href="https://dealimzoharim.com/product/%d7%a9%d7%a2%d7%95%d7%a0%d7%99%d7%9d-%d7%a7%d7%a8%d7%98%d7%99%d7%99%d7%94-5/">שעונים קרטייה</a>


[2025-09-14 08:15:00] [INFO] Starting image stitching process with 4 images
[2025-09-14 08:15:00] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/06/a684384a-e1717779035221.jpg
[2025-09-14 08:15:00] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/2682025-שעוני-קרטייר2025_08_26-16-24-03_1_32025_08_26-16-24-03-1152x1536-1.jpg
[2025-09-14 08:15:00] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/7fc9cf72.jpeg
[2025-09-14 08:15:00] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/5064439e.jpg
[2025-09-14 08:15:00] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_3629a5970a63261932339ffda8c53be8.jpg
[2025-09-14 08:15:00] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_3629a5970a63261932339ffda8c53be8.jpg
[2025-09-14 08:15:00] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_3629a5970a63261932339ffda8c53be8.jpg
[2025-09-14 08:15:00] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 08:15:00] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c4d0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1131819
content-type: multipart/form-data; boundary=------------------------30337ba69a1e7d3e

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:15:00] [ERROR] Telegram API error for sendPhoto: Bad Request
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f4c4d0)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1131819
content-type: multipart/form-data; boundary=------------------------30337ba69a1e7d3e

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
* HTTP error before end of send, stop sending
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:15:00] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request"}
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5d840)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1378
content-type: application/json; boundary=------------------------9489957165e227b6

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 08:15:00] [ERROR] Telegram API error for sendMessage: Bad Request
[2025-09-14 08:15:00] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f5d840)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1378
content-type: application/json; boundary=------------------------9489957165e227b6

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 08:15:00 GMT
< content-type: application/octet-stream
< content-length: 57
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:19] [INFO] 

Webhook processing started
[2025-09-14 09:15:37] [INFO] 

Webhook processing started
[2025-09-14 09:15:37] [INFO] Group message from ד in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי מכנסים של פולו
[2025-09-14 09:15:39] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "פולו מכנסיים",
    "category": "מכנסיים",
    "brand": "פולו",
    "model": "",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-14 09:15:39] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-14 09:15:39] [INFO] Using WordPress built-in function for production mode
[2025-09-14 09:15:39] [INFO] Loading WordPress
[2025-09-14 09:15:39] [INFO] Loaded wp-load.php
[2025-09-14 09:15:39] [INFO] WordPress loaded
[2025-09-14 09:15:39] [INFO] WordPress wc_get_products found 5 products for: 'פולו מכנסיים'
[2025-09-14 09:15:39] [INFO] Normalizing products.
[2025-09-14 09:15:39] [DEBUG] Classification Product: פולו מכנסיים
[2025-09-14 09:15:39] [DEBUG] Classification Category: מכנסיים
[2025-09-14 09:15:39] [DEBUG] Classification Brand: פולו
[2025-09-14 09:15:39] [DEBUG] Classification Features: 
[2025-09-14 09:15:39] [DEBUG] Classification Gender: 
[2025-09-14 09:15:39] [DEBUG] Classification Filters: 
[2025-09-14 09:15:42] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
[2025-09-14 09:15:42] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c1e9c0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11949 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:42 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:42] [ERROR] Telegram API error for sendMessage: Bad Request: chat not found
[2025-09-14 09:15:42] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x7f5800c1e9c0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11949 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:42 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:42] [DEBUG] Searching for: 'פולו מכנסיים'
[2025-09-14 09:15:42] [INFO] Using WordPress built-in function for production mode
[2025-09-14 09:15:42] [INFO] WordPress wc_get_products found 5 products for: 'פולו מכנסיים'
[2025-09-14 09:15:42] [INFO] Normalizing products.
[2025-09-14 09:15:42] [INFO] Found 5 products using strategy: Original Product Search
[2025-09-14 09:15:42] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9e%d7%9b%d7%a0%d7%a1%d7%99%d7%99%d7%9d-%d7%90%d7%a8%d7%95%d7%9b%d7%99%d7%9d-%d7%93%d7%a7%d7%99%d7%9d-%d7%a4%d7%95%d7%9c%d7%95-2/">מכנסיים ארוכים דקים פולו</a>
מכנסיים ארוכים דקים פולו
מידות S-XL

2. <a href="https://dealimzoharim.com/product/%d7%9e%d7%9b%d7%a0%d7%a1%d7%99%d7%99%d7%9d-%d7%90%d7%a8%d7%95%d7%9b%d7%99%d7%9d-%d7%93%d7%a7%d7%99%d7%9d-%d7%a4%d7%95%d7%9c%d7%95/">מכנסיים ארוכים דקים ראלף לורן</a>
מכנסיים ארוכים דקים פולו
מידות S-L

3. <a href="https://dealimzoharim.com/product/%d7%9e%d7%9b%d7%a0%d7%a1%d7%99%d7%99%d7%9d-%d7%a7%d7%a6%d7%a8%d7%99%d7%9d-%d7%a4%d7%95%d7%9c%d7%95-3/">מכנסיים קצרים ראלף לורן</a>
מכנסיים קצרים פולו ראלף לורן
מידות M-2XL

4. <a href="https://dealimzoharim.com/product/%d7%9e%d7%9b%d7%a0%d7%a1%d7%99%d7%99%d7%9d-%d7%92%d7%a0%d7%a1-%d7%a7%d7%a6%d7%a8-%d7%a4%d7%95%d7%9c%d7%95/">מכנסיים ג'נס קצר פולו</a>
מכנסיים ג'נס קצר פולו
מידות XS-XL


[2025-09-14 09:15:42] [INFO] Starting image stitching process with 4 images
[2025-09-14 09:15:42] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/09/fe8f2f1d-600x600-1.jpg
[2025-09-14 09:15:42] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/06/827334cd.jpg
[2025-09-14 09:15:42] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2023/07/87f7e80d.jpg
[2025-09-14 09:15:42] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/04/c02b483d-scaled.jpg
[2025-09-14 09:15:42] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-14 09:15:42] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2024/09/fe8f2f1d-600x600-1.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2024/09/fe8f2f1d-600x600-1.jpg
[2025-09-14 09:15:42] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-14 09:15:42] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2024/06/827334cd.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2024/06/827334cd.jpg
[2025-09-14 09:15:42] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-14 09:15:42] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2023/07/87f7e80d.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2023/07/87f7e80d.jpg
[2025-09-14 09:15:42] [DEBUG] Using WordPress root from config: /var/www/bzb32lvsoh.tempsite.io/htdocs
[2025-09-14 09:15:42] [DEBUG] Converted URL to local path: https://dealimzoharim.com/wp-content/uploads/2025/04/c02b483d-scaled.jpg -> /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/uploads/2025/04/c02b483d-scaled.jpg
[2025-09-14 09:15:43] [INFO] Stitched image saved to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_f1b63c69c184154a9b4c632ba8fa4329.jpg
[2025-09-14 09:15:43] [INFO] Successfully stitched images to: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_f1b63c69c184154a9b4c632ba8fa4329.jpg
[2025-09-14 09:15:43] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_f1b63c69c184154a9b4c632ba8fa4329.jpg
[2025-09-14 09:15:43] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_f1b63c69c184154a9b4c632ba8fa4329.jpg
[2025-09-14 09:15:43] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 09:15:44] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
[2025-09-14 09:15:44] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f83300)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 3300302
content-type: multipart/form-data; boundary=------------------------7b5d1998ca148391

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:44 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:44] [ERROR] Telegram API error for sendPhoto: Bad Request: chat not found
[2025-09-14 09:15:44] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f83300)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 3300302
content-type: multipart/form-data; boundary=------------------------7b5d1998ca148391

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:44 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:44] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request: message text is empty"}
[2025-09-14 09:15:44] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f83300)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1992
content-type: application/json; boundary=------------------------ac871a5158be4d9a

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:44 GMT
< content-type: application/json
< content-length: 80
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:15:44] [ERROR] Telegram API error for sendMessage: Bad Request: message text is empty
[2025-09-14 09:15:44] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f83300)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1992
content-type: application/json; boundary=------------------------ac871a5158be4d9a

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:15:44 GMT
< content-type: application/json
< content-length: 80
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:20:08] [INFO] 

Webhook processing started
[2025-09-14 09:22:00] [INFO] 

Webhook processing started
[2025-09-14 09:22:00] [INFO] Group message from el m in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): תמצאי לי כפכפי  נייק ויקטורי
[2025-09-14 09:22:01] [DEBUG] Raw AI classification response: '{
    "intent": "ProductRequest",
    "product": "נייק ויקטורי",
    "category": "כפכפים",
    "brand": "נייק",
    "model": "ויקטורי",
    "features": "",
    "gender": "",
    "filters": ""
}'
[2025-09-14 09:22:01] [DEBUG] Handling ProductRequest message - ProductRequest
[2025-09-14 09:22:01] [INFO] Using WordPress built-in function for production mode
[2025-09-14 09:22:01] [INFO] Loading WordPress
[2025-09-14 09:22:02] [INFO] Loaded wp-load.php
[2025-09-14 09:22:02] [INFO] WordPress loaded
[2025-09-14 09:22:02] [INFO] WordPress wc_get_products found 0 products for: 'נייק ויקטורי'
[2025-09-14 09:22:02] [INFO] Normalizing products.
[2025-09-14 09:22:02] [DEBUG] Classification Product: נייק ויקטורי
[2025-09-14 09:22:02] [DEBUG] Classification Category: כפכפים
[2025-09-14 09:22:02] [DEBUG] Classification Brand: נייק
[2025-09-14 09:22:02] [DEBUG] Classification Features: 
[2025-09-14 09:22:02] [DEBUG] Classification Gender: 
[2025-09-14 09:22:02] [DEBUG] Classification Filters: 
[2025-09-14 09:22:02] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f56330)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11951 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:22:02] [ERROR] Telegram API error for sendMessage: Bad Request: chat not found
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f56330)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage?chat_id=-1002637696817&text=%E2%9C%A8+%D7%A8%D7%92%D7%A2%2C+%D7%9E%D7%91%D7%A6%D7%A2%D7%AA+%D7%97%D7%99%D7%A4%D7%95%D7%A9+%D7%91%D7%9E%D7%99%D7%95%D7%97%D7%93+%D7%91%D7%A9%D7%91%D7%99%D7%9C%D7%9A%E2%80%A6&parse_mode=HTML&reply_to_message_id=11951 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:22:02] [DEBUG] Searching for: 'נייק ויקטורי'
[2025-09-14 09:22:02] [INFO] Using WordPress built-in function for production mode
[2025-09-14 09:22:02] [INFO] WordPress wc_get_products found 0 products for: 'נייק ויקטורי'
[2025-09-14 09:22:02] [INFO] Normalizing products.
[2025-09-14 09:22:02] [DEBUG] No results found using strategy: Original Product Search
[2025-09-14 09:22:02] [DEBUG] Searching by category: 'כפכפים' brand: 'נייק' and gender ''
[2025-09-14 09:22:02] [INFO] Using WordPress built-in function for production mode
[2025-09-14 09:22:02] [INFO] WordPress wc_get_products found 10 products for: 'כפכפים נייק'
[2025-09-14 09:22:02] [INFO] Normalizing products.
[2025-09-14 09:22:02] [INFO] Found 10 products using strategy: Category + Brand Search
[2025-09-14 09:22:02] [DEBUG] STS - caption: 📋 <b>המוצרים שאליס מצאה עבורך:</b>

1. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%a0%d7%99%d7%99%d7%a7-tn/">כפכפים נייק TN</a>
מידות 40-45

2. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%a0%d7%99%d7%99%d7%a7-calm-slide/">כפכפים נייק CALM SLIDE</a>
<b>כפכפים נייק CALM SLIDE קולקציה חדשה</b>
מידות 36-44

3. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%a0%d7%99%d7%99%d7%a7-25/">כפכפים נייק</a>
<b>כפכפים נייק קולקציה חדשה</b>
מידות 36-45

4. <a href="https://dealimzoharim.com/product/%d7%9b%d7%a4%d7%9b%d7%a4%d7%99%d7%9d-%d7%a0%d7%99%d7%99%d7%a7-5/">כפכפים נייק</a>
<b>כפכפי נייק</b>
מידות : 36-45


[2025-09-14 09:22:02] [INFO] Starting image stitching process with 4 images
[2025-09-14 09:22:02] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/08/102cfc48.jpg
[2025-09-14 09:22:02] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/05/0bbf08f7.jpg
[2025-09-14 09:22:02] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2025/03/0fe8ae17.jpg
[2025-09-14 09:22:02] [DEBUG] Image URL validation passed: https://dealimzoharim.com/wp-content/uploads/2024/03/854a228b.jpg
[2025-09-14 09:22:02] [INFO] Using cached stitched image: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_0c1832f63d2bd0da1f3a2055a85e750e.jpg
[2025-09-14 09:22:02] [DEBUG] STS - imagePath: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_0c1832f63d2bd0da1f3a2055a85e750e.jpg
[2025-09-14 09:22:02] [DEBUG] Found CURLFile: /var/www/bzb32lvsoh.tempsite.io/htdocs/wp-content/themes/dianazohar2019/AliceBot/src/Services/../../images/stitched_0c1832f63d2bd0da1f3a2055a85e750e.jpg
[2025-09-14 09:22:02] [DEBUG] Uploading files with multipart/form-data
[2025-09-14 09:22:02] [ERROR] HTTP 400 response from sendPhoto: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66230)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 867271
content-type: multipart/form-data; boundary=------------------------7f73fd2ab8ac3ffa

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:22:02] [ERROR] Telegram API error for sendPhoto: Bad Request: chat not found
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66230)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendPhoto HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 867271
content-type: multipart/form-data; boundary=------------------------7f73fd2ab8ac3ffa

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:22:02] [ERROR] HTTP 400 response from sendMessage: {"ok":false,"error_code":400,"description":"Bad Request: message text is empty"}
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66230)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1660
content-type: application/json; boundary=------------------------65cb6a07f1e2bf80

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 80
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 09:22:02] [ERROR] Telegram API error for sendMessage: Bad Request: message text is empty
[2025-09-14 09:22:02] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07f66230)
> POST /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/sendMessage HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*
content-length: 1660
content-type: application/json; boundary=------------------------65cb6a07f1e2bf80

* We are completely uploaded and fine
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 09:22:02 GMT
< content-type: application/json
< content-length: 80
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 10:38:30] [INFO] 

Webhook processing started
[2025-09-14 10:38:53] [INFO] 

Webhook processing started
[2025-09-14 10:38:53] [INFO] Group message from Noa Kalimian in 'אליס העוזרת האישית של דילים זוהרים' (-1002637696817): אליס תמצאי לי את התיק הזה פליז
[2025-09-14 10:38:54] [DEBUG] Raw AI classification response: '{
    "intent": "Inappropriate"
}'
[2025-09-14 10:38:54] [ERROR] HTTP 400 response from deleteMessage: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
[2025-09-14 10:38:54] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c9eff0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/deleteMessage?chat_id=-1002637696817&message_id=11953 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 10:38:54 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 10:38:54] [ERROR] Telegram API error for deleteMessage: Bad Request: chat not found
[2025-09-14 10:38:54] [DEBUG] Verbose cURL log:
*   Trying 149.154.167.220:443...
* TCP_NODELAY set
* Connected to api.telegram.org (149.154.167.220) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.telegram.org
*  start date: Mar 25 13:09:41 2025 GMT
*  expire date: Apr 26 13:09:41 2026 GMT
*  subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* 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
* Using Stream ID: 1 (easy handle 0x560b07c9eff0)
> GET /bot8332717380:AAGm-_NUpkFKqat0p_Nntd_0bQ8NfOeBPzw/deleteMessage?chat_id=-1002637696817&message_id=11953 HTTP/2
Host: api.telegram.org
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
accept: */*

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 400 
< server: nginx/1.18.0
< date: Sun, 14 Sep 2025 10:38:54 GMT
< content-type: application/json
< content-length: 73
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< access-control-allow-origin: *
< access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection
< 
* Connection #0 to host api.telegram.org left intact

[2025-09-14 10:38:54] [INFO] Message deletion: Deleted message 11953 from chat -1002637696817
[2025-09-14 10:39:08] [INFO] 

Webhook processing started
[2025-09-14 16:55:33] [INFO] 

Webhook processing started
[2025-11-16 23:11:24] [INFO] 

Webhook processing started
[2026-01-14 15:33:17] [INFO] 

Webhook processing started
[2026-01-14 22:00:05] [INFO] 

Webhook processing started
[2026-01-20 12:15:09] [INFO] 

Webhook processing started
[2026-02-24 07:41:50] [INFO] 

Webhook processing started
[2026-03-18 05:30:18] [INFO] 

Webhook processing started
[2026-05-16 18:33:15] [INFO] 

Webhook processing started
[2026-05-16 18:34:20] [INFO] 

Webhook processing started
[2026-05-16 18:51:34] [INFO] 

Webhook processing started
[2026-05-16 21:34:49] [INFO] 

Webhook processing started