Closed kromenz closed 4 months ago
This seems to be an issue with your setup and not T-Pot. Review your routing, firewall settings, cloud provider settings, security groups, etc. Also, T-Pot is not supported on Debian 11.
Update: I've changed to Debian 12, spiderfoot is working, but still the same error in Kibana, i saw somewhere that i needed 8GB of RAM, well i have 16 now and the same HTTP 502 error occurs.
Another question is how am i supposed to test the honeypot? Should i just wait, or post the ip of it in some forum that i don't know about?
Thank you for your patience.
Successfully raise an issue
Before you post your issue make sure it has not been answered yet and provide ⚠️ BASIC SUPPORT INFORMATION (as requested below) if you come to the conclusion it is a new issue.
⚠️ Basic support information (commands are expected to run as
root
)We happily take the time to improve T-Pot and take care of things, but we need you to take the time to create an issue that provides us with all the information we need.
lsb_release -a
anduname -a
? bullseye~/install_tpot.log
, attach the log and highlight the errors.dps
)? active runningsystemctl status tpot
)? active runningHi, i am doing a University project where i have to setup my an honeypot in the cloud, and then get attacked. The goal is simple analyze the attacks, see the most used ones and that's it. But i've been encountering some errors in these past weeks, some i've resolved on my own, but others, like the one i'm about to explain i can't figure it out. Soo everything seems to be normal, the containers are running, but for some reason i can't open Kibana, neither Spiderfoot. In Kibana i get error 502: In Spiderfoot it doesn't even respond: Spidefoot isn't that revelevant, i would just be happy if i could get everything running.
To finish, i would also like to know how to get attacked, this is because i have to finish this project in 2 weeks and 1 week has passed an no attacks.
Thanks for your time!