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
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.
⚙️ The Troubleshoot Section of the T-Pot Readme is a good starting point to collect a good set of information for the issue and / or to fix things on your own.
⚠️ Provide BASIC SUPPORT INFORMATION or similar detailed information with regard to your issue or we will close the issue or convert it into a discussion without further interaction from the maintainers.
⚠️ 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.
What OS are you T-Pot running on?
What is the version of the OS lsb_release -a and uname -a?
What T-Pot version are you currently using (only T-Pot 24.04.x is currently supported)?
What architecture are you running on (i.e. hardware, cloud, VM, etc.)?
Review the ~/install_tpot.log, attach the log and highlight the errors.
How long has your installation been running?
If it is a fresh install consult the documentation first.
Most likely it is a port conflict or a remote dependency was unavailable.
Retry a fresh installation and only open the issue if the error keeps coming up and is not resolved using the documentation as described here.
Did you install upgrades, packages or use the update script?
Did you modify any scripts or configs? If yes, please attach the changes.
Please provide a screenshot of htop and docker stats.
How much free disk space is available (df -h)?
What is the current container status (dps)?
On Linux: What is the status of the T-Pot service (systemctl status tpot)?
What ports are being occupied? Stop T-Pot systemctl stop tpot and run grc netstat -tulpen
Stop T-Pot systemctl stop tpot
Run grc netstat -tulpen
Run T-Pot manually with docker compose -f ~/tpotce/docker-compose.yml up and check for errors
Stop execution with CTRL-C and docker compose -f ~/tpotce/docker-compose.yml down -v
If a single container shows as DOWN you can run docker logs <container-name> for the latest log entries
The text was updated successfully, but these errors were encountered:
Stazeymitch
changed the title
I NEED AND URGENT HELP Something went wrong with the Playbook, please review the output and / or install_tpot.log for clues.
I NEED AND URGENT HELP Something went wrong with the Playbook, I keep having an error trying to install tpot
Aug 18, 2024
Stazeymitch
changed the title
I NEED AND URGENT HELP Something went wrong with the Playbook, I keep having an error trying to install tpot
I NEED URGENT HELP Something went wrong with the Playbook, I keep having an error trying to install tpot
Aug 18, 2024
Stazeymitch
changed the title
I NEED URGENT HELP Something went wrong with the Playbook, I keep having an error trying to install tpot
The error appears to have been in '/home/admin/tpotce/installer/install/tpot.yml':
Aug 18, 2024
Ask T-Pot Assistant
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.
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
?~/install_tpot.log
, attach the log and highlight the errors.htop
anddocker stats
.df -h
)?dps
)?systemctl status tpot
)?systemctl stop tpot
and rungrc netstat -tulpen
systemctl stop tpot
grc netstat -tulpen
docker compose -f ~/tpotce/docker-compose.yml up
and check for errorsCTRL-C
anddocker compose -f ~/tpotce/docker-compose.yml down -v
DOWN
you can rundocker logs <container-name>
for the latest log entriesThe text was updated successfully, but these errors were encountered: