Mahjong Soul, MITM mode , error on connecting

[zc2tech]

Akagi v3.3.3

I tried proxy tool like Proxifier or ProxyBridge using Socket5 proxy, and got below error. If I use http/https proxy, although there was no error, there not any advice from Akagi as if it did not intercept any traffic.

[07.21 15:42:15] 雀魂麻將(mahjongsoul).exe (12132) - majsoul-hk-game.oss-accelerate.aliyuncs.com(8.131.131.254):443 error : Could not connect through proxy 127.0.0.1(127.0.0.1):23410 - Warning : proxy server returned an unexpected reply 72 Proxy server uses an unsupported protocol or authentication is required.

[shinkuan]

More details needed. I suggest you debug with an AI agent.

[thefiz]

I’m seeing what looks like the same issue with Akagi 3.6.1 using MITM mode with Proxifier and the standalone Mahjong Soul client (jantama_mahjongsoul.exe).

Proxifier appears to be routing the client correctly through Akagi at 127.0.0.1:23410 using an HTTPS proxy rule. In Proxifier’s connection list, the targets are shown with hostnames such as:

• engsbk.mahjongsoul.com:443
• en-sdk-api.yostarplat.com:443
• udata-api-us.open.yo-star.com:443

However, Akagi receives those connections as IP-literal CONNECT requests instead of hostname-based CONNECT requests, for example:

CONNECT uri_host=47.252.97.9 host_hdr=47.252.97.9:443
raw-tunneling IP-literal CONNECT to 47.252.97.9:443

This happens repeatedly throughout the session. Because Akagi raw-tunnels the IP-literal connections, it never appears to inspect the Mahjong Soul WebSocket traffic, and the game tracker remains waiting for start_game.

I also tested Proxifier’s “Resolve hostnames through proxy” option. With that enabled, Mahjong Soul fails to connect entirely and shows error 100404: Network error. With normal/local DNS resolution enabled, the game works, but Akagi only sees the resolved IPs and raw-tunnels them.

My Proxifier setup has the Mahjong Soul executable routed through 127.0.0.1:23410 and loopback addresses excluded/direct, so this does not appear to be the loopback recursion issue.

It looks like Proxifier knows the original hostname internally but sends Akagi a CONNECT request using the resolved IP, which causes Akagi’s IP-literal raw-tunnel behavior to kick in.

Is there currently a supported Proxifier configuration for the standalone Mahjong Soul client that preserves the hostname in the CONNECT request, or would Akagi need to recover the hostname from TLS SNI / otherwise handle these IP-literal connections differently?