You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing an issue where the HTTPS honeypot stops responding after approximately one hour of operation. This occurs whether it's running alone or alongside other honeypots. While the other honeypots (e.g., HTTP) continue to function normally, the HTTPS honeypot becomes unreachable both via browser and when curling the IP with port 443. From the logs, it appears that no adversary can reach the HTTPS honeypot either.
Steps to Reproduce:
Cloned the latest version of the repository as the pip3 install version is outdated.
Installed the project using pip3 install within the cloned directory.
Ran the honeypot according to the instructions: sudo -E python3 -m honeypots --setup https:443 --options capture_commands
Observations:
No errors related to HTTPS are shown in the logs.
The issue only seems to affect the HTTPS honeypot; other honeypots (like HTTP) remain active and accessible.
Does anyone have an idea what may have caused this?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hello,
I'm experiencing an issue where the HTTPS honeypot stops responding after approximately one hour of operation. This occurs whether it's running alone or alongside other honeypots. While the other honeypots (e.g., HTTP) continue to function normally, the HTTPS honeypot becomes unreachable both via browser and when curling the IP with port 443. From the logs, it appears that no adversary can reach the HTTPS honeypot either.
Steps to Reproduce:
sudo -E python3 -m honeypots --setup https:443 --options capture_commands
Observations:
No errors related to HTTPS are shown in the logs.
The issue only seems to affect the HTTPS honeypot; other honeypots (like HTTP) remain active and accessible.
Does anyone have an idea what may have caused this?
Thanks in advance!
The text was updated successfully, but these errors were encountered: