[GH-ISSUE #135] error: Invalid TCP message #111

Closed
opened 2026-02-26 05:31:21 +03:00 by kerem · 6 comments
Owner

Originally created by @MrAndrewWhite on GitHub (Oct 17, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/135

Hi

Node: v.0.10.31
NPM: 2.1.4
Log.io: 0.3.4

I'm running into issues with log.io. I installed and am able to start the server and harvester but when I connect to log.io it looks like it doesn't understand the headers.

error: Invalid TCP message: GET / HTTP/1.1
error: Invalid TCP message: Host: localhost:28777
error: Invalid TCP message: Connection: keep-alive
error: Invalid TCP message: User-Agent: Mozilla/5.0 (X11; Linux armv6l) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
error: Invalid TCP message: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
error: Invalid TCP message: Accept-Encoding: gzip,deflate,sdch
error: Invalid TCP message: Accept-Language: en-US,en;q=0.8
error: Invalid TCP message: Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
error: Invalid TCP message:
error: Lost TCP connection...

Have you seen this issue before?

Originally created by @MrAndrewWhite on GitHub (Oct 17, 2014). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/135 Hi Node: v.0.10.31 NPM: 2.1.4 Log.io: 0.3.4 I'm running into issues with log.io. I installed and am able to start the server and harvester but when I connect to log.io it looks like it doesn't understand the headers. error: Invalid TCP message: GET / HTTP/1.1 error: Invalid TCP message: Host: localhost:28777 error: Invalid TCP message: Connection: keep-alive error: Invalid TCP message: User-Agent: Mozilla/5.0 (X11; Linux armv6l) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 error: Invalid TCP message: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,_/_;q=0.8 error: Invalid TCP message: Accept-Encoding: gzip,deflate,sdch error: Invalid TCP message: Accept-Language: en-US,en;q=0.8 error: Invalid TCP message: Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 error: Invalid TCP message: error: Lost TCP connection... Have you seen this issue before?
kerem closed this issue 2026-02-26 05:31:21 +03:00
Author
Owner

@MetalsDude commented on GitHub (Nov 8, 2014):

Did you ever figure out why this happens?
I also have the same exact problem.

I am using nginx.

error: Invalid TCP message: GET / HTTP/1.1
error: Invalid TCP message: X-Real-IP: xxxxxxxxx
error: Invalid TCP message: X-Forwarded-For: xxxxxxxxx
error: Invalid TCP message: Host: logsite.testing.net
error: Invalid TCP message: X-NginX-Proxy: true
error: Invalid TCP message: Connection: upgrade
error: Invalid TCP message: User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
error: Invalid TCP message: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
error: Invalid TCP message: Accept-Language: en-US,en;q=0.5
error: Invalid TCP message: Accept-Encoding: gzip, deflate
error: Invalid TCP message: DNT: 1
error: Invalid TCP message:
error: Lost TCP connection...

<!-- gh-comment-id:62248862 --> @MetalsDude commented on GitHub (Nov 8, 2014): Did you ever figure out why this happens? I also have the same exact problem. I am using nginx. error: Invalid TCP message: GET / HTTP/1.1 error: Invalid TCP message: X-Real-IP: xxxxxxxxx error: Invalid TCP message: X-Forwarded-For: xxxxxxxxx error: Invalid TCP message: Host: logsite.testing.net error: Invalid TCP message: X-NginX-Proxy: true error: Invalid TCP message: Connection: upgrade error: Invalid TCP message: User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 error: Invalid TCP message: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,_/_;q=0.8 error: Invalid TCP message: Accept-Language: en-US,en;q=0.5 error: Invalid TCP message: Accept-Encoding: gzip, deflate error: Invalid TCP message: DNT: 1 error: Invalid TCP message: error: Lost TCP connection...
Author
Owner

@gauravarora commented on GitHub (Dec 4, 2014):

I have the same problem, is there a workaround?

<!-- gh-comment-id:65620679 --> @gauravarora commented on GitHub (Dec 4, 2014): I have the same problem, is there a workaround?
Author
Owner

@dimon222 commented on GitHub (Dec 23, 2014):

You're calling wrong web port from browser.
Use 28778 instead of 28777 (28777 is backend)

You can change web UI port in ~/.log.io/web_server.conf

<!-- gh-comment-id:67966045 --> @dimon222 commented on GitHub (Dec 23, 2014): You're calling wrong web port from browser. Use 28778 instead of 28777 (28777 is backend) You can change web UI port in ~/.log.io/web_server.conf
Author
Owner

@MetalsDude commented on GitHub (Dec 24, 2014):

No, this isn't a port issue.
Tried different ones, doesn't make a difference.

<!-- gh-comment-id:68019216 --> @MetalsDude commented on GitHub (Dec 24, 2014): No, this isn't a port issue. Tried different ones, doesn't make a difference.
Author
Owner

@dimon222 commented on GitHub (Dec 24, 2014):

error: Invalid TCP message: Host: localhost:28777

Well, this guy called wrong one. :(

Prolly share your web_server.conf, harvester.conf and what are you opening in browser for further check. Try to open it without nginx. It may be related to wrong configuration of nginx.

<!-- gh-comment-id:68063127 --> @dimon222 commented on GitHub (Dec 24, 2014): > error: Invalid TCP message: Host: localhost:28777 Well, this guy called wrong one. :( Prolly share your web_server.conf, harvester.conf and what are you opening in browser for further check. Try to open it without nginx. It may be related to wrong configuration of nginx.
Author
Owner

@msmathers commented on GitHub (Jan 16, 2020):

Yeah as @dimon222 pointed it it looks like the TCP server is receiving HTTP requests. The server listens on two separate ports, one for TCP connections and the other for HTTP requests. Either your harvester & server conf aren't aligned, or there's a proxy layer between the two that is misrouting traffic.

Also try upgrading to v0.4x, the entire harvester/server stack has been rewritten.

<!-- gh-comment-id:575212680 --> @msmathers commented on GitHub (Jan 16, 2020): Yeah as @dimon222 pointed it it looks like the TCP server is receiving HTTP requests. The server listens on two separate ports, one for TCP connections and the other for HTTP requests. Either your harvester & server conf aren't aligned, or there's a proxy layer between the two that is misrouting traffic. Also try upgrading to v0.4x, the entire harvester/server stack has been rewritten.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/log.io-NarrativeScience-old#111
No description provided.