Trouble running local WordPress in Google App Engine

  • OC2PS

    (@sooskriszta)


    11 years ago

    Following these instructions: https://developers.google.com/appengine/articles/wordpress

    Installed MySQL, Python and Google App Engine PHP SDK on a Windows 8 PC. Perfect!

    Created an app for WordPress, created database and user on localhost and edited WordPress config accordingly.

    Started the app in the Google App Engine Launcher. Clicking Browse leads to blank page at https://localhost:8080/

    Hmmm…

    Checked logs, found

    2013-11-26 17:56:18 Running command: "['C:\\Python27\\python.exe',
'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py',
'--skip_sdk_update_check=yes', '--port=8080', '--admin_port=8000',
'C:\\Users\\CsillamVilag\\Documents\\development-appengine\\arcfestesmintak']"
INFO     2013-11-26 17:56:19,805 devappserver2.py:660]
Skipping SDK update check.
WARNING  2013-11-26 17:56:19,813 api_server.py:331]
Could not initialize images API; you are likely missing the Python "PIL" module.
INFO     2013-11-26 17:56:19,822 api_server.py:138]
Starting API server at: https://localhost:53853
INFO     2013-11-26 17:56:19,826 dispatcher.py:171]
Starting module "default" running at: https://localhost:8080
INFO     2013-11-26 17:56:19,828 admin_server.py:117]
Starting admin server at: https://localhost:8000
INFO     2013-11-26 17:56:21,828 module.py:617] default: "GET / HTTP/1.1" 302 -

    Pretty certain the Python for Windows package I used included PIL. Besides, that “shouldn’t” matter.

    Even more troublingly, the last line of the log output is a HTTP redirect from / to another page…the output appears to have been interrupted.

    Not sure where to go from here…

Viewing 11 replies - 16 through 26 (of 26 total)

  • Ooops..I see I was supposed to install the plugins LOCALLY first. I didnt do that. Will do that later today and re-deploy.

    Okay, I “think” I am up and running. But just went to change my permlinks structure and it says I can’t write to my .htaccess file. How do I access that?

    On a sidee note: do they (google appspot.com) expect us to do all of our configurations locally and then upload? If so how would the database stuff get transferred? Anyway, that would be ridiculous if i\we have to do everything locally and then upload.

    I guess my answer for the above question is how do we obtain ftp access to our site?

    @venturavan: your .htaccess file, when it’s present, is most often at the root of your WP installation; e.g. “htdocs\wordpress\” under most localhosts settings. If you have the standard WP installation though, you seldom have to change the admin user’s, in this case you and the WordPress application, permissions for the file when building a basic website.

    I would recommend searching the web or starting a new thread to troubleshoot the issue.

    Yes, GAE is only for production and so all development, including installing plugins, themes and making modifications that would require FTP. You can update WP versions and plugins though once installed. In short, GAE does not yet support FTP as far as I know.

    Hope this helps.

    @catalyx: So what you are saying is I have to do any changes that affect .htaccess LOCALLY and then Deploy? Seems VERY unreasonable to me, not to mention fraught with danger (possibility of post deploy (production) not liking changes I made locally)

    @venturavan: I am at the same point you were above. Everything works great locally and I can deploy without any errors. However when I try to access the site via App Engine, I get “Error Establishing a Database Connection”. What did you mean above when you said:

    I had my hostname as the xxx.appspot.com instead of localhost. When I changed it to localhost it worked.

    Any additional info is greatly appreciated.

    Thread Starter OC2PS

    (@sooskriszta)

    @oc2ps: in the Google Cloud service account, I believe you can select where to have your preferred geographic presence for the site.

    I wish it were that simple. It’s not. If you are outside the US, you can’t choose the location of your app in a free account. You need to apply for a Premium account (which I did 10 days ago). And then you need to wait (as I am still) for them to convert your account.

    I downgraded WP to v.3.5.1; the GAE-WP instructions state this is the version used while you have v3.7.1, per your query here.

    https://groups.google.com/forum/#!searchin/google-appengine/App$20Engine$20doesn$27t$20work$20with$20latest$20version$20of$20WordPress$3F/google-appengine/i-Bu3cMVgFE/XBltoBDA5ewJ
    Thank you for bring this issue to our attention. The bug surfaces due to a change in WordPress 3.7 and affects only the development server. It should be fixed in the next release. Meanwhile, please manually change line 109 -110 of <google_appengine root>/google/appengine/tools/devappserver2/php/runtime.py from

    user_environ[‘REAL_SCRIPT_FILENAME’] = environ[ http_runtime_constants.SCRIPT_HEADER]

    to

    user_environ[‘REAL_SCRIPT_FILENAME’] = os.path.normpath( os.path.join(self.config.application_root, environ[http_runtime_constants.SCRIPT_HEADER]))

    As this is a Python script, make sure the new statement is indented correctly.

    I have followed the instructions on this page to the ‘T’
    https://developers.google.com/appengine/articles/wordpress

    The everything seems to be working fine locally but it’s not working in production.

    After deployment when I try accessing buzzingbubsindia.appspot.com it redirects to https://buzzingbubsindia.appspot.com/wordpress/wp-admin/install.php where I get a ‘too many redirects’ error message.

    Has anyone else faced this issue?

    @buzzingbubs

    I’m having the exact problem as you.
    WP works locally but after deployment, it fails over there and go on redirect loop.

    I asked at the Stackoverflow forum and still got no response.

    Anyone got the same thing?
    I’m using the latest WP 3.9

    Hi guys
    I have exact problem as you.
    I have some error message on my https://womensportsbra.myprlblogs.info
    need help

    The main tutorial is really outdated and hasn’t worked in months. You guys should check out the WordPress App Engine Starter Project on Github. It is maintained by Googlers and they seem to update it fairly frequently and respond to issues/pull requests (albeit slowly). On Windows I had to move the files in step one of the readme manually but I was able to get it running both locally and on App Engine successfully following the provided instructions.

    That being said there are a few problems with running WordPress on app angine that I have encountered and can’t seem to fix. For example, if you want to use a custom domain, SSL is required to login to the WordPress Admin by the App Engine WP plugin. A workaround is to only edit your site via the (app_id).appspot.com domain that is provided by App Engine because it has SSL enabled. Another problem I have encountered is certain plugins like Jetpack, seem to not work with custom domains correctly even when set in the admin. Jetpack confuses the provided domain (app_id).appspot.com domain with my custom domain. I have not tried it with very many plugins but something is definitely not working correctly. It also seems like WordPress SEO by Yoast has similar problems.

    I have been messing around with settings for months now trying to get them perfect to no avail. Performance is not the problem. WP runs ridiculously fast if you set up Warm up requests in app.yaml, tweak the Perfomance section of the App Engine Console “Application Settings” page, and enable Pagespeed service.

    The problem is its simply not practical to run WP on it until plugins work how they should and custom domains don’t cause problems. Its definitely not ready for big production WordPress installs at this time.

    Personally, I made the switch to AWS’s Elastic Beanstalk until Google works out the kinks. It has similar speeds, similar price and none of the weird problems.

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘Trouble running local WordPress in Google App Engine’ is closed to new replies.