Hi @Bidu. I’m the author of those videos and documentation. Glad to see that these are being used. Never did a PI install, so I really don’t know what is different in your setup.
Some of the pages are outdated and need an overhaul. But the information submitted in those docs still are the best you can get at the moment.
Now to your problem. The error shows “unexpected”, this looks like some type of syntax problem whithin the .run file. What I can also see from one your screenhots above, is a very strange wrong encoding file at /home/cfuser just above the .run file. That file clearly doesn’t appear in the videos and I’ve not seen it in any of my tests before.
Related to your error I’ve found this post at SO. it makes the .run files executable by command line. Maybe that is the issue you are having. I’d give it a try:
I also have another question: Is there any specific reason you want to install those on a raspberrypi for learning? I’d use a VM for this. I’ve created those videos with a Oracle VM VirtualBox and they are great for such learning purposes. You can easily clone virtual machines as a backup, so you can test and play however you want it. And: You can also easily bridge the VM IP address within virtualbox, so you can even access or browse that VM Server from another machine of your home network.
Good morning @andreas ,
Thanks for your videos they taught me a lot
I am setting up the server on the raspberrypi for two reasons:
1 - I will leave an application running locally, with a job every 1 hour
2 - This application accesses a specific website and makes a cfhhtp of some data, however this website is protected by “cloudflare” and all my attempts to make a cfhttp from an AWS server are blocked, now leaving my local ip no have problem = /
I tried to perform the procedure to execute, the .run but says that it is not a binary
My suggestion is joining a Raspberry PI support group, as ELF binary support on the ARM system is the issue.
You would in essence download everything to run raspberry pi on a Linux OS computer
you would then recompile the support for your custom raspberry pi instance
then export the binary startup and re-flash the hardware with your own custom image.