Testing testing is this thing on?

[My57-150]

Just read an e-mail from Sid saying the issues with the site have been resolved. Just wanted to see if I could get logged in and post.

[Rick_L]

Looking good so far.

[56-210Sedan]

I see you

[Run-em]

I can see you, can you see us, 150?

[567chevys]

No i dont see any one

[NickP]

Looking good

[carls 56 (RIP 11/24/2021)]

working good today.

[smooth 56]

good to see you!

[chevynut]

So the problems we've been arguing about for months weren't the user's fault after all. Hmmmmm

We were told some time ago that the problems were fixed when the server was replaced, but they really weren't. We'll see.

[Trifiver]

So the problems we've been arguing about for months weren't the user's fault after all. Hmmmmm

We were told some time ago that the problems were fixed when the server was replaced, but they really weren't. We'll see.

My email to Sid this morning,

Hi Sid,

After four days of research neither I nor the data center engineers can explain why Nick or Hep are unable to reach the data center.

From what they see at the physical DC there is no reason why these two should not be able to reach the site. The only thing we can guess is that there is something in their individual ISPs that is blocking access.

Can you please ping both of them to see if they can see the site, or they can see the following IP?

http://www.trifivechevys.com

AND

http://173.225.20.129

If they are unable to they win at stump the engineers on this end and will need to contact their ISPs to see why access is being blocked.

Chevynut, we didn't "fix" anything. The Digital Fortress data center engineering team didn't fix anything. No admin, engineer, or technician from anywhere between the box on the rack to the DC OC3 to the cloud fixed anything on this end.

None of us, from three different organizations, can explain why the effected users couldn't see the entire data center, let alone the individual server within that data center that Sid's website lives on. Nor can we explain why, apparently suddenly today, some of them apparently can again.

I accept your continued belief that every non-related issue you combine into your description of "problems we've been arguing about for months," and accept full responsibility for all of them. Whatever is wrong is completely and personally my fault. My inability to resolve all of these issues, no matter the cause, is not meant as an affront the user base on this website, and you have my personal apology that your user experience of my client's website has not been able to meet your expectations.

Again, this is no fault of my client, Sid, but through the complete ineptitude of myself and the national co-location data center I host my services through.