[WARN] could not determine server's ip address by ifconfig Is this bad? What does it mean? entire htp_report.txt attached. Thank you.
Have a look at this post: https://www.howtoforge.com/community/threads/cant-access-ispconfig-after-installation.71942/ Is your problem similar to that?
No, it does not seem to be so. I have no problem accessing my control panel at https://example.com:8080. Also, I do not have any problems that I know of, I just don't even know what this warning even means, or how to go about seeing if I need to fix it. And I am not hosting this server at home, it's in a data center.
If you can access your server from outside, I think you can safely ignore this warning, it just means your server is connected to the network in an unusual way
Code: root@server1:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:9565 errors:0 dropped:0 overruns:0 frame:0 TX packets:9565 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1181621 (1.1 MiB) TX bytes:1181621 (1.1 MiB) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:32520 errors:0 dropped:0 overruns:0 frame:0 TX packets:26459 errors:0 dropped:192 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4672686 (4.4 MiB) TX bytes:7486286 (7.1 MiB) venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.161.179.208 P-t-P:192.161.179.208 Bcast:192.161.179.208 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
nano /etc/hosts Code: GNU nano 2.2.6 File: /etc/hosts ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.0.1 localhost.localdomain localhost # Auto-generated hostname. Please do not remove this comment. 192.161.179.208 server1.yoadam.com server1 ::1 localhost ip6-localhost ip6-loopback
nothing to worry about here. I guess the htf-common-issues.php script should be updated to take virtual environments into account as they are quite common these days