What’s wrong with -hypertaNk- and where to from here?

it’s nice to blog sometimes…. or just brain dump…
as it stands,
we have ubuntu server 18 lts esm3 on a hyper-v instance on top of a windows server 2016 OS, nearing EOL.
proposed we have;
supermicro superserver, 1u chassis, 32gb DDR4-ECC, 4 x Intel(R) Pentium(R) CPU D1508 @ 2.20GHz (1 Socket), m.2 ssd for proXmox, 4x 512gb Samsung Evo 870 SSD’s in a raidZ1 pool.

storage is insufficient in supermicro server. proxmox as a hypervisor i’m OK with, the same setup will be replicated into a Containerized format instead. So storage handled through TrueNAS, Webserver handled in its own WordPress Instance on a Debian13 container.

The above is the reason I haven’t done the migration 1) owing to storage space, 2) owing to having to re-link everything or do mass database edit&replaces but SQL isn’t my strongsuit.

And the current problem this situation causes?

Ubuntu18 is unable to cURL as it’s unsupported and the server has newer versions of php literally grafted onto the outside with duct-tape. In a word; Janky. unable to reliably communicate with sockets for cURL/php interoperability.
Giant pain in the ass.

Where to? Better case for the current 1u chassis the superserver is in. Add more drives. new proxmox install, truenas setup and data migration/database building, Migrate all data, Relink all data & Pray…

In the interim, things are fine and secure. Can’t run cURL, big whoop – this just breaks some plugin’s i purchased for media players and background videos.

 

Edit TLDR; Server too old to run cURL, and natively support later php. /rip

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Most Voted
Newest Oldest
0
Would love your thoughts, please comment.x
()
x