Forum
Notifications
Clear all
Topic starter
02/02/2025 5:02 pm
Hello,
I am trying to move from zevnet to skudonet CE.
using postman to check compatibility on new skudonet.
using same postman request i get Connection reset by peer (0.001 secs) from backend nginx.
The working query request on zevnet:
################################################################################################################################
T 2025/02/02 17:46:50.283409 yyyyy.70:45948 -> xxxxx.63:488 [AP]
GET /shop/v2/help/ANDROID/HE/he/il HTTP/1.1.
Host: num2-reg.sms.hn.
X-Forwarded-For-Source: zzzzz.190.
User-Agent: PostmanRuntime/7.43.0.
Accept: */*.
Cache-Control: no-cache.
Postman-Token: 63e8b858-199a-486a-a05b-9a6ce826a164.
Accept-Encoding: gzip, deflate, br.
X-Forwarded-For: yyyyy.70.
.
##
T 2025/02/02 17:46:50.284111 xxxxx.63:488 ->yyyyy.70:45948 [AP]
HTTP/1.1 302 Moved Temporarily.
Server: nginx.
Date: Sun, 02 Feb 2025 15:46:50 GMT.
Content-Type: text/html.
Content-Length: 154.
Connection: keep-alive.
Location: https://xxxxxx/shop/v2/assets/Num2Packages2_he.html.
The bad request from skudonet:
####
T 2025/02/02 17:42:16.574127 yyyyy.80:55542 -> xxxxx.63:488 [AP] #4
GET /shop/v2/help/ANDROID/HE/he/il HTTP/1.1.
Host: num2-reg.sms.hn.
X-Forwarded-For-Source: zzzzz.10.
User-Agent: PostmanRuntime/7.43.0.
Accept: */*.
Cache-Control: no-cache.
Postman-Token: 2e28eac8-10b7-424a-a821-b4bc39ade619.
Accept-Encoding: gzip, deflate, br.
X-Forwarded-For: yyyyy.80.
.
#
T 2025/02/02 17:42:16.574444 xxxxx.63:488 -> yyyyy.80:55542 [AR] #5
......
Regards,
Yohai
03/02/2025 8:31 am
Hi Yohai, this request is not complete as I would require to see the full postman request and the response of SKUDONET to the backend, so some information is missing related to the logs, can you share with us what is saved in /var/log/syslog when peer resets the connection? Also, are you sending the request to the backend server in HTTP or HTTPS, if the connection is sent in HTTPS please check that your backend server is running with the OpenSSL library updated. SKUDONET v10 uses the latest OpenSSL library where some SSL protocols are marked as not used (deprecated) for security reasons.
Regards!
Topic starter
03/02/2025 8:59 am
Hello Emilio,
The request is HTTP.
telnet between nodes is working fine.
This is what i see in syslog:
2025-02-02T17:42:16.575634+02:00 LB-SKDCE7-1 pound: web-num2-reg, service num2-reg-sms-hn-shop, backend xxxxx:488, (7f31c11ff6c0) e500 for yyyyy.80 response error read from xxxxx:488/GET /shop/v2/help/ANDROID/HE/he/il HTTP/1.1: Connection reset by peer (0.001 secs)
Postman log:
GET /shop/v2/help/ANDROID/HE/he/il HTTP/1.1
User-Agent: PostmanRuntime/7.43.0
Accept: */*
Cache-Control: no-cache
Postman-Token: be6b4034-db3f-4302-b1d8-a819b4cf2218
Host: num2-reg.sms.hn:8443
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Mon, 03 Feb 2025 07:53:26 GMT
Content-Type: text/html
Content-Length: 59
Connection: keep-alive
Expires: now
Pragma: no-cache
Cache-control: no-cache,no-store
An internal server error occurred. Please try again later.
03/02/2025 9:30 am
Hi @yohai, a lot of information is missing for us to understand what is going on here.
We don't see any issue in the SKUDONET, as the logs show that the backends closed the connection unexpectedly, what should be understood here is why the backend is doing this action instead of replying properly to the HTTP request.
So please connect to the SSH console of the new SKUDONET CE v7, and run a curl against the affected backend with the proper URL:
curl http://BACKENDHOST/shop/v2/help/ANDROID/HE/he/il
I assume this is the direct URL received by the nginx server, if not please correct it.
and share with us the output.
This post was modified 2 days ago 2 times by emiliocm
Topic starter
03/02/2025 7:31 pm
Hello,
I tested the secondary node by switching the cluster activity.
the second node worked fine. (same backend)
We have reinstalled node 1 and now they both works.
thanks,
Yohai
