Instant Infrastructure
Jumpbox-Mantis-1.02: Mantis application http://host URL brings up Jumpbox https://host:3000 interfaceSubmitted by poushag on Thu, 02/07/2008 - 2:58pm.I am attempting to evaluate Mantis and this is my first time to use a Jumpbox as well. However, I cannot get to the Mantis application at all. Whether I enter the URL into the browser address box directly or click on the link from the Jumpbox admin interface the result is always the same - that the Jumpbox admin interface loads instead. Can anyone explain to me why this is happening and what I can do to correct it? Thanks. |
Search |
The other URLs didn't work.
Wow, that sucks. You never see anything BUT the admin pages no matter what URL you try? Go into the admin page and reboot it. Then try again if you haven't already. The setup process could potentially be interrupted by something but we haven't seen a persistent recurrence of this type of problem. Have you tried other JumpBoxes with any success?
Austin
I never see anything BUT the admin pages no matter what
Tried the reboot from the admin page and still no difference.
I have not tried any other JumpBoxes because I don't find that idea very helpful. Mostly because the Mantis product is what I need to try out but also because I think it would be more useful to look at the logs on the existing JumpBox. However, I am in a catch-22 situation: I can't get authorized to buy something that I cannot show my team leader and justify by the fact that it works. But the VM doesn't work and it appears I can't get an SSH session going so I can troubleshoot the JumpBox by looking at the logs unless I buy some kind of license.
If I am still unable to look at the logs tomorrow without laying out funds, then I will probably just have to discard the JumpBox and find a basic Linux appliance instead and install Mantis on it myself.
I never see anything BUT the admin pages no matter what
I wouldn't encourage you to buy it if you cant get it to work either. The whole point is that you can try it before you buy it, in fact you can use the basic app without ever paying for it.
What browser are you doing the setup in? And do you have any strange browser plugins installed? Maybe that would allow me to reproduce this issue. And yes, unfortunately this is difficult to debug since you don't have access to the JumpBox but there is no real other way of enabling SSH at this point.
I am sorry you are have such a frustrating experience and I assure you I tried on three different platforms today and we have never seen anything quite like this with Mantis or any other JumpBox.
Oh, actually, the IP address the JumpBox has is correct right? It is appropriate for your bridged network and doesn't begin with 169.* or anything?
I guess at this point the most likely scenario is that the JumpBox is not making it all the way through its setup process and disabling the setup redirect. But that only tends to happen once a long while and after the reunzip and resetup it works.
Austin
Perhaps the setup did hang the first time...
but I wasn't watching the whole time and didn't notice. So I am running the setup again. This time I have been watching and it stays quite a while with the status bar saying "Waiting on https://IP:3000/appsetup..."
After several minutes, it finally reported the configuration complete and the app login is finally working. Yay!
It would have been easier if it were possible to rerun the initial setup using https://IP:3000/inital_setup
but I tried just for kicks and it won't work again after the first time.
And does it matter which browser runs the initial setup? The first time I used FireFox-2.0.12 and today I used IE-7. Have other people gotten the setup to work using FF?
Perhaps the setup did hang the first time...
"And does it matter which browser runs the initial setup? The first time I used FireFox-2.0.12 and today I used IE-7. Have other people gotten the setup to work using FF?"
No, it should work on any browser. The two of the three mantis JumpBoxes I setup yesterday were all using Firefox 2.0.0.12 on Linux and it sets up right away. Most of my JumpBox interaction is through Firefox but we test the apps and JumpBox Admin pages across all reasonable browsers on Windows, Mac and Linux.
Do you have any strange plugins installed? Something that interferes with Javascript?
This setup process has been dramatically changed to be far less brittle in our upcoming platform version, but your suggestion of re-running the setup is a good idea and we will look into that.
Sorry this has been frustrating for you. I am glad it has worked out in the end. Thanks for letting me know what the problem was too. Enjoy your JumpBox.
Austin
Are you using IE?
Do you have another web browser available? Perhaps the initial redirect from the first time you accessed your JumpBox has been cached by your web browser. This would seem more likely than anything at the JumpBox level. The JumpBoxes get tested internally on several virtualization platforms so something like this isn't likely to happen. In fact, I have just verified that the mantis-1.0.2.zip works fine on Parallels Workstation 3.0 on Mac, VMWare Workstation 6.0 on Linux and VMWare server 1.0.3.
What happens is any initial request to an unsetup JumpBox gets redirected to https://IP:3000/ so you are forced to do the setup. I think I recall someone experiencing something like this before but I can't recall seeing it myself (even when testing with other browsers).
Try typing in the two following URLs:
http://IP/index.php
http://IP/mantis
Austin
The other URLs didn't work - same result as before
I had tried different browsers the very first time I had this problem and the problem was the same in both.
Is it possible that the system thinks some part of the setup is not complete? How could I check this? Can you point me to a log file or something?
Thanks,
Andrew
Can this issue be duplicated?
Looks like it’s not a corruption issue.
The VM is running under VMWare-Server-1.0.4 (latest version) and the host OS is Windows-Server-2003-Enterprise-x64-SP2. The network connection is bridged.
When the cursor is hovering over the Mantis login hotlink I can see that the URL it directs to is http://IP/jblogin.php. But after clicking, the resulting URL is always https://IP:3000/ instead. Can you please explain what the correct behavior is supposed to be?
And could anyone at Jumpbox perhaps test the VM at your location and try to duplicate this issue?
Try setup again
Hi,
Try removing that JumpBox, unzipping a new one, and going through the setup process again.
Austin