Skip to content

www. Infront stops website access?

Solved Configure
10 2 1.7k 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?

    @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

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

    @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

    @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

    @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

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

    @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

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

    @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?!

    @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
  • Planned sunset of NTFY plugin

    Pinned Announcements push nodebb ntfy
    7
    1
    8 Votes
    7 Posts
    2k Views
    I’ve noticed that I’m the only one subscribed to the push notifications on this site. If you were using NTFY previously, and have noticed that you’ve not had any alerts for a while, it’s because this feature has been disabled. You’ll now need to use the push notification to replace NTFY as mentioned in the first post.
  • Nodebb 3.2.0

    Bugs nodebb nodebb 3.2.0
    20
    1
    2 Votes
    20 Posts
    5k Views
    @crazycells yes, I’m aware of that. Need to fix EDIT- fixed. Caused by the same CSS that is used to absolutely position the “verified” group badge in the posts view. Amended this CSS so that is specifically targets the post stream as below li[component="post"] a[href*="/groups/verified"] { position: absolute !important; left: 8px; z-index: 2; margin-top: 1px; border-radius: 999px !important; line-height: 14px; display: block; height: 22px; margin-left: 0px !important; }
  • 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; }
  • Upgrade Problem from 2.8.3 to 2.8.4

    Solved Configure nodebb
    35
    1
    8 Votes
    35 Posts
    7k Views
    @cagatay No, you can ignore that.
  • optional "snow falling" theme

    Solved Customisation nodebb
    6
    6 Votes
    6 Posts
    1k Views
    @Sala ok, but that’s still the same loop which is going to have an impact on the CPU.
  • Custom badges

    Solved Customisation nodebb
    103
    2
    49 Votes
    103 Posts
    30k Views
    Perfect
  • 4 Votes
    8 Posts
    4k Views
    @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] Help for my custom CSS

    Solved Customisation nodebb css bugfix
    237
    49 Votes
    237 Posts
    95k Views
    @baris said: You should change your selectors so it doesn’t look at the entire document. You probably only want to apply fancybox to stuff inside the #content element which is what changes when the user navigates around the page. So use $('#content a').... for your selectors then the forum logo in the header won’t be selected. I modified the JS Fancybox code now and this code and it seem better // --------------------------------------------- // Fancybox Media Reader (Without Website Logo) // --------------------------------------------- if (top.location.pathname !== '/login') { $(window).on('action:posts.loaded', function(data) { console.log("Polling DOM for lazyLoaded images to apply Fancybox"); $(document).ready(function() { $('#content a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); }); }); }); } if (top.location.pathname !== '/login') { $(document).ready(function() { $(window).on('action:ajaxify.end', function(data) { $('#content a').not('.logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); data.preventDefault() // Strip out the images contained inside blockquotes as this looks nasty :) $('#content blockquote img').remove(); }); Fancybox.bind( '#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]', { groupAll: true, } ); }); }); } // Chat fancybox - fires when chat module loaded and AJAX calls new chat $(document).ready(function() { $(window).on('action:chat.loaded', function(data) { // >>> Se limiter au contenu principal uniquement <<< $('#content img').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { var newHref = $(this).attr("src"); $(this).wrap("<a class='fancybox' href='" + newHref + "'/>"); $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); data.preventDefault(); // Strip out the images contained inside blockquotes as this looks nasty :) $('#content blockquote img').remove(); }); Fancybox.bind( '#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]', { groupAll: true, } ); }); }); For the logo, I must use overflow: visible !important; on [component="brand/logo"] /* --- Logo --- */ [component="brand/logo"] { max-height: 50px; width: auto; height: auto; max-width: 100%; display: block; object-fit: contain; object-position: left center; overflow: visible !important; } Better result !!