I can’t tell from your screenshot if what it sent was the full URL, but from the “payment required”, I believe the captcha check failed. Either the captcha expired or it didn’t send the full URL.
You may need to type your Whisperfish password and phone number in Notes and copy/paste them into Whisperfish to save time so that a re-captcha isn’t required.
Thanks. If it is time limited that may be it. I’ll set up to try and beat the clock!
Thanks @sunburnedpenguin and @rubdos I am Registered!
The key is speed as suggested by Benjamin. Don’t let the CAPTCHA expire. Have your SSL session ready in terminal to paste the Captcha URL from the moment it is available. Enter your Developer password and as soon as Whisperfish opens, enter your chosen password and then your phone number. (Having the password ready to paste certainly helps).
Providing the CAPTCHA hasn’t expired you’ll get a screen asking for a code and a text message from Signal with the code.
Fantastic. Thanks both.
Hi there i updates Whisperfish to the latest Version under 4.4.0.58.
it works fine but i cant tick on the notifications preview.
Under /home/.config/ there is a new folder be.rubdos/harbour-whisperfish/
the conf from from /home/.conf/harbour-whisperfish/harbour-whisperfish.conf wont take from the programm.
is there a workaround?
Can i safely delete the old .conf?
Thanks for reporting. There really seem to be old and new folders for configuration (at least).
Don’t do anything just yet, I’ll open a ticket about it and figure out what is what.
Hmm, that’s new to me. Do you mean that when you get a notification, that clicking it does not open Whisperfish?
I made a note about the time limit on the wiki! Thanks 
Ah right, I saw that change too. I filed a regression issue, thanks! It’s most probably the same as the double config files issue, and I’ve cooked up an untested fix.
Slightly OT: I read whisperfish was written in the go programming language. But how does that work? I can’t find the go program nor a golang package for sfos?
Thank you!
The current Whisperfish is written in Rust, but it was originally a port of the Go-written application indeed.
( Well, it was meant to be a rewrite in Rust in step one, but things evolved before what was actually achieved )
Oh ok I wonder how I could mix that up? But great, anyways, thanks for clarification!
Just a hint for those having trouble pasting it directly via terminal. I did the following:
~
For some reason just pasting it kept hanging my terminal. odd.
just to mention: i had issue to past the long link to ssh client
i did not work with easyssh from linux, it did not work with putty from windows
finally i did use winscp and there from execute menu item i was able to paste the whole captcha
other remark:
i did run android app to change some settings which cant be set from linux desktop (bad idea) → whisperfish lost the connection …
so i had to uninstall, clean everything .local, .cache etc.
and then reinstall
Yes, only one device can be the registered device. If you re-register, you lose the previous registration.
i am running whisperfish on gs290 aka vollaphone. 4.3.0.12
it crashes relatvely often after sending a message.
i did try to collect logs but seem to stupid for that cause >> whisperlog.txt does not work for me
screenshot do not work on that port …
so typing the last lines here:
anybody experiencing the same problems ?
trace:: harbour whisperfish::model::message Mark message 24 sent ‘true’
Segmentation fault (core dumped)
That’s a new one to me! Do you have any chance to run with gdb and find a back trace?
OT but handy: :x = :wq
(saves you a keystroke in Vim 
)
d: 2 } from “/home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2”
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Opening file (async) /home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Read file /home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2 with 478 bytes
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::protocol_store] Loading session for ProtocolAddress { name: “21684d9e-9ac9-490f-b264-b0d798887d9b”, device_id: 2 } from “/home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2”
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Opening file (async) /home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Read file /home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2 with 478 bytes
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Opening file (async) /home/defaultuser/.local/share/harbour-whisperfish/storage/identity/remote_21684d9e-9ac9-490f-b264-b0d798887d9b
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Read file /home/defaultuser/.local/share/harbour-whisperfish/storage/identity/remote_21684d9e-9ac9-490f-b264-b0d798887d9b with 33 bytes
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Opening file (async) /home/defaultuser/.local/share/harbour-whisperfish/storage/identity/remote_21684d9e-9ac9-490f-b264-b0d798887d9b
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Read file /home/defaultuser/.local/share/harbour-whisperfish/storage/identity/remote_21684d9e-9ac9-490f-b264-b0d798887d9b with 33 bytes
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::protocol_store] Storing session for ProtocolAddress { name: “21684d9e-9ac9-490f-b264-b0d798887d9b”, device_id: 2 } at “/home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2”
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::store::utils] Writing file (async) /home/defaultuser/.local/share/harbour-whisperfish/storage/sessions/21684d9e-9ac9-490f-b264-b0d798887d9b_2
[2022-04-03T04:56:57Z DEBUG libsignal_service_actix::push_service] HTTP request PUT https://chat.signal.org/v1/messages/21684d9e-9ac9-490f-b264-b0d798887d9b
[2022-04-03T04:56:57Z DEBUG libsignal_service_actix::push_service] AwcPushService::put response:
ClientResponse HTTP/1.1 200 OK
headers:
“date”: “Sun, 03 Apr 2022 04:56:57 GMT”
“connection”: “keep-alive”
“x-signal-timestamp”: “1648961817487”
“content-length”: “19”
“content-type”: “application/json”
[2022-04-03T04:56:57Z DEBUG libsignal_service_actix::push_service] PUT response: “{“needsSync”:false}”
[2022-04-03T04:56:57Z DEBUG libsignal_service::sender] message sent!
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::model::session] STUB: Mark sent called
[2022-04-03T04:56:57Z TRACE harbour_whisperfish::model::message] Mark message 32 sent ‘true’
Thread 1 “harbour-whisper” received signal SIGSEGV, Segmentation fault.
0x00000055557a90a4 in std::sync::mpsc::Sender::send ()
That’s so strange. You may want to check out the log censoring part on the wiki, although you’ve only dumped some UUIDs (which leaks your contacts a bit).
Either way, this needs to be debugged through gdb; logs are not enough any more. If you want this debugged, I think we’ll need to get in touch via Matrix or some other private, more interactive channel.
