-
Notifications
You must be signed in to change notification settings - Fork 1.2k
按照教程每一步都成功了,就是客户端连接不上? #62
Comments
谢谢,这个我一下就部署成功了,可能是我不会用TRAVIS CI,折腾了一下。 |
@onplus 2018-08-14T12:53:08.217069+00:00 app[web.1]: [GIN] 2018/08/14 - 12:53:08 |�[97;42m 200 �[0m| 603.806µs | 39.188.134.195 |�[97;44m �[0m GET / 2018-08-14T12:53:09.431848+00:00 heroku[router]: at=info method=GET path="/" host=rowanus.herokuapp.com request_id=5cb40082-74a0-4ec5-9b6c-0428b7309832 fwd="39.188.134.195" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=http 2018-08-14T12:53:09.428196+00:00 app[web.1]: [GIN] 2018/08/14 - 12:53:09 |�[97;42m 200 �[0m| 644.834µs | 39.188.134.195 |�[97;44m �[0m GET / 2018-08-14T12:54:50.062105+00:00 heroku[web.1]: Restarting 2018-08-14T12:54:50.062668+00:00 heroku[web.1]: State changed from up to starting 2018-08-14T12:54:50.728479+00:00 heroku[web.1]: Stopping all processes with SIGTERM 2018-08-14T12:54:50.799287+00:00 heroku[web.1]: Process exited with status 143 2018-08-14T12:54:50.919757+00:00 heroku[web.1]: Starting process with command 2018-08-14T12:54:53.792102+00:00 app[web.1]: [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. 2018-08-14T12:54:53.792121+00:00 app[web.1]: - using env: export GIN_MODE=release 2018-08-14T12:54:53.792123+00:00 app[web.1]: - using code: gin.SetMode(gin.ReleaseMode) 2018-08-14T12:54:53.792125+00:00 app[web.1]: 2018-08-14T12:54:53.792206+00:00 app[web.1]: [GIN-debug] GET /static/*filepath --> github.com/heroku/go-getting-started/vendor/github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (2 handlers) 2018-08-14T12:54:53.792213+00:00 app[web.1]: [GIN-debug] HEAD /static/*filepath --> github.com/heroku/go-getting-started/vendor/github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (2 handlers) 2018-08-14T12:54:53.792215+00:00 app[web.1]: [GIN-debug] GET / --> main.main.func1 (2 handlers) 2018-08-14T12:54:53.792219+00:00 app[web.1]: [GIN-debug] Listening and serving HTTP on :17068 2018-08-14T12:54:55.472448+00:00 heroku[web.1]: State changed from starting to up |
同 Process exited with status 143 和上面的日志除了时间都一样... |
也是,连不上,安卓和路由器都不能用。我改的版本是3.35. |
我的配置完是这样的 |
按照教程,每一步都成功。
查看HerokuAPP并重启一次(More-->restart),从more-->view logs确认启动成功:
当然UUID,端口和TLS这种是不会填错的,但客户端就是连不上。
服务器的log,我截取一部分,大神看看:
2018-08-06T14:16:51.935346+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=6ed0832d-44aa-4a5b-8e70-6f2ce38accdb fwd="14.30.21.40" dyno=web.1 connect=1ms service=3ms status=200 bytes=6960 protocol=https
2018-08-06T14:16:53.432339+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=18f6ae8e-db51-4ef5-9850-e6ec305f8869 fwd="117.14.159.12" dyno=web.1 connect=1ms service=2ms status=200 bytes=6979 protocol=https
2018-08-06T14:16:53.432253+00:00 app[web.1]: [GIN] 2018/08/06 - 14:16:53 |�[97;42m 200 �[0m| 758.29µs | 117.14.159.12 |�[97;44m �[0m GET /
2018-08-06T14:16:56.728238+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=f1a068a8-a00c-4cca-b55b-d7ca2ab2cd20 fwd="14.30.21.40" dyno=web.1 connect=1ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:16:56.728438+00:00 app[web.1]: [GIN] 2018/08/06 - 14:16:56 |�[97;42m 200 �[0m| 600.409µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:16:58.739695+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=ac0785d8-56cd-4004-a7ee-3ab9cd231de9 fwd="14.30.21.40" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:16:58.740005+00:00 app[web.1]: [GIN] 2018/08/06 - 14:16:58 |�[97;42m 200 �[0m| 852.606µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:00.275454+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:00 |�[97;42m 200 �[0m| 1.101513ms | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:00.276751+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=8f77132f-dcf7-4cbe-aa00-ad29a89461a0 fwd="14.30.21.40" dyno=web.1 connect=1ms service=3ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:03.247941+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:03 |�[97;42m 200 �[0m| 975.619µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:03.248218+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=3ab70586-ccdf-445e-8c73-4807d1c078c3 fwd="14.30.21.40" dyno=web.1 connect=1ms service=5ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:07.144532+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=791624b9-5528-4840-bad5-3f009b814b4f fwd="14.30.21.40" dyno=web.1 connect=1ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:07.146323+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:07 |�[97;42m 200 �[0m| 942.734µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:09.132909+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=77eab2c2-db84-49e1-b1d4-906f621ce54b fwd="14.30.21.40" dyno=web.1 connect=0ms service=3ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:09.131102+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:09 |�[97;42m 200 �[0m| 652.782µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:11.402158+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=a678e280-7e5c-441d-8614-47d2a9ccee59 fwd="14.30.21.40" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:11.400502+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:11 |�[97;42m 200 �[0m| 786.635µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:14.069868+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=0f408e1f-5e6f-4c76-95f9-8b1b7eb47dfa fwd="14.30.21.40" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:14.068917+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:14 |�[97;42m 200 �[0m| 1.20706ms | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:15.944892+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=ec4d4d4a-bc6a-4ede-85e1-18413dcb0986 fwd="14.30.21.40" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:15.945742+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:15 |�[97;42m 200 �[0m| 828.783µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:20.350337+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=6cfabc1f-d471-4dcc-b703-bd77568f23ee fwd="14.30.21.40" dyno=web.1 connect=0ms service=2ms status=200 bytes=6960 protocol=https
2018-08-06T14:17:20.351592+00:00 app[web.1]: [GIN] 2018/08/06 - 14:17:20 |�[97;42m 200 �[0m| 993.496µs | 14.30.21.40 |�[97;44m �[0m GET /
2018-08-06T14:17:21.585702+00:00 heroku[router]: at=info method=GET path="/" host=v2ray-heroku2.herokuapp.com request_id=b89d2a3c-61f7-4ecc-b908-2083e9276f9a fwd="14.30.21.40" dyno=web.1 connect=1ms service=9ms status=200 bytes=6960 protocol=https
The text was updated successfully, but these errors were encountered: