LupusE
6
The situation was another in the linked topic.
You don’t try to execute a compiled binary, you’re about to start a shellscript. But the solution could be the same in both questions → write ./ before the command.
The architecture (arm, mips, …) should play a lower role in a shell script, than in a binary.
As an alternative you can try bash [name_of_the_script].sh or ash [name_of_the_skript].sh …
But from your response, I’m not sure if the file will be available. Please check with ls ~/surfshark-wireguard, if the desired file is in the actual directory, before try to execute it.