2016-03-19 143 views
2

我很久没有使用Heroku,所以即使有点生疏。 我创建了一个运行棘轮IOServer的小型PHP应用程序。它监听端口5000.如果我运行heroku local并连接telnet localhost 5000一切似乎工作。我尝试了几种让PHP进程运行并接受连接的方法。Websocket在本地工作,但不在Heroku上 - PHP应用程序

我的Procfile看起来像这样;

web: php bin/console bot:start 

运行heroku local

Downloading forego-0.16.1 to /Users/roje/.heroku... done 
forego | starting web.1 on port 8080 
web.1 | It works! 
web.1 | New connection! (97) 
web.1 | Connection 97 sending message "sdfdfs" 

当我再部署服务器的Heroku这是行不通的。 当我尝试远程登录到盒子上的端口5000我得到

telnet myapplication.herokuapp.com 5000 
Trying 46.137.127.234... 
telnet: connect to address 46.137.127.234: Connection refused 
telnet: Unable to connect to remote host 

日志显示更多的信息。

2016-03-19T16:08:27.258081+00:00 heroku[web.1]: State changed from crashed to starting 
2016-03-19T16:08:29.754688+00:00 heroku[web.1]: Starting process with command `php bin/console bot:start` 
2016-03-19T16:08:31.659074+00:00 app[web.1]: It works! 
2016-03-19T16:09:29.999903+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 
2016-03-19T16:09:29.999903+00:00 heroku[web.1]: Stopping process with SIGKILL 
2016-03-19T16:09:30.638659+00:00 heroku[web.1]: Process exited with status 137 
2016-03-19T16:09:30.660710+00:00 heroku[web.1]: State changed from starting to crashed 
2016-03-19T16:18:51.610894+00:00 heroku[web.1]: State changed from crashed to starting 
2016-03-19T16:18:55.208396+00:00 heroku[web.1]: Starting process with command `php bin/console bot:start` 
2016-03-19T16:18:56.648708+00:00 app[web.1]: It works! 
2016-03-19T16:19:55.569256+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 
2016-03-19T16:19:55.569256+00:00 heroku[web.1]: Stopping process with SIGKILL 
2016-03-19T16:19:56.252235+00:00 heroku[web.1]: Process exited with status 137 
2016-03-19T16:19:56.264205+00:00 heroku[web.1]: State changed from starting to crashed 

有什么建议吗?

编辑#1

我刚刚看了一下Heroku的一部分分配动态端口Heroku + node.js error (Web process failed to bind to $PORT within 60 seconds of launch)

我试过端口上侦听,而不是,但我仍然无法通过连接。远程登录。虽然我确实得到了一些有趣的日志。也许你们中的一些人正在尝试IP地址?

2016-03-19T16:38:35.577130+00:00 app[web.1]: It works! 
2016-03-19T16:38:35.827466+00:00 app[web.1]: New connection! (97) 
2016-03-19T16:38:35.827531+00:00 app[web.1]: Connection 97 has disconnected 
2016-03-19T16:38:35.832097+00:00 app[web.1]: New connection! (107) 
2016-03-19T16:38:35.832160+00:00 app[web.1]: Connection 107 has disconnected 
2016-03-19T16:38:49.891455+00:00 app[web.1]: New connection! (108) 
2016-03-19T16:38:49.891506+00:00 app[web.1]: Connection 108 has disconnected 
2016-03-19T16:40:54.694321+00:00 app[web.1]: New connection! (109) 
2016-03-19T16:40:54.694368+00:00 app[web.1]: Connection 109 has disconnected 

虽然我仍然得到相同的错误。

Trying 176.34.255.126... 
telnet: connect to address 176.34.255.126: Connection refused 
telnet: Unable to connect to remote host 
+0

我不相信Heroku可以让你从外部连接到80或443以外的任何东西。请参阅http://stackoverflow.com/questions/8107748/can-a-heroku-app-use-different-multiple-ports - 您的端口5000只在实例内,但Heroku的路由器不会在外部路由它。 – ceejayoz

+0

我试着在环境变量中由Heroku动态定义的端口上启动IOServer。在这种情况下,端口被分配为“40220”。仍然没有运气。 –

回答

-2

您是否检查过防火墙和端口?

+0

Heroku是一家平台即服务提供商。您无法访问防火墙和端口配置。 – ceejayoz

0

我能够使用nginx作为web套接字前的代理来管理这个。

Procfile:

web: private/bin/start_socket vendor/bin/heroku-php-nginx -C nginx_app.conf 

start_socket:

php private/bin/start_socket.php & 
exec "[email protected]" 

start_socket.php:

<?php 
require_once(dirname(dirname(__DIR__)) . '/vendor/autoload.php'); 
require_once(__DIR__ . '/socket/socket.php'); 

use Ratchet\Server\IoServer; 
use Ratchet\Http\HttpServer; 
use Ratchet\WebSocket\WsServer; 

$server = IoServer::factory(
    new HttpServer(
     new WsServer(
      new Socket() 
     ) 
    ), 
    8085 
); 
$server->run(); 

nginx.conf:

location /wss { 
    proxy_pass http://localhost:8085; 
    proxy_http_version 1.1; 
    proxy_set_header Upgrade $http_upgrade; 
    proxy_set_header Connection "upgrade"; 
} 

现在您可以像这样访问套接字:https://myapp.com/wss?mydata=test。这并没有解决每个dyno都会运行它自己独特的websocket服务器这一事实,但这是一个完全独立的问题。

相关问题