http://wordpress.org/support/ WordPress › Support Tag: amazon-machine-tags en Thu, 26 Nov 2009 09:23:27 +0000 http://wordpress.org/support/topic/225496#post-1263383 Thu, 29 Oct 2009 16:35:43 +0000 kliehm 1263383@http://wordpress.org/support/ <p>@olederer do you know what IP address your machine uses? </p> http://wordpress.org/support/topic/225496#post-1262629 Wed, 28 Oct 2009 22:47:31 +0000 olederer 1262629@http://wordpress.org/support/ <p>Hi I get this error on a normal web server, sure it's a shared host.</p> <p>is it possible to disable the test? I can't see any tags now </p> http://wordpress.org/support/topic/225496#post-1178246 Mon, 17 Aug 2009 22:06:06 +0000 kliehm 1178246@http://wordpress.org/support/ <p>@alastairmayer Well, I took the private IP ranges as defined by the HTTP spec. That wasn't for simplicity, but the most logical choice. By definition those IP addresses aren't unique or in a registry, so I wonder how Amazon could look those up and resolve them to your server?</p> <p>The affected files are the XSL files. This was a very common error until I implemented this message as people often test-installed the plugin locally where no access was possible for the Amazon API. The reason for this approach is that Amazon can transform the results; I thought that is more reliable and reproducable than relying on an XSL transformation on a users' server where the environment and processor is unknown. </p> http://wordpress.org/support/topic/225496#post-1174409 Fri, 14 Aug 2009 00:15:25 +0000 alastairmayer 1174409@http://wordpress.org/support/ <p>The problem here is the simple-minded function <code>test_status()</code> in <code>amtap.php</code>, which blindly assumes that private range IPs aren't accessible from the internet. This may be true for <code>localhost</code> (the function checks for IP's starting with 127), but it is <em>not necessarily</em> true for e.g. 10.x.x.x or 192.168.x.x IPs (which it also checks for), because they may be behind a NAT firewall (as mine is, for example). This is perfectly okay by internet standards.</p> <p>If you know PHP you can just bypass this test by hardcoding <code>$bIsLocal</code> to false, although that's a very quick and dirty solution. (More elegant might be to get the hostname and look up the public IP, but even that won't work if your web server is hosting virtual domains.)</p> <p>I made this change and have (apparently) no problem with accessing the AWS information. Of course it might help to know just what file Amazon wants to access so that we can check ourselves (via a browser or wget) if it's accessible. </p> http://wordpress.org/support/topic/225496#post-1086328 Fri, 29 May 2009 09:36:45 +0000 kliehm 1086328@http://wordpress.org/support/ <p>As I said, your server needs to be connected to the Internet on a domain so that Amazon can fetch the XSL file. If you run your own server at <code>localhost</code> that is not possible. In the meantime I changed the error messages so that they give a more detailed feedback on the cause of the error. Still you need to run the plugin on a real web server with an IP address and DNS entry connected to a domain. </p> http://wordpress.org/support/topic/225496#post-940669 Tue, 30 Dec 2008 23:01:34 +0000 ed4becky 940669@http://wordpress.org/support/ <p>I am not ssure what you men by MU. </p> <p>It is a single install on my own server sitting in my home. </p> http://wordpress.org/support/topic/225496#post-940266 Tue, 30 Dec 2008 14:59:38 +0000 kliehm 940266@http://wordpress.org/support/ <p>@ed4becky: you confused me with that mapping orgy... Anyway, does that mean you are using WordPress MU, or the single install of WordPress? Recently I tried to use my plugin on a MU site, and I had a similar error. However, there were none with ordinary WordPress installs. </p> http://wordpress.org/support/topic/225496#post-930427 Fri, 19 Dec 2008 01:48:08 +0000 ed4becky 930427@http://wordpress.org/support/ <p>I have the same error, but I believe I am on a public IP.</p> <p>ed4becky.dnsalias.org/jupiterthree is my dynamic site.</p> <p>I map ed4becky.org/jupiterthree to it and map jupiterthree.com to ed4becky.org/jupiterthree.</p> <p>I get a cannot fetch error like above.</p> <p>Suggested trouble shooting approach? </p> http://wordpress.org/support/topic/225496#post-925645 Mon, 15 Dec 2008 08:59:46 +0000 kliehm 925645@http://wordpress.org/support/ <p>I'm sorry you're having trouble getting started. Indeed your question is not in the FAQ (yet), but there is detailed information about this on the plugin homepage.</p> <p>The error message means you are running the blog on something like <code>localhost</code>. AWS needs to get an XML file from your server, obviously that is impossible when it's not located on a server that can be accessed with a public IP address from the outside. </p> http://wordpress.org/support/topic/225496#post-925160 Sun, 14 Dec 2008 21:46:32 +0000 Messire Loup 925160@http://wordpress.org/support/ <p>Getting this error:<br /> Your server is located in a private IP address space. Amazon Web Services cannot fetch the file that is required to validate the access key.</p> <p>Could not find the slightest hint about how to even start resolving the problem...</p> <p>This plugin still needs work </p> http://wordpress.org/support/topic/153418#post-685995 Fri, 01 Feb 2008 14:55:27 +0000 kliehm 685995@http://wordpress.org/support/ <p>Hi Shageman,</p> <p>sorry for the late reply, I didn't monitor this page. Why didn't you post on the plugin's page? Anyway, I think I fixed the problem, but I can't test it because I have no idea which widget you are referring to. Could you please provide a link?</p> <p>Thanks, Martin </p> http://wordpress.org/support/topic/153418#post-681842 Thu, 24 Jan 2008 16:05:00 +0000 shageman 681842@http://wordpress.org/support/ <p>Tried to use this plugin in the sidebar. Doesn't work if you put the &lt;?php AMTAP::get_items(); ?&gt; after the "Latest posts" widget. After this widget the current post ID is set to the ID of the last entry of that list.</p> <p><a href="http://wordpress.org/extend/plugins/amazon-machine-tags/" rel="nofollow">http://wordpress.org/extend/plugins/amazon-machine-tags/</a> </p> http://wordpress.org/support/topic/150495#post-672729 Mon, 07 Jan 2008 23:10:45 +0000 kliehm 672729@http://wordpress.org/support/ <p>It still worked in posts and in the sidebar, alas there was a bug that prevented the display of items on the home page. That is fixed in version 1.1.0 now. </p> http://wordpress.org/support/topic/150495#post-671761 Sat, 05 Jan 2008 22:38:37 +0000 minstrel 671761@http://wordpress.org/support/ <p>I was using Amazon Machine Tags version 1.04 which was working well on WordPress version 2.32.</p> <p>When I saw the notice on my ACP plug-ins page, I upgraded to 1.06. The plug-in no longer worked - no jacket image, no link, nothing - everything just vanished.</p> <p>I re-uploaded Amazon Machine Tags version 1.04 (I've gotten into the habit of saving previous working versions for Wordpress and vBulletin plug-ins) to my server and everything works again.</p> <p>Nothing else has changed on my blog.</p> <p>I conclude that there's an error in your upgrade. </p>