Elements 1.3.3 breaks CMS

See for yourself: Numeric Citizen News

This is very strange. I cannot see any code in the CMS that could cause this “Misdirected Request”.

Are you sure it is the CMS causing the issue? Do you have any custom code on that page, or have any type of CDN setup?

If I could get a login to your server I could take a closer look, if you’re ok with that you can send the details to ben at realmac software :slight_smile:

Could it be that this is a message from the firewall, which is trying to resolve the domain using SNI?

Is the link correct?

This is above my pay grade, but i’ve asked ChatGPT, he says the following:

A 421 usually means the TLS SNI used for the connection does not match the hostname of the HTTP request. With HTTP/2, browsers may reuse a single TLS connection across hosts, and if the server or proxy routes it to the wrong vhost you will see 421.

Why it happens

  • Certificate or vhost mismatch for the exact hostname on the origin.
  • Reverse proxy or CDN reusing an upstream connection for the wrong origin, often after recent server updates. Seen often with Apache, Nginx, Plesk, cPanel, and Cloudflare.

Is this the actual cause? I’m not sure…
Can you ask your hosting provider if they know why this might be happening?

I know we’ll get to the bottom of this and get you back up and running, whatever the root cause is!

I opened a support ticket at Chillidog hosting. They replied to look at my Elements project. Duh.

The problem started when going from 1.3.2 to 1.3.3. Ask me the link to my project and I’ll provide it. There is another CMS component elsewhere that works just fine. Strange.

Here is the htaccess file (reported to be possibly wrong by Chillidog support personal):

# php -- BEGIN cPanel-generated handler, do not edit
# Set the “ea-php84” package as the default “PHP” programming language.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php84 .php .php8 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

We are looking into it, please stand by. We will update your ticket when we have additional information. Thanks

it’s most likely not an htaccess issue (now having seen it). We’re (Chillidog) still investigating it.

This is an issue with the SSL set up for your site as HTTP works:

Your main domain is pointing elsewhere (CloudFlare). Please check that you have FLEXIBLE set on CloudFlare:

See if that resolves it.

Thanks,

Greg

Made the change, still same issue.

@dan this is so strange… I tried renaming the /news page for /new. It fixed the issue. After putting it back to /news, the issue returned. but, what is even more strange is if you navigate to other sections from the top menu component, you’ll see the the /new sections becomes /news sometimes… how weird is that?

@dan I did force an update to the home page, and the /news section returned (in the menu) but clicking the News item brings back the issue.

It seems the problem has been fixed. I don’t how, but now it’s working fine.

Sounds like a CloudFlare/server caching issue to me (but I’m not a server expert). I take it the caching is still switched off on Chilldog?

Yay :tada:

Would have been nice to know exactly what it was, but sometimes these things remain a mystery :face_with_monocle: