T-pot WebUI connection failed (64297 - 64295)

[LyCrash]

I have successfully installed the latest T-pot version on a debian VM (Vmware Workstation 17) following the exact TL;DR instructions ( curl the installer not manual nor through tpot iso). After rebooting the system, I checked that ssh, tpot, docker are all active and running, but when I try to login from the browser (firefox) and access the T-Pot WebUI and tools with my private ip address (https://192.168.1.34:64297), I get that the website isn't availabe:

But if I enter on localhost (https://127.0.0.1:64297), I get the first loading page, but accessing other links (attackmap, cyberchef, elasticvue, kibana, spiderfoot) would lead to the same issue (connection failed)

Note that I can access remotly through ssh :

• What OS are you T-Pot running on? --> Debian 12 (iso installed from your github readme x64)

• 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)? --> T-Pot 24.04.0

• What architecture are you running on (i.e. hardware, cloud, VM, etc.)? --> HIVE = Standard

• Review the ~/install_tpot.log, attach the log and highlight the errors. --> no such a file

• How long has your installation been running? --> This is what I did: 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? --> No, I only followed TL;DR installer

• Did you modify any scripts or configs? If yes, please attach the changes. --> No

• Please provide a screenshot of htop and docker stats.

• htop:

• docker stats: (this is only the first lines but the list is longer)

• How much free disk space is available (df -h)?

• What is the current container status (dps)?

• Status Of T-Pot service:

• Status of Docker service:

[t3chn0m4g3]

Based on the description it seems the VM is setup as host only, it should use bridge mode.

[LyCrash]

Based on the description it seems the VM is setup as host only, it should use bridge mode.

@t3chn0m4g3 VM is already set to be bridged (not host-only nor NAT)

[t3chn0m4g3]

Works completely fine in VirtualBox, Parallels, VMware and UTM. Even followed up on host mode which works fine as well. Other than VMNet routing on your host or routing in general I cannot think of anything else (Windows firewall or maybe another security tool preventing access, maybe even a traffic shaper like cFosSpeed?).