System Log Errors : send() failed (40: Message too long) !!
-
Dears,
Could you please provide a proper solution for below errors which is found in the log file?
Dec 4 20:28:42 nginx 2021/12/04 20:28:42 [alert] 86917#100411: send() failed (40: Message too long)
Dec 4 20:28:42 nginx 2021/12/04 20:28:42 [alert] 86941#100394: send() failed (40: Message too long)
Dec 4 20:28:42 nginx 2021/12/04 20:28:42 [alert] 86941#100394: send() failed (40: Message too long)
Dec 4 20:28:43 nginx 2021/12/04 20:28:43 [alert] 86941#100394: send() failed (40: Message too long) -
Are you seeing that error repeatedly?
What pfSense version are you running?
Are you using the captive portal? With a custom login page?
Check the nginx error logs in /var/log.
Steve
-
Yes .. repeating the same ..
we do have captive portal also -
@stephenw10 said in System Log Errors : send() failed (40: Message too long) !!:
What pfSense version are you running?
With a custom login page?
Check the nginx error logs in /var/log.
Steve
-
2.5.2-RELEASE (amd64) -
@sparktcs said in System Log Errors : send() failed (40: Message too long) !!:
we do have captive portal also
Do you use the default, build 'pfSense' portal login page ?
Or do you use your own portal page ?Also :
Does this happens with every portal client using every possible device ?
Or just some client using some type of device ?Are you using the SSL portal login (https) ? Or IP based (http) ?
Does it happen with user launched browsers ?
Are they accessing the portal's login page directly ?Normally, portal users don't need to know that a captive portal is used.
The connect to your, typically a Wifi, network, and as soon as the link comes up, DHCP does it's thing, the OS of the device will handle the portal's login page as it is auto detected, the user will get redirects to the captive portal's login page, the user logs itself in, and the request is repeated using the initial URL. Most if not all is done without portal user interaction. -
@stephenw10 said in System Log Errors : send() failed (40: Message too long) !!:
With a custom login page?
Exactly. Previous reports of this were caused by a bad custom port page that was creating a forward incorrectly.
Steve
