404 Not Found

[fieu]

404 Not Found

[yudai]

Did you add :8080?

[fieu]

Yes.

[yudai]

Could you provide the URL you accessed?

[fieu]

Sure.

http://127.0.0.1:8080/6kbv8603

I was using --random-url

[yudai]

Cloud you try the latest pre-release? It has some changes in handling URLs that might solve your issue.

[fieu]

Sure. :)

[fieu]

@yudai How would I go about this? I'm on a Mac.

[yudai]

Try this one: https://github.com/yudai/gotty/releases/download/pre-release/darwin_amd64.tar.gz

[fieu]

Thank you.

[fieu]

Using the one you sent me: https://shel.io/f/aiUg.png

[yudai]

Could you try gotty --random-url --permit-write --addr 127.0.0.1 --port 8080 top?

It looks like there is another bug in parsing arguments

[fieu]

Error(s): https://shel.io/f/5ppd.png

[yudai]

Thanks for testing. I'll test on Mac and try to figure out what's happening soon. Give me some time.

[fieu]

No problem. I am here to test anything you need. :)

[yudai]

I could not reproduce your problem.
However, I added an error handling to the code around you got the error. Could you redownload the latest one from the same URL and try it? And I'd like to see what happens when you run gotty without sudo.

[nzyuzin]

I had just the same problem before I updated to current revision (from 94f571d to 56ae9ab).
It seems something in this range has fixed the issue.

@nurdturd you could try fetching latest changes to see if it's fixed for you too.

P.S. Problem disappears after 67b54b7.

[fieu]

Sure. I got this: https://shel.io/f/8BsP.png

[nzyuzin]

Same for me for the release binary.
Works fine with binary built with go get github.com/yudai/gotty though.

[yudai]

Found the root cause: http://stackoverflow.com/questions/20609415/cross-compiling-user-current-not-implemented-on-linux-amd64

[yudai]

Pushed the fix to the latest release. I hope it will work on your environment.

[fieu]

Thanks!

[fieu]

Using the new one, another 404 error. https://shel.io/f/MjMH.png

[yudai]

Hi, thank you for the report. Unfortunately, I cannot reproduce the issue you are experience.
Could you paste the full log? If your browser reaches the gotty server, gotty should output some GET lines like below:

./gotty -a 127.0.0.1 -r top
2015/08/24 12:22:15 Server is starting with command: top
2015/08/24 12:22:15 URL: http://127.0.0.1:8080/17qe10bp/
2015/08/24 12:22:33 GET /17qe10bp/
2015/08/24 12:22:33 GET /17qe10bp/hterm.js
2015/08/24 12:22:34 GET /17qe10bp/gotty.js
2015/08/24 12:22:34 GET /17qe10bp/ws
2015/08/24 12:22:34 New client connected: 127.0.0.1:55083
2015/08/24 12:22:34 Command is running for client 127.0.0.1:55083 with PID 45432
2015/08/24 12:22:47 GET /invalid_token/
2015/08/24 12:22:47 Command exited for: 127.0.0.1:55083
2015/08/24 12:22:47 Connection closed: 127.0.0.1:55083

In this case, the 404 error page was shown by accessing http://127.0.0.1:8080/invalid_token/ and that was logged as 2015/08/24 12:22:47 GET /invalid_token/ .

[yudai]

Closing as no activities last week. Please reopen if this issue still exists.