You can create an account on this Gitlab server and ask questions in the Issues section of this project.
[since 28-march-2016] LoginFailure/no tracking (possibly number blocked).
There have been a lot of reports that last night numbers where blocked that were used in the Raspberry Pi image. This seems to be a clean-up on WhatsApp side trying to block "malicious" users with the WhatsApp update 2.0. Apparently instances on a VPS/Server are not affected as much.
Unfortunately updating does give a guarantee you won't be blocked again. The new WhatsApp version is currently being reverse engineered, which might take some time.
If you want to try now (no guarantees about being blocked!): Please update your WSP installation (Rpi users: bash /home/pi/whatsspy-public-startup, others check the update page). Updating might be already to late, since there is the possibility that your current number is permanently blocked. If you still want to use the PoC it's best to buy a new number and use that number to register a new WhatsApp account. For this you can re-use the getting started. Make sure that you update BEFORE retrieving the secret for a new number.
I'm new to WhatsSpy Public, is it OK to setup now?
If you are certain that the number and secret are correct there might be another issue. You can debug via the following way:
If this did not work set debug = true (in $whatsappAuth) in your config.php and create an issue on this gitlab server with the output.
Another problem can be the fact that you have no internet connection, to check this execute ping google.com and check if there are responses.
If you ran a long successful session and got this error you might have a temporary WA ban. Try to switch to an secondary WA account or stop the tracker for a day.
Summary of requirements for this to work:
Working internet connection (no proxy etc.) over port 443 (HTTPS).
Phonenumber is not blockend
Phonenumber must be supplied correctly in the config.php (no zero's in front of countrycode and local phonenumber)
Secret must be supplied (including the last =).
PHP Warning: file_put_contents ... Permission Denied error while starting tracker
Make sure the files have the correct permissions. Follow this step again and make sure to start the tracker with sudo -u www-data php tracker.php
Raspberry pi image: Call to undefined function mcrypt_create_iv()
Execute: sudo apt-get update && sudo apt-get install php5-mcrypt and restart the tracker.
If that doesn't work:
Edit your php.ini for CLI and add (nano /etc/php5/cli/php.ini)
Raspberry pi image: Couldn´t resolve host gitlab.maikel.pro
Wait for the Raspberry Pi to have an internet connection, this may take a while on some networks. You can test if your internet is working by executing ping google.com.
Tracker says "An error occured, please check your configuration."
Problems while setting it up
Check if http://<ipaddress>/whatsspy/api/?whatsspy=getStats gives a blank page.
Check the error logs at /var/log/nginx/error.log if you use Nginx. Apache would be roughly the same.
You might have one of the following problems:
PDO might be not installed in your PHP (make sure you edit the php.ini for both the CGI and CLI).
Make sure you have the newest PHP (5.4+)
Your configuration might be wrong: Does the PostgreSQL username and password actually work? Does the user have rights to acces the tables? etc.
Make sure Nginx runs (instead of something like Apache, use sudo service apache stop && sudo service nginx restart to be sure)
Try running in case you get any PDO errors: sudo apt-get install nginx php5-pgsql postgresql php5-curl php5-cli php5
If the network is unreliable or the hardware very busy this might occur. Make sure you track on a device that is not under full load and the network has not too much switches etc. in between.
PHP Parse error: syntax error, unexpected '[' ...
Make sure you have the newest PHP (5.4+).
Error: Tree length did not match received length
This is a problem occuring at WhatsApp and there is no way to fix this. This problem will resolve itself within a day. Make sure you keep the tracker offline for a few hours so you don't spam login requests.
I don't have any notification options
You need to enable notification options in your config.php. After filling these options in you need to restart the tracker.
I have started the tracker but the UI shows "tracker offline"
The UI comminucates with the tracker via PostgreSQL. If this problem occurs it means there is something going wrong with PostgreSQL:
Check if all the tables exist in the correct database whatsspy.
Make sure the connecting database user has rights to read/write/delete in any of these tables.
Make sure the PDO is working.
Make sure you understand the difference between schema and database. You need to use the database whatsspy and schema public.
To test any database issues try the following in the terminal:
psql -U postgres\connect whatsspySELECT * FROM accounts;
If the last command returns that there is no relation called accounts you have probably inserted the tables in the wrong database.
You can insert in the correct database by executing the following command:
cd <location of whatsspy>/api/psql -U postgres-d whatsspy -f whatsspy-db.sql
For these commands to work you need to have created the database whatsspy
Wrong timezone set
If the tracker reports incorrect online/offline activites there is probably a misconfiguration:
Check if the timezone in the config.php is set properly.
Error after update
Check what the URL api/?whatsspy=getStats gives you. It might say something like:
The following error occured when trying to upgrade DB:<something more specific here>
This will probably a DB right issue, which you need to fix for future updates. But you can manually update by using this command:
"It seems like WhatsSpy Public is not working correctly."
Error like this? Delete your browser cache (directly by using Ctrl+F5). If this doesnt help post an issue.
Error after database update
Some updates have a small database adjustment which can cause problems. Check if the api/?whatsspy=getStats yields any "The following error occured when trying to upgrade DB:" error. Usually the problem is that the whatsspy database user has no rights to alter the database table. You can do the following to adjust this:
psql -U postgres\connect whatsspyALTER TABLE accounts OWNER TO whatsspy;GRANT ALL ON TABLE accounts TO whatsspy;\q
Make sure in the future that all the tables belong to the user whatsspy (thus repeating these steps for all the tables).
If this does not fix the problem use:
chmod 777 -R /var/www/whatsspy/
(chmod 777 is generally not a good practice, but on your Rpi this should be no problem).
Whatsapp uses an HTTPS connection which is going outbound (example for eth0):
iptables -A OUTPUT -o eth0 -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT