+- TACTIC Open Source (http://forum.southpawtech.com)
+-- Forum: TACTIC Open Source (http://forum.southpawtech.com/forumdisplay.php?fid=3)
+--- Forum: TACTIC Discussion (http://forum.southpawtech.com/forumdisplay.php?fid=4)
+--- Thread: Can't connect to webserver (VM Images) - solved (/showthread.php?tid=177)
Can't connect to webserver (VM Images) - solved - tim - 10-22-2020
Hi
I'm trying to Run VM images ver.4.7 (ova) ver4.8 (vmdk) in VirtualBox and VMware and I'm getting IP: localhost:9090
and it does not work
Interesting that ver4.1 works, but because JAVA applets and some problems within Schema in workflow is hard to play with it.
some details:
I tried Mac and Windows 10 laptop. And the same result. I have Astrill vpn on both, but on Windows I've deleted it and import VM Image4.8 again and I'm getting the same not working address: localhost:9090
Windows10
I tried 3 different versions of VirtualBox 5, 6, 6.1
Tried (run VB as administrator, turned off firewall, deleted Astrill VPN)
Imported 4.7 and 4.8 images
Network Settings: tried host-only, bridge, NAT
Not working
contrary to 4.1
I've attached some screenshots
any suggestion highly appreciated
RE: Can't connect to webserver (VM Images) - remkonoteboom - 10-22-2020
I think I see what the problem is. The message you are seeing:
WebConsole: http://localhost:9090
is not something we did. It "came" with the OS. I never really noticed it before because I never look at the console on VMWare. I ssh directly into to it through some external means (ie: putty). I guess this is some web console that came with the OS (Fedora 31) and that is what is dumped by default.
From your browser, localhost is the windows OS, not the VMWare IP. You need the IP address of your VM. In the VM Console, type in:
# ifconfig
It will output something like:
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.115.129 netmask 255.255.255.0 broadcast 192.168.115.255
inet6 fe80::af1:795e:a079:6c31 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:b9:8b:be txqueuelen 1000 (Ethernet)
RX packets 2389935 bytes 1817094469 (1.6 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2168325 bytes 1712384491 (1.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3708413 bytes 3002810754 (2.7 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3708413 bytes 3002810754 (2.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
It's a bit mess, but in my case the IP is "192.168.115.129". So this is the address you would put in the browser:
http://192.168.115.129/
where TACTIC is running on the default port 80.
You would replace it with whatever IP address your VM is assigned.
RE: Can't connect to webserver (VM Images) - tim - 10-23-2020
this made a trick
thanks a lot remkonoteboom[b][url=http://forum.southpawtech.com/member.php?action=profile&uid=11][/url][/b]
Now I will try to test it
That was a strange behaviour and the same was on mac
great day