Hello,

Using Mozilla v35 with PRTG15.1.4 it takes at least 10 minutes time until PRTG will recognize JScript is enabled realy letting me use the ajax based Web GUI. If I check Mozillas JScript setting its everytime OK: about:config, search for javascript.enabled, is true allways

The reason I prefere mozilla for local web based tools is the easy way of changing proxy setting with this browser. Chrome and IE = system proxy settings are administrated by our local IT where I have no influence.

thx for hints in advance, Steffen

Article Comments

Hi,
could you please call the URL /speedtest.htm on your PRTG installation. What are the results?


Mar, 2015 - Permalink

Average Page Load Time: 183 ms, Slowest 307 ms, Fastest 94 ms (74 %)


Mar, 2015 - Permalink

Hi,
Thank you for the information. Are you actively using a Proxy when accessing PRTG? If so, could you perform a test with/without proxy? Does that make any difference?


Mar, 2015 - Permalink

Hi,

I feel my performance of the Web Frontend is also very bad, so I ran /speedtest as well:

Average Page Load Time: 1592 ms, Slowest 34587 ms, Fastest 45 ms (100 %)

Especially slow are 19, 20, 29, 18, 22, 17

Even if I run the speedtest locally on the Core Server I get this: Average Page Load Time: 1355 ms, Slowest 29044 ms, Fastest 27 ms (100 %)

Are there any particular things you can recommend by checking these particular slow results? Other than https://helpdesk.paessler.com/en/support/solutions/articles/76000041624-how-can-i-speed-up-prtgespecially-for-large-installations

We're currently using 8000 Sensors. 1 Core server with 5 remote probes.

Would it make huge difference if we move the sensors (900) from our Core Server to a seperate probe?

Kind Regards Lars


Mar, 2015 - Permalink

Hi,
in general more remote probes are better. :) So, yes every sensor distributed away from the core would be good in your case. You also can open up a support ticket to have us a look at the logs.
Best regards


Mar, 2015 - Permalink

Hello,

I was out of office couple of days. To clearify the problem again and to answer the questions in between:

1. Im very glad about the PRTG-GUI-performance after Im able to can login with Ajax Interface

2. The problem is about explicitly the more than 10 minutes it takes that PRTG checks Java Script is enabled using Mozilla as a prerequisite to can use the AJAX interface

3. with Mozilla and foxy-proxy-plugin I can call PRTG directly without a proxy because this is the only browser not mis-designed regarding proxy flexibility as none admin user. With a proxy configured browser the PRTG GUI does NOT work as long the proxy does not redirect to PRTG.

Steffen


Mar, 2015 - Permalink

Dear Steffen

Configuring a proxy for the PRTG webinterface is outside the scope of our technical support. Please try to use another browser and/or another proxy.

If you experience issues to get PRTG's webinterface working even when you access it directly (without proxy) please contact us again. You can also contact us directly via support@paessler.com


Mar, 2015 - Permalink

I use PRTG directly without a Proxy but strictly forced to must use Mozilla, because with all other browsers proxy = system setttings, without admin rights ...


Mar, 2015 - Permalink

Please forward a Support Bundle via the Contact Support ribbon in the lower right corner of the web interface. We need to have a look at your log files to see if there are any irregularities.

Best regards


Apr, 2015 - Permalink