Hello,

I tried your solution from this topic

https://helpdesk.paessler.com/en/support/solutions/articles/6793-how-to-make-prtg-accessible-by-providing-username-and-password-in-the-url

But it didn't work. When I use for example:

http://127.0.0.1/group.htm?id=0&tabid=1&username=foo&password=bar

Then it opens the login page and ignores my given username and password in the URL.

Thanks a lot, Tal


Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Did you make sure that the password is actually correct? Are there any special characters in your password? I use that authentication method all the time and it surely does work properly :)


Dec, 2016 - Permalink

Yes, I use the korrekt password and username. Both of dem have a "." In them and nothing special beside that. The only different thing that I do is to open 2 pages with a different id, because the info on the main page is too big, so I had to split the info and use 2 monitors to show it and avoid using the scrolling option.


Dec, 2016 - Permalink

Could you try the passhash (which you can obtain from the account) instead, using the passhash parameter?


Dec, 2016 - Permalink

Do you mean like this

http://servername:port/group.htm?id=2894&tabid=1&passhash=passhash

If yes then it didn't work as well.


Dec, 2016 - Permalink

Is your server available publicly so I could try with a designated user and password? You can post it here, I won't publish it.


Dec, 2016 - Permalink

Unfortunately the server is not for public use and is only internal for the company's employees reachable.


Dec, 2016 - Permalink

Bummer. What PRTG version are you actually using?


Dec, 2016 - Permalink

It's the 14. something, I'm not going to be at work until January 2017 so I can't give you the exact version.


Dec, 2016 - Permalink

Hm, maybe an update might work here - possibly a bug, given that it's at least 2y old :)


Dec, 2016 - Permalink