@ricirick I checked feudalife.indiegala.com on SSL Labs and there might be something for you to look into.
First off, the IP adressess for feudalife.indiegala.com are as following, according to multiple DNS servers (I checked Cloudflare, Google and 9Quad, also from multiple devices and networks to make sure there is no DNS cache issue):
A (IPv4): 45.79.248.227
AAAA (IPv6): [2a01:7e01:0:0:f03c:92ff:fe15:ad5a]
SSL Labs, when checking feudalife.indiegala.com, shows seperate results for both IP adresses:
45.79.248.227 is doing fine with TLS 1.3 and 1.2 support. I can confirm this on my side since I can directly connect to that IP and land on the usual feudalife website.
For [2a01:7e01:0:0:f03c:92ff:fe15:ad5a], the test returns "Assessment failed: No secure protocols supported". Directly connecting to this IP throws the SSL error.
When I check tracert feudalife.indiegala.com, my ISP (Telekom Germany) is routing me over to [2a01:7e01:0:0:f03c:92ff:fe15:ad5a], and thus trying to access feudalife.indiegala.com throws the SSL error. Only when I deactivate IPv6 on my network adapter (or use an internet connection by another provider that has not deployed IPv6, e.g. O2/Telefonica Germany), I get routed towards 45.79.248.227, and the site loads fine when accessing the URL.
My guess is that, since you said there was a change in host server, something might have gone wrong in regards to the IPv6 TLS setup in the process. Since IPv6 is not widely deployed yet for some reasons (according to
Google, worldwide deployment rate of roughly 30%, only Germany, Belgium, India and Malaysia have a deployment rate of over 50%), this would also explain why only a few users are getting consistent problems in regard to the SSL error while many others can access the page without problems.