interactsh-server starts without public ip
ehsandeep opened this issue · 0 comments
ehsandeep commented
Interactsh version:
v1.1.4 | dev
Current Behavior:
Server randomly starts without an assigned Public IP
, resulting into dns resolution error.
interactsh-server -dr -d oast.online
_ __ __ __
(_)___ / /____ _________ ______/ /______/ /_
/ / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
/ / / / / /_/ __/ / / /_/ / /__/ /_(__ ) / / /
/_/_/ /_/\__/\___/_/ \__,_/\___/\__/____/_/ /_/
projectdiscovery.io
[INF] Current interactsh version 1.1.2 (latest)
+ [INF] Public IP:
[INF] Outbound IP: 167.99.69.236
1.6811892541549845e+09 info maintenance started background certificate maintenance {"cache": "0xc0003260e0"}
[INF] Loading existing SSL Certificate for: [*.oast.online, oast.online]
[INF] Listening with the following services:
[SMTP] Listening on TCP 167.99.69.236:25
[LDAP] Listening on TCP 167.99.69.236:389
[DNS] Listening on UDP 167.99.69.236:53
[HTTPS] Listening on TCP 167.99.69.236:443
[SMTPS] Listening on TCP 167.99.69.236:587
[HTTP] Listening on TCP 167.99.69.236:80
[DNS] Listening on TCP 167.99.69.236:53
Expected Behavior:
A server should not start without Public IP.
Steps To Reproduce:
Slack (for internal team)
Note:
Investigate why the server is getting started without ip even when ip is available which is being set for Outbound IP and fix if possible and error handling to not start server without public ip.
This issues results into downtime of public interactsh server - https://status.projectdiscovery.io