Node.js TW not responding to HTTP requests in AWS EC2

45 views
Skip to first unread message

Andrés Pérez

unread,
Oct 4, 2018, 5:48:04 AM10/4/18
to TiddlyWiki
I stood up an EC2 instance with port 8080 open. I verified it by dropping an index.html in home and serving it with python simplehttp. I then did an --init server in home using the node version of TW, followed by --server. If I curl http://localhost:8080 I get back the new TW, but I get a connection refused if I try it using either the internal or public IPs. Anybody experience this?

Andrés Pérez

unread,
Oct 4, 2018, 10:21:00 AM10/4/18
to TiddlyWiki
So a netstat -an shows that the server is only listening for traffic on localhost
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN

instead of world

tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN

I am using nginx to reverse proxy the traffic.

Arlen Beiler

unread,
Oct 4, 2018, 11:13:59 AM10/4/18
to TiddlyWiki
That was my first suspicion. I believe you can specify which IP address to use in the command line.

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/808dc996-c09f-492f-80ed-5431dcb81452%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Andrés Pérez

unread,
Oct 4, 2018, 2:55:17 PM10/4/18
to TiddlyWiki
ah! I see that now. gonna keep the proxy for ssl, but good to know. Thank you!!
Reply all
Reply to author
Forward
Message has been deleted
0 new messages