Skip to content

Iframely (Nodebb)

Solved Configure
40 4 12.4k 1
  • I have install Iframely nodebb plugin and setup with my local IP (because it’s a VM on no prod server) like this :

    dfcaa6bd-ef9d-4cf3-95ad-f055beb8926c-image.png

    Doesn’t work

    @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.

    bddf233f-69cb-4169-9aea-3ccc85aead31-image.png

    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 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.

    bddf233f-69cb-4169-9aea-3ccc85aead31-image.png

    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).

    @phenomlab

    I have open the port on my router:

    1c93d90e-0cec-44b3-9939-4025e28456c2-image.png

  • @phenomlab

    I have open the port on my router:

    1c93d90e-0cec-44b3-9939-4025e28456c2-image.png

    @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

  • 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

    03a1fd88-f7c9-4fe2-805c-d78a63e7db17-image.png

    The NAT on my router and the server is OK on 8061 port

  • 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

    03a1fd88-f7c9-4fe2-805c-d78a63e7db17-image.png

    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.

  • @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 😉

  • @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

  • @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 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.


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Nodebb and emails

    Solved Configure nodebb
    27
    5 Votes
    27 Posts
    8k Views
    @Panda it will use SMTP. In all cases, I never use any plugin to send email. I’ll always send it raw.
  • Fixed background to nodebb forum

    Solved Configure nodebb
    25
    4 Votes
    25 Posts
    8k Views
    @Panda said in Fixed background to nodebb forum: Chatgpt told me the ::before method. Go figure
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    2k Views
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • NodeBB: Opening the Composer for replies

    Solved Configure cms composer
    2
    0 Votes
    2 Posts
    888 Views
    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below [image: 1681314389744-82ca1209-31be-4a51-a641-9887b5a238b8-image.png] Failing that, you’ll need to use the reply button in the sticky toolbar [image: 1681314442570-1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png]
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    2k Views
    @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: 1680448167972-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.
  • restarting nodebb on boot

    Unsolved Configure nodebb
    3
    1 Votes
    3 Posts
    2k Views
    @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.
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    4k Views
    @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.
  • NodeBB metadata

    Solved Configure nodebb
    4
    2 Votes
    4 Posts
    2k Views
    @phenomlab said in NodeBB metadata: @jac Are you sure ? https://www.google.co.uk/search?q=site%3Astockportcounty.fans&sxsrf=AOaemvLwnaZL-PliU_2dBOg_Eo1pMVhBjg%3A1638982328139&source=hp&ei=uOKwYeatBcOsad3yp7AE&iflsig=ALs-wAMAAAAAYbDwyLBSDcG5XYoFCKwQFhgz94wTxOcV&ved=0ahUKEwjm6dX71NT0AhVDVhoKHV35CUYQ4dUDCAk&uact=5&oq=site%3Astockportcounty.fans&gs_lcp=Cgdnd3Mtd2l6EAM6BAgjECc6CwgAEIAEELEDEIMBOg4ILhCABBCxAxDHARCjAjoRCC4QgAQQsQMQgwEQxwEQowI6BQguEIAEOggIABCABBCxAzoFCAAQgAQ6CAguELEDEIMBOgsILhCABBDHARCvAToICC4QgAQQsQM6BQgAELEDOgsILhCABBDHARDRAzoLCAAQgAQQsQMQyQM6BQgAEJIDUABYySZg0CdoAHAAeACAAW2IAa0NkgEEMjMuMpgBAKABAQ&sclient=gws-wiz Fair enough 🤪🤪.