Closed Mehran closed 7 years ago
same here, before it was working well, after last update and build i see same issue while running the server, nothing shown running in UI, and these error on CLI.
Warning: You have 0 query credits. @ Saving session to site-xray-session.json @ Web UI running on http://0.0.0.0:8080/
0.02 % completed, 2.10 req/s, 3 unique targets found so far ... 0.05 % completed, 2.95 req/s, 5 unique targets found so far ... 0.07 % completed, 2.87 req/s, 6 unique targets found so far ... 0.09 % completed, 2.82 req/s, 8 unique targets found so far ... 0.11 % completed, 2.84 req/s, 8 unique targets found so far ... 0.13 % completed, 2.82 req/s, 11 unique targets found so far ... 0.16 % completed, 3.03 req/s, 11 unique targets found so far ... http: panic serving x.x.x.x.x:36082: [map]: [optional]: [xray.Target]: [optional]: [xray.Context]: [optional]: [xray.Machine]: unsupported type: chan interface {} goroutine 786 [running]: net/http.(conn).serve.func1(0xc4204f2460) /usr/local/go/src/net/http/server.go:1721 +0xd0 panic(0xb50580, 0xc4202dfb50) /usr/local/go/src/runtime/panic.go:489 +0x2cf github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render.JSON.Render(0xb74e60, 0xc42039fc20, 0x7f8ec4b50e98, 0xc42026a4d0, 0xc42026a400, 0x7f8ec4b50e98) /go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render/json.go:35 +0x80 github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render.(JSON).Render(0xc4203af280, 0x7f8ec4b50e98, 0xc42026a4d0, 0x7f8ec4b50e98, 0xc42026a4d0)
I'm having the same issue here. The error messages are the same as @keleju reported (with unsupported type: chan interface {}
). I noticed this one is missing in error mesages @Mehran pasted.
Now, few more details that might help tracing the problem.
Same here, it throws an error everytime the javascript trys to request the http://127.0.0.1:8080/targets
page.
goroutine 2549 [running]:
net/http.(*conn).serve.func1(0xc420222aa0)
/usr/local/go/src/net/http/server.go:1721 +0xd0
panic(0xb50580, 0xc42030e9b0)
/usr/local/go/src/runtime/panic.go:489 +0x2cf
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render.JSON.Render(0xb74e60, 0xc4203d5800, 0x7f992f78be10, 0xc42009da20, 0xc42009da00, 0x7f992f78be10)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render/json.go:35 +0x80
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/render.(*JSON).Render(0xc42030e000, 0x7f992f78be10, 0xc42009da20, 0x7f992f78be10, 0xc42009da20)
<autogenerated>:10 +0x6a
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin.(*Context).Render(0xc42009da20, 0xc8, 0xf6f920, 0xc42030e000)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/context.go:598 +0x125
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin.(*Context).JSON(0xc42009da20, 0xc8, 0xb74e60, 0xc4203d5800)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/context.go:629 +0x8d
main.main.func1(0xc42009da20)
/go/src/github.com/evilsocket/xray/cmd/xray/main.go:154 +0x234
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin.(*Context).Next(0xc42009da20)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/context.go:110 +0x5a
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc42023a120, 0xc42009da20)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/gin.go:337 +0x62a
github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc42023a120, 0xf71520, 0xc42017d960, 0xc4200d0600)
/go/src/github.com/evilsocket/xray/vendor/github.com/gin-gonic/gin/gin.go:301 +0x16b
net/http.serverHandler.ServeHTTP(0xc42009cbb0, 0xf71520, 0xc42017d960, 0xc4200d0600)
/usr/local/go/src/net/http/server.go:2568 +0x92
net/http.(*conn).serve(0xc420222aa0, 0xf72120, 0xc42036dbc0)
/usr/local/go/src/net/http/server.go:1825 +0x612
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2668 +0x2ce```
The docker image seems to work well, however when I try to access the UI it doesn't get loaded. You can still grab the JSON file from the docker image with docker exec
.
As for the CLI, it gives the errors mentioned previously.
it seems every is okey but when i browse that ip address i see bad log and its empty . also i didn't have this issue on first Released .