Can't open Nodebb with URL from config.json
-
Ok, what else should I check or setup to see NodeBB opened with http://forum.example.com in the browser? I can post any info to get help to solve this issue
-
@Evg-R said in Can't open Nodebb with URL from config.json:
Ok, what else should I check or setup to see NodeBB opened with http://forum.example.com in the browser? I can post any info to get help to solve this issue
We're still trying to check the basics. Test http://yourip:4567/ and see if it is working correctly.
-
@scottalanmiller under "yourip" you mean IP address of the my linux ubuntu vm? It's dynamic ip, NAT shared from my laptop. I can not open NobeBB with http://myip:4567/ also
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@scottalanmiller under "yourip" you mean IP address of the my linux ubuntu vm? It's dynamic ip, NAT shared from my laptop. I can not open NobeBB with http://myip:4567/ also
It has to be accessible from somewhere, or the Nginx can't reach it, either.
-
But we know it is reachable from somewhere, because you got an error from it. So use its IP from wherever that was.
-
@scottalanmiller And how to make it accessible for Nginx?
-
@scottalanmiller sorry I tried again and I could open http://myip:4567 but got the same message as for localhost:
Looks like your connection to NodeBB was lost, please wait while we try to reconnect. -
You may not have port forwarding set up at your router so you can access it through the internet.
Do you have another computer on your local network? You may be able to check if you can access it through your LAN.
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@scottalanmiller sorry I tried again and I could open http://myip:4567 but got the same message as for localhost:
Looks like your connection to NodeBB was lost, please wait while we try to reconnect.Ah, that will do it then. That's got to be solid and working before the proxy will work.
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@PitaJ Yes I haven't set up port forwarding for router. Could you specify which ports and ip to specify for forwarding ports?
It's the port you specified... 4567, and your IP address. The one that you just used to access it.
-
@scottalanmiller I have added forwarding port 4567 to router for ubuntu vm 192.168.1.4 TCP+UDP 4567 but I have still the same issues...
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@scottalanmiller I have added forwarding port 4567 to router for ubuntu vm 192.168.1.4 TCP+UDP 4567 but I have still the same issues...
That's not necessary. You were already testing from your LAN. Let's stay focused on testing one thing at a time. We don't want to jump around and get confused. (And now that we know your IP we can be explicit as to what we mean.)
If you add a hosts entry for your 192.168.1.4 to your forum.example.com and you browse to http://forum.example.com:4567/ does the issue clear up?
-
@scottalanmiller Yes, now after adding to hosts and opening http://forum.example.com:4567/ I do not have message about lost connection any more
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@scottalanmiller Yes, now after adding to hosts and opening http://forum.example.com:4567/ I do not have message about lost connection any more
Awesome, okay I know that that was a pain, but it clears some things up.
-
Now we are going to try the same exercise, but with port 80 instead.
The issue returns?
-
@scottalanmiller if I open http://forum.example.com/ It's also clean now but with leaving previous hosts record unchanged
-
@Evg-R said in Can't open Nodebb with URL from config.json:
@scottalanmiller if I open http://forum.example.com/ It's also clean now but with leaving previous hosts record unchanged
Yes, that was my intention.
-
Okay, that it is now clean we know that both NodeBB and Nginx should be working fine. Now we can remove the hosts file entry.
-
I hate these 30 second holds on a second response, I write the response then go do something else and forget to submit because I'm always having to wait. I mean to respond quickly, but it doesn't let me get right back to you, hence the delays even though I'm sitting right here.
