Skip to content

How to install a self-hosted instance of iFramely for use with NodeBB

Configure
29 4 15.1k 1
  • wrote on last edited by DownPW
    #8

    Thanks @crazycells for your code, I will test it, for sure 😉

    @phenomlab Resources level, do you know to what extent the CPU will be impacted by Iframely?

    Generally speaking, our forum uses between 20 and 50% of the CPU. With peaks at 80-90 which return an excess load and unavailability to the forum (a few seconds).

  • Thanks @crazycells for your code, I will test it, for sure 😉

    @phenomlab Resources level, do you know to what extent the CPU will be impacted by Iframely?

    Generally speaking, our forum uses between 20 and 50% of the CPU. With peaks at 80-90 which return an excess load and unavailability to the forum (a few seconds).

    wrote on last edited by
    #9

    @DownPW iFramely is multi threaded and runs as a cluster, so will spread itself across the amount of cores you have. If you run pm2 status you’ll see how many cores it’s using, plus the memory usage.

    I’ve never had an issue with it and I know that thousands of sites have it installed with no performance degradation. It scales very well and only seems to occupy a small selection of CPU and memory.

  • @DownPW iFramely is multi threaded and runs as a cluster, so will spread itself across the amount of cores you have. If you run pm2 status you’ll see how many cores it’s using, plus the memory usage.

    I’ve never had an issue with it and I know that thousands of sites have it installed with no performance degradation. It scales very well and only seems to occupy a small selection of CPU and memory.

    wrote on last edited by
    #10

    Ok @phenomlab

    Thanks for your answer but with pm2 status command, I see a % of CPU used but not the number of CPU core used…

  • Ok @phenomlab

    Thanks for your answer but with pm2 status command, I see a % of CPU used but not the number of CPU core used…

    wrote on last edited by
    #11

    @DownPW how many cores do you have ?

  • @DownPW how many cores do you have ?

    wrote on last edited by
    #12

    @phenomlab

    What a loser I am lol 😵

    I configured only one core on my VM !!!

  • @phenomlab

    What a loser I am lol 😵

    I configured only one core on my VM !!!

    wrote on last edited by
    #13

    @DownPW OMG 🤦

  • wrote on last edited by DownPW
    #14

    ha ha, i’m tired voila 🙂

    you say this:

    if you are using Cloudflare, this particular port (8061) isn’t routable with the free plan, so something to be aware of

    @phenomlab
    I’m using a free plan from CloudFlare, will this bother me for use Iframely on my server?

  • ha ha, i’m tired voila 🙂

    you say this:

    if you are using Cloudflare, this particular port (8061) isn’t routable with the free plan, so something to be aware of

    @phenomlab
    I’m using a free plan from CloudFlare, will this bother me for use Iframely on my server?

    wrote on last edited by
    #15

    @DownPW only if you choose to not proxy the traffic (grey cloud only, which is just DNS rather than the default orange cloud)

  • ha ha, i’m tired voila 🙂

    you say this:

    if you are using Cloudflare, this particular port (8061) isn’t routable with the free plan, so something to be aware of

    @phenomlab
    I’m using a free plan from CloudFlare, will this bother me for use Iframely on my server?

    wrote on last edited by
    #16

    @DownPW you will win this war 🙂

  • wrote on last edited by DownPW
    #17

    @phenomlab

    A CNAME on Cloudflare is not sufficient ?

    like this :

    16e51b39-776a-43d8-81a8-0b072cb52b6a-image.png

  • @phenomlab

    A CNAME on Cloudflare is not sufficient ?

    like this :

    16e51b39-776a-43d8-81a8-0b072cb52b6a-image.png

    wrote on last edited by phenomlab
    #18

    @DownPW no. It needs to be an A record. CNAME is canonical meaning that traffic sent to it will land up at your main nginx site. The A record will sent headers which nginx can use to route the traffic correctly.

    CNAME records do not have this and will resolve to the underlying host which will cause you problems. Useful for WWW and non-WWW, but that’s about it.

    Essentially, it’s an alias and not a record in it’s own right.

  • @DownPW no. It needs to be an A record. CNAME is canonical meaning that traffic sent to it will land up at your main nginx site. The A record will sent headers which nginx can use to route the traffic correctly.

    CNAME records do not have this and will resolve to the underlying host which will cause you problems. Useful for WWW and non-WWW, but that’s about it.

    Essentially, it’s an alias and not a record in it’s own right.

    wrote on last edited by cagatay
    #19

    @phenomlab i think my ifamely started to not work i dont know why 😞 youtube embed not working 😞

    7b229e08-8c8f-4d9e-be5d-78a4f0bb1b37-image.png

    [PM2][ERROR] Process or Namespace iframely not found
    [PM2][WARN] Current process list is not synchronized with saved list. App iframely iframely differs. Type ‘pm2 save’ to synchronize.

  • wrote on last edited by phenomlab
    #20

    @cagatay is the iframely service started ? That error message would indicate it’s not running

  • @cagatay is the iframely service started ? That error message would indicate it’s not running

    wrote on last edited by
    #21

    @phenomlab as a result of ps -x i cant see iframely service pid id so i think its not working automaticly when i rebooted the server. How can i start it?

  • @phenomlab as a result of ps -x i cant see iframely service pid id so i think its not working automaticly when i rebooted the server. How can i start it?

    wrote on last edited by
    #22

    @cagatay try pm2 start pm2.json which needs to be executed from the directory of the iFramely domain where it is installed. See previous documentation I provided after the installation.

    A quicker route would be to reboot your VPS to see if that resolves the issue.

  • @cagatay try pm2 start pm2.json which needs to be executed from the directory of the iFramely domain where it is installed. See previous documentation I provided after the installation.

    A quicker route would be to reboot your VPS to see if that resolves the issue.

    wrote on last edited by
    #23

    @phenomlab
    d52f9baf-3989-4753-bda4-5065c81504b1-image.png

    hope everything is ok from now.

  • @cagatay try pm2 start pm2.json which needs to be executed from the directory of the iFramely domain where it is installed. See previous documentation I provided after the installation.

    A quicker route would be to reboot your VPS to see if that resolves the issue.

    wrote on last edited by cagatay
    #24

    @phenomlab when i reboot the vps nodebb and iframely not working auto 😞
    but manually everything is working fine right now.

  • @phenomlab when i reboot the vps nodebb and iframely not working auto 😞
    but manually everything is working fine right now.

    wrote on last edited by
    #25

    @cagatay ok, that needs looking at then as it seems it’s not configured properly. For now of course you can start it manually.

  • wrote on last edited by
    #26

    Hello @phenomlab

    I like your iframe :

    a414dfb3-db00-4dd1-a50b-3ef781deaea6-image.png

    Can you please provide your CSS code with me for Iframely Iframe ?

    Thanks in advance dude

  • Hello @phenomlab

    I like your iframe :

    a414dfb3-db00-4dd1-a50b-3ef781deaea6-image.png

    Can you please provide your CSS code with me for Iframely Iframe ?

    Thanks in advance dude

    wrote on last edited by
    #27

    @DownPW this was actually stolen from @crazycells (😁) and slightly modified, so I can’t really take the credit.

    His original response to the iFramely guide I posted contains the CSS he’s using is here

    https://sudonix.com/topic/331/how-to-install-a-self-hosted-instance-of-iframely-for-use-with-nodebb/2?_=1668364874877

  • phenomlab phenomlab referenced this topic on

Related Topics
  • NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    6k Views
    phenomlab
    @DownPW I still do not see any issues.
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    3k Views
    phenomlab
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • nodebb loading emojis

    Solved Configure nodebb emojis
    16
    1
    1 Votes
    16 Posts
    6k Views
    phenomlab
    @DownPW sure. Let me have a look at this in more detail. I know nginx plus has extensive support for this, but it’s not impossible to get somewhere near acceptable with the standard version. You might be better off handling this at the Cloudflare level given that it sits in between the requesting client and your server.
  • restarting nodebb on boot

    Unsolved Configure nodebb
    3
    1 Votes
    3 Posts
    2k Views
    phenomlab
    @eeeee said in restarting nodebb on boot: can I just run nodebb under nodemon for auto restarts? It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.
  • 4 Votes
    8 Posts
    5k Views
    WesleyMoura
    @phenomlab Sorry to delay in responding, yes as i mentioned above, i had to remove my redis from docker and reinstall a new image with this command docker run --name=redis -p 127.0.0.1:6379:6379 -d -t redis:alpine and now when i test my ip and port on https://www.yougetsignal.com/tools/open-ports/ the status of my redis port is closed. I think which to configure firewall in droplet digital ocean is a good idea too, and i will configure soon. Thanks for the help!
  • iFramely self host help

    Solved Configure iframely hosting
    10
    9 Votes
    10 Posts
    4k Views
    phenomlab
    @DownPW https://sudonix.com/topic/331/how-to-install-a-self-hosted-instance-of-iframely-for-use-with-nodebb
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    5k Views
    phenomlab
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    17k Views
    phenomlab
    @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.