Respond link single slash as well as bad ticket

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
potentiate
Posts: 2
Joined: Wed Aug 14, 2013 12:00 am

Respond link single slash as well as bad ticket

Post by potentiate »

Hi,

We have got an issue with our rapid response link in our email notifications, here is an example:

http:/172.16.1.158/nagiosxi/rr.php?uid=62--1-5b8569a2b3a676edd4fcf14e39a88cac

The issue showed up on Nagios xi 2014R1.1 but at least had a clickable link with http://, so we upgraded to 2014R1.2 hoping there would be a fix, however bad ticket is still showing after clicking the link and now it has a broken http:/ with a single slash. Has anybody came across such issue and has a resolution by any chance or place to start looking?

We are running on CentOS release 6.3 (Final) 64 bit. Manual install of XI. No special setup.

Thanks in advance !!!
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Respond link single slash as well as bad ticket

Post by lmiltchev »

This issue has been fixed. Please, read the following post (bottom of the page):

http://support.nagios.com/forum/viewtop ... 25#p103625
Be sure to check out our Knowledgebase for helpful articles and solutions!
potentiate
Posts: 2
Joined: Wed Aug 14, 2013 12:00 am

Re: Respond link single slash as well as bad ticket

Post by potentiate »

Oh I see! Sorry I missed that when searching for a solution earlier.

Awesome that fixes one of the issues, however we are still receiving "bad ticket" links which I cannot find a cause nor a solution. All i know is that the double "--" is to be blamed in the link? Do we know if this is a bug or issue with our setup?

Thanks!
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Respond link single slash as well as bad ticket

Post by lmiltchev »

To be honest with you - I am not sure. I've seen this only a couple of times, and we are not able to recreate the issue in house. It has to be something specific to your environment. If you had a email support, we could schedule a remote session, and try to troubleshoot the issue this way.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked