Arlen Beiler's questions

When I listen on port 80 with NodeJS v10 all other machines can access the port but the machine itself cannot. This is very strange, and is the same for loopback and the eth0 IP address. However, it can access port 90 on itself just fine as can the other machines on the network.

I've used a simple hello world app to verify that the NodeJS script is not at fault.

This also occurs in NodeJS 12.13.0, so I don't think Node is the problem at all.

iptables -L says everything is empty with policy ACCEPT.

netstat -tulpn lists no port 80 except the one I'm testing with.

I have a Ubuntu 16.04 VM and when I run curl http://192.168.254.42 (the eth0 IP address) it quickly replies with connection refused. However, the server is definitely listening on 0.0.0.0 and can be accessed by other computers on the network using that same address in the browser. curl http://192.168.254.1 returns the html of my router admin page.

Of course this wouldn't normally be a blocker, but this also means that VPN clients connected to the server cannot access the server itself using the eth0 IP address (which clients on the network use). I've never run into this problem before, and Google brings up the obvious "listening on localhost", which isn't the case here.

I can ping the eth0 ip address from the terminal (i.e. ping itself) and it responds properly. A traceroute from a VPN client also looks correct. But accessing the http://192.168.254.42 immediately responds with connection refused.

Here is netstat -tulpn output.

$ netstat -tulpn | grep :80
tcp6       0      0 :::80                   :::*                    LISTEN      5724/index-lib
$ netstat -tulpn | grep :85
tcp6       0      0 :::85                   :::*                    LISTEN      1212/server.js
$ netstat -tulpn | grep :81
tcp6       0      0 :::81                   :::*                    LISTEN      1515/apache2

Setting it to Port 86 works. And another NodeJS server is running on port 85 as well and can be accessed just fine. So it's not a problem with the NodeJS side of things.

Old info

The webserver is a single NodeJS v10.16.3 HTTP server instance listening on 0.0.0.0.

Listening on 192.168.254.42 does not work either.

More importantly, an Apache webservice listening on port 81 can be accessed just fine.

Chrome says ERR_CONNECTION_FAILED, but it does it almost instantly.

No iptables rules are set.

A NodeJS process is listening on Port 85 and can be accessed in the same manner.

Here is netstat -tulpn output.

$ netstat -tulpn | grep :80
tcp6       0      0 :::80                   :::*                    LISTEN      5724/index-lib
$ netstat -tulpn | grep :85
tcp6       0      0 :::85                   :::*                    LISTEN      1212/server.js
$ netstat -tulpn | grep :81
tcp6       0      0 :::81                   :::*                    LISTEN      1515/apache2

The command I am using to check this is

$ curl http://192.168.254.42
curl: (7) Failed to connect to 192.168.254.42 port 80: Connection refused

Port 81 and 85 return expected HTML.

Setting it to listen on port 86 makes it accessible! So it's not on the NodeJS side, I don't think.

I was looking through my Nginx (port 80) access log on a server which I do not use much, and I found a lot of lines that have an entire URL in the get statement. What is that supposed to accomplish? Most return a 404, but one of them (not the one below) was a 200, and had several Hexadecimal codes in the request right after it. What is going on?

#.#.#.# - - [28/Sep/2016:18:01:31 +0000] "GET http://www.baidu.com/cache/global/img/gs.gif HTTP/1.1" 404 169 "-" "Mozilla"

I am trying to setup a MySQL server and when I went to create a second user it wouldn't give it permissions for the database. I can connect fine as long as I don't specify a database.

Access denied for user 'user'@'localhost' to database 'diddata'

The connection details are:

{ 'host' : 'localhost', 'user' : 'user', 'password' : 'password' , 'database': 'diddata' };

And to create the DB and table I did:

CREATE DATABASE IF NOT exists diddata;
CREATE USER 'user'@'localhost' IDENTIFIED BY 'password';
GRANT ALL ON user.* TO 'user'@'localhost';

Note that I've changed the username and password in this question.

I've already checked the privileges in MySQL workbench and they are there.