Server Error Reports

[gnif]

edit: I conducted some tests in another place (to not spam here). Something insane is going on. I can send the characters I did send above, but then I can’t, then I can send them again.

Sounds a bit as if the two EEVBlog hosts do not have identical configuration?

They do, it's not possible for them to not be as they are maintained by puppet.
I am sorry everyone, my health has prevented me from getting back to this yet. I know it's frustrating, hopefully ill be able to investigate this in the coming few days.

[2N3055]

Getting better should be your first priority... 

[squadchannel]

Code: [Select]

Loading [MathJax]/extensions/Safe.js
am I only one who noticed that a small message pops up in the bottom-left corner of the browser when I refresh the page?

[golden_labels]

Sounds a bit as if the two EEVBlog hosts do not have identical configuration?

Such a possibility is why I mentioned the exact IP address and certificate in another report.

But latter tests were done in a single, short session. I was interacting with only one IP address. This implies a single host unless anycast or a front load balancer is at play.

More so, I can now confirm it happens on both addresses.

They do, it's not possible for them to not be as they are maintained by puppet.

My first report was for 192.154.109.3. Just now I tested it on 192.154.111.219. Problems appear on both.

I am sorry everyone, my health has prevented me from getting back to this yet. I know it's frustrating, hopefully ill be able to investigate this in the coming few days.

In me it causes curiosity, not frustration.

Get better, take your time. I believe we can live with avoiding the @ character where it triggers the bug.

[gnif]

Sounds a bit as if the two EEVBlog hosts do not have identical configuration?

Such a possibility is why I mentioned the exact IP address and certificate in another report.

This is because the LetsEncrypt SSL certificates are automatically generated and signed per host on a 15 day cycle. The certs do not get distributed by Puppet, but the config that generates them does. Because of various things that have occurred over the years (fire at the DC/replaced server, etc), they are simply no longer in sync for the refresh period, which doesn't really matter.

But latter tests were done in a single, short session. I was interacting with only one IP address. This implies a single host unless anycast or a front load balancer is at play.

Load balancer, you will ping pong between servers no matter which IP you hit depending on server load.

More so, I can now confirm it happens on both addresses.

As expected, the public have no control over which server handles the request, by design.

Get better, take your time. I believe we can live with avoiding the @ character where it triggers the bug.

Thanks

[golden_labels]

Earlier there was a question of reproducibility. It seems that this exact sequence is a sufficient condition to trigger the bug (but not a ncessary condition):

At-sign Pound Euro (separated by spaces).

Exact codepoints:  U+0040, U+00A3, U+20AC.

It may not be the minimal one, but should be enough for debugging.

[gnif]

FYI: https://www.eevblog.com/forum/chat/scheduled-eevblog-server-maintenance/

[44kgk1lkf6u]

I often get the "you are banned from using this forum" message after the CrowdSec check passes.  Is it necessary to have both?

[gnif]

Crowdsec is absolutely required, the ban however seems to be something different. Please DM me a screenshot and your IP and I will investigate the ban itself.

In future please do not though reply to this thread unless there is actually a server error.