Unable to Login to KingPhisher. Not sure what has changed in the past week?

Issue Description

Unable to Login to KingPhisher. I rebooted my Kali Linux and launched ./KingPhisher. The client GUI popped up and I tried to login. Logs showed this.

EBUG 127.0.0.1 tid: 0x7f1ed37fe700 running http request handler DEBUG calling RPC method rpc_version() INFO 127.0.0.1 “RPC /version HTTP/1.1” 200 - DEBUG 127.0.0.1 tid: 0x7f1ed37fe700 running http request handler DEBUG sent request with sequence number 0 and action ‘authenticate’ DEBUG received request with sequence number 0 and action ‘authenticate’ DEBUG pam returned code: 0 reason: ‘Success’ for user root after 0.03 seconds DEBUG sent response with sequence number 0 DEBUG received response with sequence number 0 INFO user root has successfully authenticated INFO successful login request from 127.0.0.1 for user root

However, the client GUI showed Login Failed. Why the discrepancy? Then, I got this error below.

rror Type: advancedhttpserver.RPCError Error Details: RPCError(message=‘Unauthorized’, status=401, remote_exception=False) Error UID: 94c43c84-e7b0-46ec-902e-142f1cd813de RPC Error: N/A (Not a remote RPC error) King Phisher Version: 1.10.0 (rev: 63aaf4772ed9) Platform Version: Linux: Kali kali-rolling kali-rolling Python Version: 3.6.5 Gtk Version: 3.22.29 Timezone: America/Los_Angeles

Thread Information: => MainThread (alive=True daemon=False)

Stack Trace: Traceback (most recent call last): File “/opt/king-phisher/king_phisher/client/client_rpc.py”, line 421, in ping return self.call(‘ping’) File “/usr/local/lib/python3.6/dist-packages/advancedhttpserver.py”, line 601, in call raise RPCError(resp.reason, resp.status) advancedhttpserver.RPCError: the server responded with 401 ‘Unauthorized’

Reproduction Steps

1. Start King Phisher
2. Login fails via the client GUI.

Environment Details

Host OS: Kali2 2018.1 King Phisher Version: installed

Error Details / Stack Trace

If you are opening an issue regarding the client, copy text from the "Error
Details" of the error dialog in the client here. If you are opening an issue
regarding the server copy the relevant lines from the logs here.

[zeroSteiner]

Well since we open a port forward for the websocket it should never connect with a proxy, so this is really a bug. I’ll get a patch pushed up to dev tomorrow that will explicitly disable proxy support for the websocket and that will address the issue.

[chrisandjer949]

Let me know if I can provide any additional logs… strange, this was running fine for 2 weeks and then this happened. Weird.