Failed to connect to RPC server

[zoubida43]

Issue Description

Trying to re-connect to server after i was able to connect couple of days ago

Reproduction Steps

1. Start King Phisher
2. Do something to trigger the crash

Environment Details

Host OS: Kali
King Phisher Version: x.y.z

Error Details / Stack Trace

root@kingkali:/opt/king-phisher# lsof -i -P -n | grep LISTEN
postgres 757 postgres 3u IPv6 19616 0t0 TCP [::1]:5432 (LISTEN)
postgres 757 postgres 4u IPv4 19617 0t0 TCP 127.0.0.1:5432 (LISTEN)
sshd 1094 root 3u IPv4 23773 0t0 TCP *:22 (LISTEN)
sshd 1094 root 4u IPv6 23784 0t0 TCP *:22 (LISTEN)
python 1224 nobody 4u IPv4 26539 0t0 TCP 172.21.98.211:8081 (LISTEN)
python 1266 root 4u IPv4 26539 0t0 TCP 172.21.98.211:8081 (LISTEN)

DEBUG target directory: /opt/king-phisher
INFO checking for the pipenv environment
DEBUG pipenv path: '/usr/local/bin/pipenv'
DEBUG pipenv Pipfile: /opt/king-phisher/Pipfile
Loading .env environment variablesâ¦
DEBUG king phisher version: 1.16.0-beta (rev: 51185b4) python version: 3.7.5
DEBUG using plugin-specific library path: /var/king-phisher/lib/python3.7/site-packages
INFO listening on 172.21.98.211:8081
INFO serving files has been enabled
INFO initializing database connection with driver postgresql
DEBUG postgresql-setup was not found
DEBUG starting external process: /usr/bin/systemctl status postgresql.service
DEBUG postgresql service is already running via systemctl
DEBUG starting external process: su postgres -c psql -At -c "SELECT usename FROM pg_user"
DEBUG starting external process: su postgres -c psql -At -c "SELECT datname FROM pg_database"
DEBUG current database schema version: 9 (latest)
DEBUG connected to postgresql database: king_phisher
INFO restored 0 valid sessions and skipped 0 expired sessions from the database
DEBUG use pam service 'sshd' for authentication
DEBUG forked an authenticating process with pid: 1266
INFO the job manager has been started
INFO adding new job with id: 74febfc3-b065-4447-9f9d-d04535af4370 and callback function: _maintenance
INFO adding new job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG web socket manager worker running in tid: 0x7fbe99d11700
DEBUG initialized the table api dataset (schema version: 8)
DEBUG server request test id initialized with value: S5yzp6XYAcQnHg7iqLZ3br8o
INFO including 4 custom http headers
INFO server running in process: 1224 main tid: 0x7fbe9e1a0740
INFO dropped privileges to the nobody account (uid: 65534, gid: 65534)
DEBUG executing job with id: 74febfc3-b065-4447-9f9d-d04535af4370 and callback function: _maintenance
DEBUG running periodic maintenance tasks
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: ping_all
DEBUG executing job with id: 3ee2ffa7-9877-4597-bb15-9a51d4e49092 and callback function: pin

[zoubida43]

Thank you!

[zeroSteiner]

Well you're listening on port 8081 which is odd. Are you connecting to that port in the client?

[zoubida43]

Yes,

…

On Sun, Jan 26, 2020 at 11:20 PM Spencer McIntyre ***@***.***> wrote: Well you're listening on port 8081 which is odd. Are you connecting to that port in the client? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#424>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYXP3BDTYPVCWGCZLOBEVDQ7ZOKBANCNFSM4KL2XXGQ> .

-- Please be advised that under the _Public Records Law, _M.G.L. c.66, any email created or received by an employee of Wellesley Public Schools may be considered a public record and subject to public disclosure. This email may also contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies.__

[zeroSteiner]

Well you should double check that because that error message means the client can't connect to the server. Need to make sure the server is running and that you're connecting to the correct port that it's listening on.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.