You are not logged in.

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Irbis

Sage

  • "Irbis" is male
  • "Irbis" started this thread

Posts: 109

Date of registration: Jul 12th 2006

Location: Magdeburg

  • Send private message

1

Monday, February 15th 2010, 2:57pm

additional ports to be provided for access to ramp-up

Hi,

I'm a little in trouble here as I wanted to provide a reporting interface via web access using the nice web interface.

I'm only allowed to run the web server on port 80 which suits me well, I edited the httpd.conf accordingly to allow listen on 0.0.0.0:80. Locally this works, all the interface does play nicely ;)

As soon as I try from a remote station after logging in via admin/admin I get "Backend not "

It would be troublesome for me to have to open some mysterious port for the communication but when I check on network level I see that the web server is delivering this message together with an HTTP 200 result code - which would be ok! This is quite confusing. Does something in the application framework really distinguish between a local login and some remot request?

What did you folks do to remotely access a Palo Web which is not on the same network?


Thank,
Mario

Irbis

Sage

  • "Irbis" is male
  • "Irbis" started this thread

Posts: 109

Date of registration: Jul 12th 2006

Location: Magdeburg

  • Send private message

2

Tuesday, February 16th 2010, 12:58pm

RE: additional ports to be provided for access to ramp-up

Well, it "automagically" fixed iteself.

Wit Listen 0.0.0.0 8081 and Listen 0.0.0.0:80 and a reboot of the machine (it's a VM to be exact) it now works.

Thanks for those who considered my problem anyway,
Mario

Rate this thread