Testing HTTP Interface with wget and curl

First check if the Iguana service is running using something like:

./iguana --service status

Then another thing to check is the IguanaServiceLog.txt file - you can see if there were issues listening on the port. This file is found in the working directory of Iguana typically something like:

/home/<user id>/.iNTERFACEWARE/IguanaX/<instance dir>/IguanaServiceLog.txt

You can test if IguanaX is running on a port using either curl or wget. These are command line tools which can be used to pull down a file from a web server.

Most systems will have either curl or wget - you’ll need to see what the default tool is for your system. They can both operate with similar syntax:

wget http://localhost:7654/
curl http://localhost:7654/

These are both command line clients for web browsers - they are useful when you are on a server which doesn’t have a built in web browser like many Linux servers.

If these fail to connect then it’s indicative of a problem with Iguana listening on port its web interface. Things to check here are whether you can run Iguana at the command line like this:

[ec2-user@ ~]$ ./iguana
Running service as command line application. (ctrl+C to exit)
Instance: /home/ec2-user/.iNTERFACEWARE/IguanaX/Yj75m3hhEnpLVgp65kNgUN/
Listening on http://localhost:7654/
Normal production mode.
Initializing the log system...
Log system initialization completed.
Control+C to exit.

If you can run it this way then it might be worth checking if SELinux is active.