PHP built-in web server not working (php -S) #62
Description
When I use sudo proxychains nmap -sT -p443,80 -Pn 192.168.37.238
I get
sudo proxychains nmap -sT -p443,80 -Pn 192.168.37.238
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.15
Starting Nmap 7.92 ( https://nmap.org ) at 2022-04-06 14:13 EDT
[proxychains] Dynamic chain ... 127.0.0.1:1080 ... 192.168.37.238:443 <--socket error or timeout!
[proxychains] Dynamic chain ... 127.0.0.1:1080 ... 192.168.37.238:80 <--socket error or timeout!
Nmap scan report for 192.168.37.238
Host is up (0.0038s latency).
PORT STATE SERVICE
80/tcp closed http
443/tcp closed https (<--This is supposed to be **open**, it is an **open** port in my **VM**'s)
Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
/etc/proxychains:
dynamic_chain
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
# add proxy here ...
# meanwile
# defaults set to "tor"
socks5 127.0.0.1 1080
On the other window, I have this:
$ python neoreg.py -k pivotpassword -u http://192.168.37.238:8080/tunnel.php --cut-left 5528 --cut-right 23 --skip
+------------------------------------------------------------------------+
Log Level set to [ERROR]
Starting SOCKS5 server [127.0.0.1:1080]
Tunnel at:
http://192.168.37.238:8080/tunnel.php
+------------------------------------------------------------------------+
[CRITICAL] Bad KEY or non-neoreg server
[CRITICAL] Bad KEY or non-neoreg server