mitro-core 404 not found

[argonius]

hi

i have followed installation instruction on: https://github.com/mitro-co/mitro/tree/master/mitro-core
everything seems fine until i wanted to connect via browser to https://:8443/mitro-core/
i am getting a 404:
[21/Aug/2014:07:36:47 +0000] "GET /mitro-core/ HTTP/1.1" 404 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0

Error Page says:
HTTP ERROR: 404

Problem accessing /mitro-core/. Reason:

Not Found

Powered by Jetty://

i am not sure how to investigate this.

hope you can help me out.

thx, argonius

[evanj]

That looks like the server is working. If you go to https://localhost:8443/mitro-core/api/BuildMetadata you should get some plain text output about the build to verify that it is working.

Beyond that, you should be able to load the local debug extension and get it to connect to this server. This is super great by the way. If you want to write some "how to run a local server" documentation, I would greatly appreciate it.

[argonius]

i've tried to reach this url but still 404 :(

how to enable the debugging feature?
and yes, if it is up and running i will provide a guide for installing it on linux server system ;)

[evanj]

Hm. That must mean something isn't working right. I'll try to go through the build directions and see what must be happening, but on my machine when I run "ant server" in the mitro-core directory, it just works. There are no debugging flags to enable that (in fact, you can see it on the production server: https://www.mitro.co/mitro-core/api/BuildMetadata )

[vijayp]

I wonder if the host header is wrong. Can you try wget with http 1.0 and
see if that works?
On 22 Aug 2014 09:38, "Evan Jones" notifications@github.com wrote:

Hm. That must mean something isn't working right. I'll try to go through
the build directions and see what must be happening, but on my machine when
I run "ant server" in the mitro-core directory, it just works. There are no
debugging flags to enable that (in fact, you can see it on the production
server: https://www.mitro.co/mitro-core/api/BuildMetadata )

—
Reply to this email directly or view it on GitHub
#53 (comment).

[argonius]

how to force http 1.0 request with wget?

[vijayp]

I think it uses 1.0 by default. See what's logged...
On 22 Aug 2014 09:53, "argonius" notifications@github.com wrote:

how to force http 1.0 request with wget?

—
Reply to this email directly or view it on GitHub
#53 (comment).

[argonius]

no it uses 1.1 :/

[vijayp]

Try curl -0
On 22 Aug 2014 10:33, "argonius" notifications@github.com wrote:

no it uses 1.1 :/

—
Reply to this email directly or view it on GitHub
#53 (comment).

[argonius]

still the same problem:

<title>Error 404 </title>

HTTP ERROR: 404

Problem accessing /mitro-core/. Reason:

    Not Found

---

Powered by Jetty://

[vijayp]

You have to load the build metadata page
On 22 Aug 2014 10:47, "argonius" notifications@github.com wrote:

still the same problem:

Error 404

HTTP ERROR: 404

Problem accessing /mitro-core/. Reason:

Not Found

---

Powered by Jetty://

—
Reply to this email directly or view it on GitHub
#53 (comment).

[argonius]

sorry, now i get:

commit: a7e7827
describe: fatal: No names found, cannot describe anything.

[evanj]

Perfect! That sounds like success, and looks like I need to fix the build script to remove the "git describe" output. :)

So this means the server is running. You will also need to have a local postgres instance running, with a database called "mitro" that is accessible without a password on localhost. If you have that, your local server will probably work.

[argonius]

ok, great. but how to proceed? i think i have to create a user, so i can use the server from my firefox
plugin?

[evanj]

Right. If you build the local extension (make firefox-debug in the browser-ext/login directory), and load that, it will talk to the local server, and you can use the "sign up" flow to create a user like you normally would. You will need to visit the local server first, in order to get Firefox to trust the unsigned SSL certificate.

[kristofer]

so I ftp'd the release.xpi that I built for firefox from my server down to my machine. I added it to firefox from the Add-on page, (Add on from file...) and it get loaded without problems.

I browse to the front page on my mitro server and I get the 404 like above.

my buildmetadata page acts like normal.
When I click on the mitro icon in my tool bar on firefox, I get a pop-up panel, that is blank?

[evanj]

If you downloaded "release.xpi", that should be talking to the public mitro server. You want "debug.xpi" to talk to your local server.

I just tried it with an old version of Firefox (30), and it worked. If you are getting the blank panel, this could be related to the Firefox 32 bug that causes Mitro not to work on recent versions of the browser? You should definitely try using the debug version, since it has un-minified javascript, so you might actually be able to figure out what the error is.

[klochner]

As someone who never used mitro pre-acquisition, it would be helpful to know how the flow is expected to work. This doesn't function as a standalone web app?

I was able to boot the metadata page, so now what? Is there really no admin interface?

[evanj]

Admin interface? No. We didn't have any need for it. If you got the server
running, you should be able to load a debug extension and click "create
account", which will create an account on your localhost server.

Evan

On Mon, Oct 27, 2014 at 2:58 AM, kevin lochner notifications@github.com
wrote:

As someone who never used mitro pre-acquisition, it would be helpful to
know how the flow is expected to work. This doesn't function as a
standalone web app?

I was able to boot the metadata page, so now what? Is there really no
admin interface?

—
Reply to this email directly or view it on GitHub
#53 (comment).

Evan Jones
http://evanjones.ca/

[klochner]

Is the design doc comprised mostly of unfinished plans?

https://github.com/mitro-co/mitro/blob/master/PasswordManagerDesign.pdf?raw=true

"An organization’s administrators can access and edit anything that belongs to an organization (accounts/secure notes, and groups). This way they can see what services their organization is using, can access accounts if someone leaves, and can reset passwords."

[evanj]

Yeah, mostly. Much of the underlying infrastructure is there, and some of the UI was finished, but at this point we've disabled all of the organizations support because it was buggy and caused too many customer support issues.