iQCloud - Troubleshooting HTTP proxy

Owned by Mohamed El Kandoussi
Last updated: Jun 27, 2019 by Conor McCann

Check if the appliance was registered using the HTTP proxy

Make sure the appliance.conf is configured to use the HTTP proxy, to do so check the appliance.conf


  • ~$ cat /opt/appliance-server/appliance.conf

REMOTE_SERVER=127.0.0.1
REMOTE_PORT=8443

If the 2 properties are different you have to register again the appliance:

  • Remove  the appliance.conf.

~$ sudo rm /opt/appliance-server/appliance.conf

  • Restart the appliance process.

~$ sudo appliance-hard-restart.sh


Check if the chisel client is started and configured properly

Is the chisel client configured properly?

On the file /opt/chisel/start_http-tunnel.sh, the variable http_proxy must be set properly: 

http_proxy="http://LOGIN:PASSWORD@PROXY_IP:PROXY_PORT"

http_proxy="http://iquate:Falcon99@192.168.0.36:3128"

Is the chisel client up and running?

Execute following command:

~$ ps -aux | grep chisel

You should have a entry like this:

./chisel client -v http://queue.iquate.net:443 3000 127.0.0.1:8443:queue.iquate.net:443


if you don't find thus entry, the chisel process is not started just start the chisel client: /wiki/spaces/HADM/pages/1508954



Check chisel log


The logs are located here: /opt/chisel/chisel.log

~$ less /opt/chisel/chisel.log

2018/10/09 14:09:32 client: Connecting to ws://queue.iquate.net:443
2018/10/09 14:09:32 client: tunnel#1 0.0.0.0:3000=>0.0.0.0:3000: Listening
2018/10/09 14:09:32 client: tunnel#2 127.0.0.1:8443=>queue.iquate.net:443: Listening
2018/10/09 14:09:37 client: Handshaking...
2018/10/09 14:09:37 client: Fingerprint 37:45:e2:35:35:34:40:f8:50:f7:2e:6c:1a:b1:6d:96
2018/10/09 14:09:38 client: Sending config
2018/10/09 14:09:38 client: Connected (Latency 165.923809ms)


If everything is ok, the logs output will be similar:


The first line shows the url of the chisel server side, the client is trying to connect to.


You should have the same value: client: Connecting to ws://queue.iquate.net:443


The last line shows the status of the session:


You should have the status connected : client: Connected (Latency xxx.xxxxxxms)


If the client keeps trying the connect without success, check  the chisel configuration (sad)