Jeremy Davis's picture


Your hashcash string is not valid.




Liraz Siri's picture



For now I've disabled Hashcash.

Jeremy Davis's picture





Liraz Siri's picture

Jiger's picture

Hi mate,




Can somebody take care of this at the earliest, Thanks.




Jeremy Davis's picture

But with perseverence it usually works...


Jeremy Davis's picture



Disorganise's picture

Don't know if this will post...



Jeremy Davis's picture


Disorganise's picture

thanks heaps :)

kaktux's picture




Jeremy Davis's picture


nextidturnkeyforums_1116919's picture

This is currently a problem with Firefox 70.

I'm trying to post this about the PostgreSQL image, BTW:

* * *

First: I can't create issues on the github repo for the PostgreSQL appliance.

Second: it hung for a while on first boot. Error message:

[  802.762617] inithooks[336]: Traceback (most recent call last):
[  802.784061] inithooks[336]:   File "/usr/lib/inithooks/firstboot.d/25ec2-userdata", line 40, in <module>
[  802.791844] inithooks[336]:     main()
[  802.802152] inithooks[336]:   File "/usr/lib/inithooks/firstboot.d/25ec2-userdata", line 28, in main
[  802.818551] inithooks[336]:     userdata = ec2metadata.get('user-data')
[  802.828055] inithooks[336]:   File "/usr/lib/python2.7/dist-packages/ec2metadata/", line 85, in get
[  802.838756] inithooks[336]:     m = EC2Metadata()
[  802.852056] inithooks[336]:   File "/usr/lib/python2.7/dist-packages/ec2metadata/", line 32, in __init__
[  802.871975] inithooks[336]:     raise Error("could not establish connection to: %s" % self.addr)
[  802.893493] inithooks[336]: ec2metadata.Error: could not establish connection to:


Jeremy Davis's picture

I'm not sure how or why, but this post slipped past me.

Re the hashcash issue, I'm still not clear on what the cause of that is, nor why it seems to affect some users consistently, but not others. Generally, the way that it seems to be best avoided by most users is to create a user account, let me know (email jeremy AT and I can disable the spam traps for your account. Unfortunately, even that doesn't appear to be foolproof as one user has stated that he still occasionally has issues posting, but it seems to be an improvement. When I have my backlog under control, I'll try to put a bit more time and attention into this issue and see if we can improve it without opening the spammer floodgates...

Regarding reporting your issue, we disable issues for the individual repos on purpose as we have a consolidated issue tracker. The reason why we do that, is that because our appliances have such a large footprint of common code, often issues that occur on a specific appliance may actually affect multiple appliances.

With regard to the specific issue you are reporting here, I assume that this is an AWS server? (Only AWS servers should be running the ec2-metadata firstboot script). The IP address should be bonded to all AWS instances and is where the instance metadata is stored and accessible. The error you note suggests that for some reason the metadata service was not available when the appliance was trying to start up. In my experience, that is generally an intermittent AWS infrastructure issue. AFAIK it should only occur on firstboot (at least that's the only time I've hit it, and only a few times in the last ~10 years). Assuming that it's on firstboot, generally just starting a new server will resolve it. If that doesn't do it, try launching a new server in a different availability zone (and/or region if appropriate to your use case).

If the scenario where you're hitting this issue doesn't match what I've posted, please provide additional info and context and I'll try again...

Add new comment