Send() failed (40: Message too long)

nutel.pr

Same problem in my pfsense, 2.3.2-RELEASE-p1 (amd64)
built on Tue Sep 27 12:13:07 CDT 2016
FreeBSD 10.3-RELEASE-p9

2016/11/25 15:13:07 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:13:38 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:13:40 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:12 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:27 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:41 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:15:36 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:15:49 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:21:53 [alert] 15623#100082: send() failed (40: Message too long)
2016/11/25 15:23:19 [alert] 15623#100082: send() failed (40: Message too long)

sisko212

Same trouble with my pfsense after upgrade to 2.3.2 pi1, coming from pfsense 2.2.x
I didn't installed any Captive portal.
This issue looks related to the web interface, even if i can't be 100% sure.
I tried to remove all widgets from dashboard, switch from http to https, and taking a look from shell with "tail -f /var/log/nginx-error.log", an alert entry appears a couple times per minutes, instead once per second as before.

Lampogriz

Same problem here, 2.3.4-RELEASE-p1 (amd64)

stbird

2.3.4-RELEASE-p1 (amd64)

captive portal

Any ideas for this problem?

Lampogriz

Upgraded to 2.4.2 , still spams "send() failed (40: Message too long)" in log

SouthPointHotel

@digital_janitor:

I am also getting these since upgrade. Are there any logs that give more info?

Same here. help?

Gertjan

@krashneo:

I changed my form from:

To:

to see the results… I will reply asap

Did you try to change your old redirect URL "http%3A%2F%2F172.16.0.1%2F" == "http://172.16.0.1/"
to "http://www.google.com" instead of changing the source ?

What pfSense version ? - is it patched or modified ?

pama

The same here.
After re-applying the squid settings it stopped to logs the errors, but after 2 or 3 days (depends on load) it reappears

sujyo1

2.4.2-RELEASE-p1 (amd64)
built on Tue Dec 12 13:45:26 CST 2017
FreeBSD 11.1-RELEASE-p6

Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
Current: 2667 MHz, Max: 2668 MHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: No

Interfaces:
WAN 1000baseT <full-duplex>xx.xx.ccc.ccc
LAN autoselect 192.168.1.1
OFFICE 100baseTX <full-duplex>192.168.100.1
HOTSPOT 1000baseT <full-duplex>10.10.10.1 (captive portal is ON)

nginx: 2018/02/10 19:49:01 [error] 28887#100127: *4888 open() "/usr/local/www/phpmyadmin" failed (2: No such file or directory), client: 1x0.2x9.1xx.x6, server: , request: "GET /phpmyadmin HTTP/1.1", host: "xx.3x.2xx.xxx", referrer: "http://xx.xx.xxx.xxx/phpmyadmin"

I getting same a full page…

Feb 10 15:05:55 nginx: 2018/02/10 15:05:55 [alert] 43837#100173: send() failed (40: Message too long)</full-duplex></full-duplex></full-duplex>

AMD_infinium05

Hey guys, is there an update to this issue?

hasanfatih

ishtiaqaj did you solve this problem

A Former User

@Lampogriz

Aug 28 10:22:38	pfsense.localdomain		nginx: 2019/08/28 10:22:38 [alert] 54908#100145: send() failed (40: Message too long)

I experienced this also in latest pfsense right now. my captive portal disconnects .I hope there is a fix for this.

wazim4u

@dyobetem I also have this issue since 2 months and its related to Captive Portal. i have 2500+ captive portal users and 2 WAN. i changed a lot of settings in nginx but useless. still i am getting these errors. I've pfsense 2.4.4-P3 Lastest version.

i have already mentioned this issue in given blow post ( last Issue )

https://forum.netgate.com/topic/144868/dell-r430-bge-built-in-port-hangs-captive-portal-stop-working/23

Gertjan

@wazim4u : Do you redirect a new, just logged-in user to an URL ( setting After authentication Redirection URL ) ?

This is what I think : when a user logged in using the IP (or URL) of the captive portal page, the users browser gets redirected to the same URL (== the captive pprtal's web server).... which will redirect again - to itself -, and again, and again etc - recursif. The URL thrown back to the browser becomes to big, nginx will finally produce the "send() failed (40: Message too long)" error.

For myself, I redirect, no matter what, to "https://www.google.com" but you can take any URL like a your companie's site.

Another explanation : you have quiet a lot of portal users. Not every user uses the latest smart devices /PC's with the latest OS and the best browsers.
Even I see still IE8 (Windows XP) connecting to my portal.
These ancient devices are not portal aware. They won't behave correctly.

Or even : not all the apps are written the same way. At least, Apple reviews (some what) each and every app before it's released - the Android society is a pure zoo. So, a bad app can throw out an URL that's to big. nginx will bail out.

So, mind you, these are all theories.
I do not have the test park to test them.

andresense

This issue has been resolved?

I have this same problem

Gertjan

@andresense

Sure.
No news after more then one year : that means : no issue.

We are also 2 (at least) version of pfSense further on.