Forum Discussion

Misty_Spillers_'s avatar
Misty_Spillers_
Icon for Nimbostratus rankNimbostratus
Jul 01, 2014

PRTG web console and portal access

I have been publishing our PRTG web console for years with no issues through Firepass. I'm trying to do the same thing with APM and I'm not having much luck at all. I can get to the login page (and help page, change password page) or PRTG but once I try to login I get "Page not found". Its running on port 80, so no certificate issues.

 

One thing I do notice is that the login page URL is obfuscated (as well as help, change password page), but the page after that isn't. I don't know if that an issue.

 

Anyone have any pointers on how to trouble shoot this? It worked first try on Firepass, with no special settings.

 

Thank you very much!

 

Misty

 

3 Replies

  • By obfuscated I assume you mean as performed by the APM portal itself?

     /f5-w-encoded-value-here
    

    Yes? Can you do a client side capture with Fiddler or HTTPWatch (or really anything if you're not doing SSL)? There's a good chance that the portal is not rewriting a URL in the response, which could either be a configuration setting in the portal app's properties, or something unusual with the app itself (like the URLs being written in JavaScript on the client side - yes I've actually seen this).

  • We are doing ssl on the front side, but back end traffic is all port 80.

     

    And yes that is what I mean by obfuscated.

     

    I'm not sure what to look for in fiddler, after I try to login to PRTG is says:

     

    [Fiddler] ReadResponse() failed: The server did not return a response for this request (instead of the page not found on the PRTG browser)

     

    And nothing much in the packet trace, but as I said, I'm not sure what to look for.

     

    Maybe I'll grab a tcpdump between the LTM and the PRTG box and see if that reveals anything. I'm a little better with that.

     

    Thanks for your help. This is not my certainly not my first time with a web site that worked perfectly in Firepass but not APM

     

  • The problem should be visible in the Fiddler capture. You're looking for the following things:

     

    1. The HTTP response content. Are all of the (required) URLs in the HTTP headers and payload rewritten?

       

    2. The request that resulted in this error response. What was this URL? Assuming it wasn't obfuscated, where did the URL come from? Part of an HTML form? JavaScript? Internal redirect?