@DownPW The reverse proxy is relatively simple. I’m using the below
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://127.0.0.1:8061/;
proxy_redirect off;
# Socket.IO Support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
If you’re not running MemCached or Redis then you can ignore the cache part and just use the NodeJS defaults. I much prefer PM2 as this provides greater flexibility and control (in my view)
Below output from pm2 status
I have install iframely like the doc, no cache app, no reverse proxy with PM2 and I have not modify config file.
Results? it does not work 
something I missing ?
what I don’t understand is how Iframely can interact with NodeBB. There is nothing to configure on the NodeBB side?
I have install Iframely nodebb plugin and setup with my local IP (because it’s a VM on no prod server) like this :
Doesn’t work
@DownPW can you try removing the port and just use the IP address ?
@DownPW said in Iframely (Nodebb):
what I don’t understand is how Iframely can interact with NodeBB. There is nothing to configure on the NodeBB side?
We are using self-hosted iframely… Unfortunately, our developer is currently busy with relocation etc, therefore I cannot ask for more detail…
But we have this as the endpoint address:
http://0.0.0.0:8061/iframely?
So, I guess we installed it as a subfolder at this port location in the same server? Maybe @phenomlab can tell it better 
sorry, I am not good at backend work
@crazycells typically, you do not need the port as that is handled and processed by the NGINX config. I have my instance running in a subdomain for security reasons with CORS headers adjusted to suit.
@DownPW from what I see, iFramely isn’t setup properly on your server as the port of 8061 does not appear to be listening. For example, see below for the response I get when trying to access the port.
Another possibility here (and a strong one in fact) is that you probably need to open this port on your firewall (perhaps iptables) and probably your router also (in terms of NAT).
@DownPW right, but what about iptables on the server itself? The port isn’t responding which is the first hurdle to overcome.
I don’t know because I think you are connected to ssh, so I don’t see this
grrr it’s a debian scratch and iptables is not installed by defaut
@DownPW what happens if you perform the same telnet command from the server itself ? If that responds, then the issue is possibly the NAT translation via the router.
Fire example, if telnet 127.0.0.1 8061 connects, then the port is listening on localhost. If you try the same but with the public IP you have instead, then that’s a NAT issue (potentially)
very odd @phenomlab
I can connect to telnet on server (local host) and externally (with my phone on 4g network = externally network) with public ip
telnet privateIP 8061 is OK on the server
telnet externalPublicIP 8061 is OK with my smartphone on 5G (externally network) with Termux app
The NAT on my router and the server is OK on 8061 port
@DownPW very odd. Ok. I’ll take a look at this tomorrow morning but I do need root access (and password) to this server.
@phenomlab said in Iframely (Nodebb):
@DownPW very odd. Ok. I’ll take a look at this tomorrow morning but I do need root access (and password) to this server.
OK
you already have these information in your PM
@DownPW confirmed. Thanks
@DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.
