(Quote)

(Quote)

Which increasingly suggests that the incident at CC was largely due to a human error at CC

(Quote)

(Quote)

(Quote)

Ok, but here's the thing. If this was really a human error on CC's part, would you trust them with anything in the future? Because personally, I wouldn't trust even if they said 'good morning'

(Quote)

proxy, but it either results in a 502 or 444 error.

At some point, you'll need to "update-initramfs -u" I ended up doing it later, after rebooting and getting a "resume" error, though it eventually boots without swa

Internal Server Error500Internal Error (ID 165344224850745)

bro, you don’t have many chances for error.

There's talk that this incident was due to a human error (at CC) + a Virtualizor bug (so the bug alone wouldn't have been sufficient for the incident)

I looked it up earlier when I saw it mentioned and it looks like they started using it here in their most recent offer thread, but there's a thread from 11/2023 with an error msg showing /home/coloclo

(Quote)

(Quote)

Exactly. It could very well be human error. @raindog308 could be wrong and made assumptions.

(Quote)

(Quote)

@mateolee said: