That makes no sense 🤔 The search plugin has nothing to do with themes or skins. Do you have any errors in your logs after you disable the plugin and restart the forum? What about when you run ./nodebb build and restart is everything working after that?
NodeBB running fine port not listening
-
Hey Guys,
Merry Christmas and such. Doubt I'll see a response today which I guess I can understand
Saw this last night and just had to try it out asap so I launched an EC2, got node and redis installed.. Nodebb launches just fine, however it won't listen on any port:
node app
info: NodeBB v0.1.1 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
info: Initializing NodeBB v0.1.1, on port 4567, using Redis store at 127.0.0.1:6379.
info: NodeBB instance bound to: Any address (0.0.0.0)
info: NodeBB Ready
netstat --listen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:6379 : LISTEN
tcp 0 0 *:ssh : LISTEN
tcp 0 0 *:tram : LISTEN
tcp 0 0 localhost:smtp : LISTEN
tcp 0 0 *:10843 : LISTEN
tcp 0 0 *:ssh : LISTEN
udp 0 0 *:bootpc :
udp 0 0 ip-10-238-207-25.ec2.int:ntp :
udp 0 0 localhost:ntp :
udp 0 0 *:ntp :
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 6536 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 5539 @/com/ubuntu/upstart
unix 2 [ ACC ] SEQPACKET LISTENING 5613 @/org/kernel/udev/udevd
The only thing I notice is that while NodeBB is running it does open the two ports 10843 and the *:tram, but when I kill it - those two don't exist there anymore.
I'll update this if I figure it out. Thanks!
