Also, I ran a port scan on the resolving IP address of the domain name, and discovered that the port given in the config.json file in the URL of the instance is not even open, as you can see below:
Nmap scan report for static.reserve.wtt.net.hk (218.255.80.122)
Host is up (0.25s latency).
Not shown: 992 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
1723/tcp open pptp
3211/tcp open avsecuremgmt
3306/tcp open mysql
3371/tcp open satvid-datalnk
8007/tcp open ajp12
8008/tcp open http
Nmap done: 1 IP address (1 host up) scanned in 22.84 seconds
Additionally, It appears that this domain is utilizing a shared hosting provider, which likely has something to do with the mismatching SSL certificates, especially since most shared hosting providers use VHOST configuration to allow multiple domains to be loaded from the same port, and the lack of a VHOST record can cause a different domain to attempt to load content to a different address than it is supposed to.
In addition, you can see that the IP I scanned here does indeed resolve to the domain in question by viewing this link:
https://securitytrails.com/list/ip/218.255.80.122
UPDATE:
I discovered when investigating a bit further into the SSL mismatch error that @ahmaddanial found, that when connecting to the domain on port 80 (HTTP) the " Wonderful 電話報更系統" login page is shown. However, when connecting to the same address over HTTPS on port 443, the response given is a certificate warning showing that the HTTPS certificate is not able to be verified, and upon bypassing the warning and continuing to the page, a different response is given, as you can see below:
In addition to the discovery above, when browsing to the actual domain name, and not the IP address of the domain, and connecting over HTTPS and HTTP, it does appear that the domain does resolve to the same URL, however, when connecting over HTTPS it does inform me of a certificate not matching, which leads me to strongly believe that virtual hosting (VHOST) configuration has not been configured in the domain web server configuration, and I do believe that simply changing this in your web server configuration files would help quite a bit. (see below for domain when directly browsed to over HTTPS/HTTP)
