Skip to content

www. Infront stops website access?

Solved Configure
10 2 3.2k 1
  • wrote on last edited by Panda
    #1

    Strange thing today, thought my pals nodebb.com site was down, as browser prevented access.
    It gave the your connection is not private security warning (like when theres no SSL)
    But Ive been told issue was that i was using
    www.sitename.nodebb.com
    And should just use sitename.nodebb.com
    !
    Have I missed something, since when did www. stop websites accessing properly?

  • Strange thing today, thought my pals nodebb.com site was down, as browser prevented access.
    It gave the your connection is not private security warning (like when theres no SSL)
    But Ive been told issue was that i was using
    www.sitename.nodebb.com
    And should just use sitename.nodebb.com
    !
    Have I missed something, since when did www. stop websites accessing properly?

    wrote on last edited by phenomlab
    #2

    @Panda www these days is typically an alias record in DNS, and isn’t a requirement for the site to function. Most websites (including this one 🙂 ) drop the www part as it’s less for people to type (but it will accept those requests, then strip it back to the actual URL). Only those who have a legacy reason to include www in their website addresses these days do so.

    It’s considered unnecessary in today’s internet landscape. However, if the site presents an SSL certificate mismatch or warning, then this will actually not only harm your SEO (Google penalises against this), but it also means that if you proceed, every transaction on the site will be in plain text - not good at all.

    Furthermore, those sites (like NodeBB) that require a specific URL to operate against won’t work properly because of the mismatch, and that site should then be forcing all non-https traffic to https to ensure that this does not happen.

    Essentially, not doing so isn’t just bad etiquette, it’s bad for overall security. Depending on the host in use (either Apache or NGINX), there are a variety of ways to accomplish this. One of the easiest ways if you use Cloudflare is to do it with a page rule - failing that, a few simple lines of config is all it takes to resolve it.

    A bit more on the whole www part here

    https://dropwww.com/why

  • phenomlab phenomlab has marked this topic as solved on
  • @Panda www these days is typically an alias record in DNS, and isn’t a requirement for the site to function. Most websites (including this one 🙂 ) drop the www part as it’s less for people to type (but it will accept those requests, then strip it back to the actual URL). Only those who have a legacy reason to include www in their website addresses these days do so.

    It’s considered unnecessary in today’s internet landscape. However, if the site presents an SSL certificate mismatch or warning, then this will actually not only harm your SEO (Google penalises against this), but it also means that if you proceed, every transaction on the site will be in plain text - not good at all.

    Furthermore, those sites (like NodeBB) that require a specific URL to operate against won’t work properly because of the mismatch, and that site should then be forcing all non-https traffic to https to ensure that this does not happen.

    Essentially, not doing so isn’t just bad etiquette, it’s bad for overall security. Depending on the host in use (either Apache or NGINX), there are a variety of ways to accomplish this. One of the easiest ways if you use Cloudflare is to do it with a page rule - failing that, a few simple lines of config is all it takes to resolve it.

    A bit more on the whole www part here

    https://dropwww.com/why

    wrote on last edited by Panda
    #3

    @phenomlab the only problem is that some places require the www to know its a website.
    E.g. if I write,
    aignite.nodebb.com
    (This page does recognise its a link. But some chat / media pages dont)
    Or if I write
    www.aignite.nodebb.com

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    Further thought, how does this site know which of the following are links?
    test
    test.one
    test.com
    test.test2.org

  • @phenomlab the only problem is that some places require the www to know its a website.
    E.g. if I write,
    aignite.nodebb.com
    (This page does recognise its a link. But some chat / media pages dont)
    Or if I write
    www.aignite.nodebb.com

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    Further thought, how does this site know which of the following are links?
    test
    test.one
    test.com
    test.test2.org

    wrote on last edited by
    #4

    @Panda said in www. Infront stops website access?:

    the only problem is that some places require the www to know its a website

    This isn’t the case at all. All websites even without the www part will still begin with either http or https even if entered directly into the address bar as (for example) mysite.mydomain.com - the browser will first try http then https and ideally, if the request is received as http it should then by issued a 301 permanent redirect to https

  • @phenomlab the only problem is that some places require the www to know its a website.
    E.g. if I write,
    aignite.nodebb.com
    (This page does recognise its a link. But some chat / media pages dont)
    Or if I write
    www.aignite.nodebb.com

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    Further thought, how does this site know which of the following are links?
    test
    test.one
    test.com
    test.test2.org

    wrote on last edited by
    #5

    @Panda said in www. Infront stops website access?:

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    100%, yes, as it’s the industry standard. If anyone does write www that should auto redirect to the correct convention. Try accessing this site as www and see what happens.

  • @phenomlab the only problem is that some places require the www to know its a website.
    E.g. if I write,
    aignite.nodebb.com
    (This page does recognise its a link. But some chat / media pages dont)
    Or if I write
    www.aignite.nodebb.com

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    Further thought, how does this site know which of the following are links?
    test
    test.one
    test.com
    test.test2.org

    wrote on last edited by
    #6

    @Panda said in www. Infront stops website access?:

    Further thought, how does this site know which of the following are links?
    test
    test.one
    test.com
    test.test2.org

    Because the a href anchor will only react to valid TLD (Top Level Domains), of which .one isn’t, and no suffix at all will obviously be ignored and treated as text.

  • @Panda said in www. Infront stops website access?:

    From what you wrote above, do you say its ok for nodebb to have it set up such that the www one doesnt work?
    Many people not so technical may write www., out of habit.

    100%, yes, as it’s the industry standard. If anyone does write www that should auto redirect to the correct convention. Try accessing this site as www and see what happens.

    wrote on last edited by Panda
    #7

    @phenomlab
    Im not talking about entering in a browser, but writing in a post

    So on Discord I mesaged someone
    www.aignite.nodebb.com
    And it gave the SSL error when clicked
    Nodebb.org arent striping the www

  • @phenomlab
    Im not talking about entering in a browser, but writing in a post

    So on Discord I mesaged someone
    www.aignite.nodebb.com
    And it gave the SSL error when clicked
    Nodebb.org arent striping the www

    wrote on last edited by
    #8

    @Panda if I check that URL, it redirects to the NodeBB home page.

  • @Panda if I check that URL, it redirects to the NodeBB home page.

    wrote on last edited by
    #9

    @phenomlab said in www. Infront stops website access?:

    @Panda if I check that URL, it redirects to the NodeBB home page.

    Yes, but why?!

  • @phenomlab said in www. Infront stops website access?:

    @Panda if I check that URL, it redirects to the NodeBB home page.

    Yes, but why?!

    wrote on last edited by
    #10

    @Panda because there is no match for the DNS entry specified. The receiving web server parses the headers looking for a destination hostname to match, and anything the web server is unable to resolve will be sent back to the root.


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
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    6k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • TNG + Nodebb

    General tng genealogy nodebb plugin
    4
    0 Votes
    4 Posts
    2k Views
    phenomlab
    @Madchatthew said in TNG + Nodebb: you have to try and use duck tape and super glue to change something to make it do what you want it to do I couldn’t have put that better myself.
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlab
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • 36 Votes
    55 Posts
    31k Views
    phenomlab
    @DownPW I see why. The code relies on the existence of [component="topic/quickreply/container"] However, this by definition means that the below has to be enabled [image: aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png] It will then work [image: 7fb38631-e0f3-46ef-b652-00929d927b13-image.png] For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component. The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on
  • Gettin Erors NodeBB

    Solved Configure nodebb eror
    7
    0 Votes
    7 Posts
    2k Views
    cagatay
    @phenomlab no forum is working goods. there is no eror message since yestarday.
  • 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!
  • [NodeBB] username cards

    Solved Customisation nodebb
    8
    5 Votes
    8 Posts
    3k Views
    Sampo2910
    @phenomlab Aha…nice to know. As always thank you for the reply and information.