Setting Proxy Using Freegate - Proxifer And Ccproxy?

I have two computers (192.168.1.101 and 192.168.1.102) connected to a TP-Link TD-W8960N (192.168.1.1).I have the following softwares:[URL]However "Freegate" is a proxy software, but it still has some restrictions on particular websites, so I planned to bypass this limitation like this:

1. I ran the Freegate on 192.168.1.102 and then opened CCProxy and then I used Proxifer to set all data transmissions of CCproxy through Freegate by setting a rule in Proxifer. I put IP: 127.0.0.1 Port: 8580 Protocol: HTTP in Proxifier.

2. I ran Proxifier on 192.168.1.101 and set the IP: 192.168.1.102 Port: 808 Protocol: HTTPS as the proxy setting in it.I checked the internet and the configuration was successful. It seemed like I had directly run Freegate on this computer and since I tested those particular websites and they were blocked by Freegate servers, so everything was correct.

3. Now I managed to set a chain proxy configuration in Proxifier in 101 so I could bypass the Freegate limitation. I went to Free Proxy List - Public Proxy Servers (IP PORT) - Hide My ***! and picked some free SOCKS5 and HTTPS proxies. I tested them individually to see if they were working properly and they were. Then I set the chain proxy like this:

192.168.1.102:808 (HTTPS)
IP:Port (HTTPS/SOCKS5)

It didn't work... I received "connection closed unexpectedly" in Proxifier on 101 and "IP (the IP I picked up from hidemyass) : Client requested HTTPS connection. use separate HTTP connection for this." on 102.

1. I also tried Port Forwarding on my router and it didn't work either.

2. I couldn't connect CCProxy to Freegate via other protocols in Proxifier rather than HTTP. When testing I got the error that Freegate doesn't support SSH protocol. This most likely means that there is no built-in interface in Freegate to allow other softwares to connect to it via other protocols rather than HTTP.

3. I used port scanner to see if any other ports were open on 127.0.0.1 so I could use another protocol, and nope there wasn't any rather than 8580 : HTTP.