If HTTP works normally but SOCKS5 does not, this is usually caused by your network or ISP blocking the default SOCKS5 port.
Solution
To resolve this, simply change the port number of your proxy.
Switching to an alternative port (e.g., 1081, 1082, etc.) can bypass network restrictions and restore SOCKS5 functionality.
Example
Original:
gate.nodemaven.com:1080:NodeMavenTest-country-us-region-california-sid-5039368ca1184-filter-medium:1951069ad0de4
Updated:
gate.nodemaven.com:1081:NodeMavenTest-country-us-region-california-sid-5039368ca1184-filter-medium:1951069ad0de4