为什么我无法让 Google Adwords API 在 Amazon EC2 实例上运行?
我似乎遇到了另一个 Amazon EC2 问题。对于我正在开发的这个应用程序,我需要使用 Google Adwords API 来检索一些域数据,但它不适用于我们的 Amazon EC2 实例。如果我把它放在我们的 BlueHost 服务器上,它就可以正常工作。但是,它不适用于 Amazon EC2。如果我尝试运行 Google Adwords,它只会显示空白屏幕,不会显示任何错误。
我已在我的 Amazon EC2 实例上安装了 SOAP。在我安装 SOAP 之前,它返回一个错误,指出未安装 SOAP。现在,即使我注释掉对从 Adwords API 提取数据的函数的调用,它也不会显示任何内容。
我什至添加:
error_reporting(E_ALL);
ini_set('display_errors',1);
到我的索引页面,以确保它会显示错误。还是什么都没有。
这是我正在使用的 AMI:
AMI-6AE81503
我确信有一些配置会阻止它正常工作,但我不确定是什么。有一段时间我想知道 SOAP 是否使用了一些我已禁用的特殊端口或协议,但它似乎只使用了已启用的端口 80。所以我不确定是什么原因导致了这个问题。
同样,我已经安装了 SOAP,并且 Apache 和 PHP 都使用最新版本。
提前感谢...
I'm having another Amazon EC2 issue, it seems. For this application I'm developing I need to use Google Adwords API to retrieve some domain data, but it isn't working on our Amazon EC2 Instance. If I put it on our BlueHost server, it works fine. However, it does not work on Amazon EC2. If I try running Google Adwords, it just shows a blank screen and doesn't show any errors.
I have installed SOAP on my Amazon EC2 instance. Before I installed SOAP, it returned an error saying that SOAP was not installed. Now it just shows nothing, even though if I comment out the call to the function that extracts data from Adwords API.
I even added:
error_reporting(E_ALL);
ini_set('display_errors',1);
To my index page in order to ensure that it will display errors. Still nothing.
This is the AMI I'm using:
AMI-6AE81503
I'm sure that there's some configuration which is preventing it from working right, but I'm not sure what. For a while I was wondering if SOAP used some special port or protocol which I've got disabled, but it seems to just use port 80, which is enabled. So I'm not sure what could be causing the issue.
Again, I have installed SOAP, and both Apache and PHP are using the latest version.
Thanks in advanced...
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
好吧,在花了一天的大部分时间在 Amazon EC2 上配置新实例(这次使用 Ubuntu 服务器)后,我终于让它工作了。只是那个AMI给我带来了麻烦,看来……
Well, after spending most of the day configuring a new instance on Amazon EC2 (this time with an Ubuntu server), I finally got it working. It was just that AMI that was giving me trouble, it seems...