Fedora Core 6 + EZproxy (not working)

tekmann33 · 01-11-2007, 03:16 PM

I have installed and run EZproxy on a SuSe machine with relatively no problem. Recently I changed to Fedora Core 6 and I am having issues with getting the default page for EZproxy to come up locally and remotely. Here is what I did:

1. I installed EZproxy as per the instructions on
http://www.usefulutilities.com/download/linux.html

Code:

# Create a directory for EZproxy and make it your current directory with command such as:

    mkdir /usr/local/ezproxy
    cd /usr/local/ezproxy 

# Download ezproxy.bin into this directory. If you download this file on different system and use FTP to move it to your EZproxy server, be sure to perform the transfer using binary.
# Rename the download file from ezproxy.bin to ezproxy and make it executable with the commands:

    mv ezproxy.bin ezproxy
    chmod 755 ezproxy

# To create the default version of most of the files mentioned above, issue the command:

    ./ezproxy -m

The "-m" stands for "missing file replacement" and this command can be used at any time to reconstruct any missing files without overwriting existing files that you have changed.

2. This Proxy Server (which runs on Fedora) is behind a Firewall and for now is just for testing purposes for a future project and to learn about EZproxy itself, so I do not have a domain name for the server and just refer to it by its IP address = 10.3.0.99.

All remote access to the ezproxy server will be from behind the firewall from the same 10.3.0.X network.

3. I go to the appropriate directory "/usr/local/ezproxy" and start the service "./ezproxy" and get the following output, which looks like it is running without a problem.

Code:

[root@BriansFC ezproxy]# ./ezproxy
EZproxy for Linux 4.0f GA (2006-12-10)
You may evaluate this unregistered copy of EZproxy for up to 30 days.
For further information, visit http://www.usefulutilities.com

Guardian initialized
Guardian starting EZproxy

EZproxy for Linux 4.0f GA (2006-12-10)
You may evaluate this unregistered copy of EZproxy for up to 30 days.
For further information, visit http://www.usefulutilities.com

Server name BriansFC
The use of a server name with no periods will cause some databases to fail.
Proxy by port
Due to export restrictions, SSL (https) features are
  disabled. To evaluate SSL features, request a test license
  from support@usefulutilities.com.

To configure EZproxy to start automatically when the system is booted,
press CTRL/C and issue the command:
     ./ezproxy -si

To run EZproxy in the background, press CTRL/C and issue the command:
     ./ezproxy start

You may not see any additional messages, but EZproxy is running.

If you press CTRL/C or end this session, EZproxy will stop running.

According to the installation instructions, I should be able to connect to EZproxy remotely by typing in the URL and the port number 2048 to receive the login page.

Code:

# Using your web browser, connect to your server on port 2048. If your EZproxy server was named ezproxy.yourlib.org, you would use this URL:

    http://ezproxy.yourlib.org:2048/admin

#

Enter the username and password that you created when you edited the ezproxy.usr file. This should bring you to the main server administration page.

You can also try a URL similar to:

    http://ezproxy.yourlib.org:2048/

to access the default menu of databases configured in your server.

However, since I do not have a domain name and I am behind a firewall, I just use the IP address and port number

http://10.3.0.99:2048/

The message that I receive in the browser is a "Unable to connect" message.

I try to bring up the page locally from the ezproxy server itself

http://localhost:2048/

and I get the same "Unable to Connect" message.

Just to see if it is a http issue, I started apache up and brought up the default page both remotely and locally with no problem.

I disabled SElinux and I still have the same problem.

I also checked to see if port 2048 is open:

Code:

nmap -p 2048 localhost

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-01-11 15:09 CST
Interesting ports on localhost (127.0.0.1):
PORT     STATE SERVICE
2048/tcp open  dls-monitor

Nmap finished: 1 IP address (1 host up) scanned in 0.132 seconds

Which it is.

Am I forgetting something basic with IP resolution or is this and ezproxy issue?

Any help would be appreciated.

unSpawn · 01-12-2007, 10:43 AM

Am I forgetting something basic with IP resolution or is this and ezproxy issue?
I'd say contact the vendor: they make money off of it, so they should deal with problems.
Since it's not FOSS SW its a good test to see what kind of support you can expect.