have problem with install on vm

PitaJ

@dark-shy as for the startup logs, you have a few plugins that aren't compatible with your version of NodeBB. Try disabling them for now

Dark Shy

@pitaj disable CloudFlare-it will not work, since I have all the dns running through it. In it, I have all the settings for this domain.

@gotwf said in have problem with install on vm:

2021-03-06T11:24:03.929Z [4567/1511] - error: Error: Cannot find module './categories'

............

2021-03-06T11:24:03.936Z [4567/1511] - error: Error: Cannot find module './user'

i dont know how fix it.

PitaJ

@dark-shy the fix is to update those plugins so they use require.main.require('./src/user') instead of module.parent.require('./user'). But if you aren't the developer of those plugins, there's nothing you can do, so just disable them or ignore the errors for now. They aren't causing the issue.

Since you can access NodeBB on http://localhost:4567, this means NodeBB is running.

Since you can access NodeBB on http://localhost:80, this means that nginx is (at least partially) working.

Since you cannot access NodeBB on http://your.ip:80, this means that there's something blocking requests into your server. It may be a firewall on your server, or it may be something upstream from that. Do you mind sharing more information about your setup?

Dark Shy

@pitaj

@pitaj said in have problem with install on vm:

Since you cannot access NodeBB on http://your.ip:80, this means that there's something blocking requests into your server. It may be a firewall on your server, or it may be something upstream from that. Do you mind sharing more information about your setup?

by external address-works from the external network, and from the internal network does not work at the external address.
from the device 192.168.1.101, it is not possible to connect to 93.95.167.101:80/4567, although it is safe to connect to 192.168.1.103:80/4567. Localhost also works

gotwf

@pitaj said in have problem with install on vm:

@dark-shy the fix is to update those plugins so they use require.main.require('./src/user') instead of
Since you cannot access NodeBB on http://your.ip:80, this means that there's something blocking requests into your server. It may be a firewall on your server, or it may be something upstream from that. Do you mind sharing more information about your setup?

Ah, wait, have we established this? Nginx tail I missed?

Freakin' snap! Eyes missed this bit from the opening post. Sigh...

there is no response - 93.95.167.101.

And I was even looking for it too, earlier when I did those other telnet test. Ho, man!!!

telnet 93.95.167.101 80
Trying 93.95.167.101...
^C

Above confirms that your external IP address is not accessible, at least not by general public. Perchance do you have a firewall rule restricting access to only Cloudflare servers?? If not and all incoming requests to port 80 are blocked then we have just pinpointed the problem because if I nor Cloudflare cannot get there... then the proof is pretty much in the pudding that you have a fw rule issue.

Mind you, you could still additionally have a Cloudflare issue on top of that, but you got to work your way back upstream one link at a time.

Pitaj very efficiently cut to the chase. I was trying to also teach you how to fish. Hope that helps somebody on down the line.

Good luck and have fun. Methinks you are almost there. o/

Dark Shy

@gotwf you cant ping my ip bcs i turn off ICMP traffic.

at now i reboot my vm and at now i see - NGINX again dont working... (WTF?!)
via internet, but in local - working normal

PitaJ

@dark-shy if it's working on http://localhost:80 then it's likely not an nginx problem given your config. You can run lsof -n -i:80 to make sure, you should see nginx there.

Dark Shy

@pitaj said in have problem with install on vm:

if it's working on http://localhost:80 then it's likely not an nginx problem given your config. You can run lsof -n -i:80 to make sure, you should see nginx there.

I was write this command. And take nothing.

server {
    listen       80;
    server_name  forum.slainscraft.com;                                          root   /var/www/html;
    index  index.php index.html index.htm;

    access_log  /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://localhost:4567;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

nhl.pl

Are sure you want it here?
index index.php index.html index.htm;

Again.
root /var/www/html;

You can also try to replace localhost with 127.0.0.1:4567.
proxy_pass http://localhost:4567;

Dark Shy

@pitaj Screenshot_20210307_162706_com.android.chrome.jpg Screenshot_20210307_162714_com.android.chrome.jpg
But at now doesn't work statistics.

PitaJ

@dark-shy You got it coming out, nice!

Do you see any errors in the browser developer console?

Dark Shy

@pitaj nothing

PitaJ

@dark-shy maybe it's just because you don't have any traffic yet. Is any other functionality broken?

gotwf

@nhl-pl said in have problem with install on vm:

You can also try to replace localhost with 127.0.0.1:4567.
proxy_pass http://localhost:4567;

Good catch.

Should work with localhost but I also prefer to be explicit and specify localhost via IP address. Of course those nginx log tails would have pointed us thusly a long ways back. Checking log files for errors and warnings are step one in troubleshooting 101.

Dark Shy

I started looking for a solution to the problem and as one of the solutions, I decided to reinstall, so now it does not work at all on the domain, the situation is as it was, on 93.95.167.101: 4567-it works, on 192.168.1.*: 4567-it works, but with the domain-again some crap.

server {
    listen       80;
    server_name  forum.slainscraft.com;

    access_log  /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://localhost:4567;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Dev-log:
https://pastebin.com/wMUnkgCS

PitaJ

@dark-shy so your-domain.invalid:4567 doesn't work?

Dark Shy

@pitaj yep

PitaJ

@dark-shy if your-ip:4567 works but your-domain:4567 doesn't work, them you have a DNS issue. Your domain isn't correctly pointing to your ip.

Dark Shy

@pitaj my-ip:4567 doenst work from inside network, but work if i connect via another network /_
try: 93.95.167.101:4567

PitaJ

@dark-shy okay so you're going to need to fix the DNS settings for your domain