(Quote)

(Quote)

I can't even complete the credit card verification because their backend is returning a 502 error.

(Quote)

* If you're running a large, horizontally-scaled app (app running on many physical servers) with significant redundant servers. You can get a lot more bang-for-the-buck running consumer-grade hardware

This error

2023.10.11 07:59:58 LOG3[155]: SSL_read: ../ssl/record/rec_layer_s3.c:308: error:0A000126:SSL routines::unexpected eof while reading

The most pertinent part of the error log appears to be this.

I just went and began my test stream, and Entropy is working. No errors, no problem, smooth sailing on Entropy.

"Error 1001" since I don't have that domain on CF but just point it to 1.1.1.1:80

(Quote)

(Quote)

(Quote)

(MCA, PFA, etc.)RAS features help in error detection and correction, enhancing reliability.Multi-Socket SupportNoYes (Up to 2 sockets)Allows for more redundancy and therefore higher reliability.PCIe

An error occurred 1696931148740 TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:" at new NodeError (node:internal/errors:406:5)

(Quote)

I have received several DMs from folks but when I try to reply it throws a permissions error. So please know if you have reached out to me and I have not replied, it is not from a lack of effort.

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error# 1 Short offline Completed without error 00% 174 -# 2 Short offline C

It seems that the problem was with Debian 12.2. I installed Debian 11.8 and LetsEncrypt worked without any error.

Once you have set the DOCKER_HOST environment variable, you should be able to run docker-compose without any errors.