开云体育

I am running Hercules R3.13 and VMCE-V1.1.2 on a Windows 11 computer (i.p. address 192.168.15.61) and would like to access the Hercules Console from my Web Browser (firefox) on that machine. I enter in the browser and the connection simply times out. I have entered the netstat -a command (see below) and it does not appear that anything is listening on port 8081. Can anyone give me some insight into what is or isn't happening.

Ed.

C:\windows\system32>netstat -a

Active Connections

? Proto? Local Address????????? Foreign Address??????? State
? TCP??? 0.0.0.0:135??????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:445??????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:3270?????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:3389?????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:5040?????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:7680?????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:17500????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:30883????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49664????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49665????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49666????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49667????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49668????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49669????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49670????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 0.0.0.0:49671????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 127.0.0.1:843????????? JOHN-52-2:0??????????? LISTENING
? TCP??? 127.0.0.1:2759???????? JOHN-52-2:2760???????? ESTABLISHED
? TCP??? 127.0.0.1:2760???????? JOHN-52-2:2759???????? ESTABLISHED
? TCP??? 127.0.0.1:2761???????? JOHN-52-2:2762???????? ESTABLISHED
? TCP??? 127.0.0.1:2762???????? JOHN-52-2:2761???????? ESTABLISHED
? TCP??? 127.0.0.1:2763???????? JOHN-52-2:2764???????? ESTABLISHED
? TCP??? 127.0.0.1:2764???????? JOHN-52-2:2763???????? ESTABLISHED
? TCP??? 127.0.0.1:2765???????? JOHN-52-2:3270???????? ESTABLISHED
? TCP??? 127.0.0.1:2766???????? JOHN-52-2:3270???????? ESTABLISHED
? TCP??? 127.0.0.1:3270???????? JOHN-52-2:2765???????? ESTABLISHED
? TCP??? 127.0.0.1:3270???????? JOHN-52-2:2766???????? ESTABLISHED
? TCP??? 127.0.0.1:17600??????? JOHN-52-2:0??????????? LISTENING
? TCP??? 127.0.0.1:49737??????? JOHN-52-2:49738??????? ESTABLISHED
? TCP??? 127.0.0.1:49738??????? JOHN-52-2:49737??????? ESTABLISHED
? TCP??? 127.0.0.1:49740??????? JOHN-52-2:49741??????? ESTABLISHED
? TCP??? 127.0.0.1:49741??????? JOHN-52-2:49740??????? ESTABLISHED
? TCP??? 192.168.15.61:139????? JOHN-52-2:0??????????? LISTENING
? TCP??? 192.168.15.61:1064???? 13.64.180.106:https??? ESTABLISHED
? TCP??? 192.168.15.61:2011???? 123:https????????????? TIME_WAIT
? TCP??? 192.168.15.61:2123???? ec2-3-211-126-36:https? TIME_WAIT
? TCP??? 192.168.15.61:2127???? server-13-35-105-97:https? TIME_WAIT
? TCP??? 192.168.15.61:2147???? yq-in-f156:https?????? TIME_WAIT
? TCP??? 192.168.15.61:2238???? ec2-54-158-114-97:https? TIME_WAIT
? TCP??? 192.168.15.61:2244???? 150-232-115-208:https? TIME_WAIT
? TCP??? 192.168.15.61:2251???? ec2-18-211-164-150:https? TIME_WAIT
? TCP??? 192.168.15.61:2287???? ec2-35-174-179-18:https? TIME_WAIT
? TCP??? 192.168.15.61:2372???? ec2-44-196-88-208:https? TIME_WAIT
? TCP??? 192.168.15.61:2646???? 162.125.35.134:https?? ESTABLISHED
? TCP??? 192.168.15.61:2784???? 162.125.36.2:https???? ESTABLISHED
? TCP??? 192.168.15.61:2801???? 152.199.24.163:https?? CLOSE_WAIT
? TCP??? 192.168.15.61:2803???? yr-in-f95:https??????? TIME_WAIT
? TCP??? 192.168.15.61:2806???? yx-in-f155:https?????? TIME_WAIT
? TCP??? 192.168.15.61:2815???? server-216-137-45-77:https? TIME_WAIT
? TCP??? 192.168.15.61:2817???? 20.44.10.123:https???? TIME_WAIT
? TCP??? 192.168.15.61:2820???? 20.42.73.24:https????? ESTABLISHED
? TCP??? 192.168.15.61:2821???? 20.42.73.24:https????? ESTABLISHED
? TCP??? 192.168.15.61:2824???? atl26s29-in-f6:https?? TIME_WAIT
? TCP??? 192.168.15.61:2829???? 8:https??????????????? TIME_WAIT
? TCP??? 192.168.15.61:2833???? 52.168.117.169:https?? TIME_WAIT

开云体育

开云体育

Dave:

??? OK adding the HTTPPORT 8081 line works. In reading the configuration file I thought that 1.) port 8081 was the default and 2.) the HTTP PORT ${HTTPPORT:=8081} line was what enabled it. I learn something new every day.

Regards:

Ed.

# HTTP Configuration for Hercules V4.x
# ============================================================================
# ----------------------------------------------------------------------------
# Identify the port to find the the Operator Console.
# Ensure you have allowed access to this port via iptables, or firewalld.
# Default is 8081.
# ----------------------------------------------------------------------------
HTTP PORT ${HTTPPORT:=8081}

HTTPPORT 8081

Ed..

================================================

Edward lott wrote:

OK adding the HTTPPORT 8081 line works. In reading the
configuration file I thought that 1.) port 8081 was the
default

AFAIK, there is no default. The port number must be specified on the HTTPPORT configuration file statement itself. And as Dave pointed out, that particular statement was commented out. Thus, the Hercules HTTP Server was never started. It is the existence of the HTTPPORT statement in your configuration file that triggers the Hercules HTTP Server to start. Without it, the server will never start.

and 2.) the HTTP PORT ${HTTPPORT:=8081} line was
what enabled it.

That's a Hercules v4.x Hyperion configuration file statement, *not* a Hercules v3.x configuration file statement.

Originally, Hercules supported two "http" statements: HTTPPORT and HTTPROOT:

*

and, as just explained, it is the existence of the HTTPPORT statement which triggers the server to start.

Starting with Hercules 4.0 however, both statements were deprecated and replaced with the "HTTP" statement instead:

*

Now, with Hercules 4.x, you specify all HTTP Server configuration values via the "HTTP" statement. One specifying the server's root directory ("HTTP ROOT directory") and the other specifying the port number the server should listen for connections on ("HTTP PORT nnnn ...").

But even then (even with *both* statements specified), with Hercules 4.x, the server will not automatically start. To start the Hercules HTTP Server, with Hercules 4.x, you have to *explicitly* specify that you *want* it to be started, via either the "HTTP START" configuration file statement, or the "http start" command:

*


So in summary, the "HTTPPORT" statement is a Hercules 3.x statement, whereas the "HTTP PORT" statement is a Hercules 4.x statement, which requires a separate "http start" command (or configuration file statement).

Hope that helps!

I learn something new every day.

Indeed. The day I myself stop learning new things is the day I've died and gone to my grave. :)

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...