Forum Discussion
The client and server cannot communicate, because they do not possess a common algorithm
Thank you kyazaferr, I appreciate your reply. I am aware that the server should probably be upgraded, however it is on a VPS rental and the folks at the VPS company have been MIA / AWOL for a long time, and have not yet set up a secondary virtual HDD for me again, for backing up the system. Some options short of backing up and upgrading would be nice.
The website for my HalcyonGrid https://grid.toallchurches.net is using ASP .NET v4.0 Classic, on IIS 7.5. MySQL Server 8.0.26, Connector/NET 8.0.26, and have MySQL Workbench 8.0 CE, and is a template from https://myworldsrc.com The website itself works, although there's several consoles for the HalcyonGrid.
Whip Assets 1, Grid Users 2, Grid Server 3, Grid Messaging 4, Grid Aperture 5, then each region is 9500-9509, for 10 regions.
2-4 are all getting that same error as above, although 1 is getting stuck at one of the asset folders, which may not be the same issue.
Also the first four(4) of the region consoles are causing the following error:
---------------------------
Halcyon.exe - This application could not be started.
---------------------------
This application requires one of the following versions of the .NET Framework:
.NETFramework,Version=v4.8
Do you want to install this .NET Framework version now?
---------------------------
Yes No
---------------------------
If I hit Yes, it opens the download page for .NET 4.8.1, which can't run on Windows Web Server 2008 R2, and if I hit No, it shows Error -2146232576.
Although I do have .NET 4.8 installed.
Thank you, Shalom.
- kyazaferrNov 21, 2024MCT
VPS Issues and Backup Options
Since the VPS company has been unresponsive, I understand the frustration. While upgrading your server or getting a secondary virtual HDD might be a long-term solution, here are a few alternatives you can consider for your current setup:
- Cloud Backup Solutions: Even without a secondary HDD, you could explore cloud-based backup solutions that are independent of the VPS provider. Services like Backblaze, Acronis, or Carbonite can back up your critical data without needing a physical secondary disk. They also offer automated backups and can be set up with minimal configuration.
- Remote Backup: If you have access to another server or cloud storage, consider setting up remote backup solutions like Rsync (Linux-based) or Robocopy (Windows-based) for scheduled file copying to another server or cloud storage provider.
- Database Backup: For MySQL, consider using MySQL's built-in backup utilities (mysqldump) or configuring automated backups via a third-party service that supports MySQL databases. This way, you don’t need to rely on the VPS provider for backing up your databases.
- Virtual Machine Snapshots: If your VPS hosting supports it, consider using snapshots to back up the entire server state. These snapshots can be taken periodically and stored as part of your disaster recovery strategy.
- Server Monitoring: If the VPS company is unresponsive, it might be worth looking into more reliable VPS providers or exploring cloud options like AWS, Google Cloud, or Azure, which offer strong support and flexible backup solutions.